Skip to content
OutageDeck

Incident detail

Increased errors for R2 and Tiered Cache

Active incidentMinor1 affected service

Timeline window

Started

Get alerted the next time Cloudflare breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Cloudflare alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    Cloudflare is aware of, and investigating an issue with R2. Customers in Chicago, IL, may see 503 errors when using R2. We are currently investigating this issue.

  2. Monitoring

    Starting at 05:00 UTC, a network connectivity issue between several Cloudflare data centers caused a small percentage of requests to fail. R2 customers may have seen HTTP 500 errors, and requests for content served through Tiered Cache may have returned 520, 522 or 524 errors. Customers in Chicago and Newark saw the highest error rates, and other locations were affected at lower rates. Error rates have dropped close to normal levels since 05:30 UTC. We are continuing to monitor while the underlying network issue is resolved.

Keep exploring

More from Cloudflare

Neighboring incidents on Cloudflare's timeline and the rest of their record on OutageDeck.

← Older incident

Issues with 1.1.1.1 public resolver in Canada

All Cloudflare incidentsCloudflare live status