Resolved Cloudflare · degraded service

Increased errors for R2 and Tiered Cache

Started today 05:30 UTC, resolved today 06:45 UTC: it lasted 1 h 15 min.

Cloudflare status page On the status board

1 h 15 min How long it lasted, from the provider's times

3Updates posted

1Region named

6Other incidents at the same time

What it affected

As the provider names it

North AmericaR2

What the provider posted

Newest first

today 06:45 UTCResolvedThis incident has been resolved.
today 05:43 UTCMonitoringStarting 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.
today 05:30 UTCInvestigatingCloudflare 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.
today 05:44 UTC ChangeIntel noticed a new title; it was "Increased Errors for R2 in Chicago"

Around it

From the sources ChangeIntel reads; a match in time is not a cause

Elsewhere at the same time

OpenAI Delayed Costs Data in the Compliance API
Microsoft 365 and Copilot for consumers Users may be unable to access or perform several actions in Microsoft 365 services
Cloudflare Changes to Cloudflare Workers are not producing Event Subscription events
Cloudflare Spectrum Availability issues
Palo Alto Networks cloud services Prisma Cloud: App: alert remediation is unavailable
Palo Alto Networks cloud services Scheduled Maintenance for File Manager (FileMgr) in France region

Earlier incidents in the 14 days before

Cloudflare: Issues with 1.1.1.1 public resolver in CanadaService incident · 13 Nov
Cloudflare: Cloudflare is currently having an issue with the r8.im registry used for Replicate model publishing and builds is currently restrictedService incident · 13 Nov
Cloudflare: Elevated error rate for workers startupService incident · 13 Nov
Cloudflare: Durable Objects increased error rates in North AmericaService incident · 12 Nov
Cloudflare: Replicate IssueService incident · 12 Nov

Keep track

Service status now: every provider ChangeIntel reads, with ongoing incidents first.
Status RSS feed: new and ended incidents as they happen.
Everything about Cloudflare: its changes, known issues and incidents on one timeline.

What changed

Resolved: 14 Nov 2026 06:45 UTC · Status: Monitoring → Resolved · Incident state: Ongoing → Ended
14 Nov 2026 · 06:46:12 UTC
Status: Investigating → Monitoring · Title changed
14 Nov 2026 · 05:44:45 UTC

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version

Field-level log (7)

Up to 100 recent field edits are shown; older edits may be outside retention.

14 Nov 2026 · 06:46:12 UTC Resolved14 Nov 2026 06:45 UTC
14 Nov 2026 · 06:46:12 UTC StageMonitoring → Resolved
14 Nov 2026 · 06:46:12 UTC Observed stateOngoing → Ended
14 Nov 2026 · 06:46:12 UTC SummaryStarting 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. → This incident has been resolved.
14 Nov 2026 · 05:44:45 UTC StageInvestigating → Monitoring
14 Nov 2026 · 05:44:45 UTC SummaryCloudflare 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. → 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.
14 Nov 2026 · 05:44:45 UTC TitleIncreased Errors for R2 in Chicago → Increased errors for R2 and Tiered Cache