Increased errors for R2 and Tiered Cache
Cloudflare reported increased errors for R2 and Tiered Cache in Chicago (ORD) and Newark (EWR), with lower error rates in other locations. Cloudflare reported the incident as resolved after 75 minutes, from 05:30 UTC to 06:45 UTC.
State
Resolved
Started
Lasted
1 h 15 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
15 min 20%
Monitoring
1 h 80%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
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.
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.
Affected components
4Cloudflare in the last 90 days
Full historyIncidents in 90 days
98
Days with an incident
79
Median duration
1 h 29 min
This incident
16% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Issues with 1.1.1.1 public resolver in Canada
The 1.1.1.1 public resolver does not work for some users in Canada. The Recursive DNS component is affected. Cloudflare reports that the incident is resolved. The outage lasted about 68 minutes.
Cloudflare·Cloudflare is seeing an issue with Workers API availability
Cloudflare Workers API availability is degraded. Customers can see more 5xx errors when they deploy Workers or do other API actions. Cloudflare identified the issue, implemented a fix, and now monitors the results.
Cloudflare·Cloudflare is currently having an issue with the r8.im registry used for Replicate model publishing and builds is currently restricted
Cloudflare reports a problem with the r8.im registry. This problem restricts Replicate model publishing and builds. The incident is resolved. It lasted about 10 hours.
Cloudflare·Elevated error rate for workers startup
Cloudflare Workers startup had an elevated error rate. The problem affected Workers and Developer Services - Workers, mainly for Workers that use large amounts of memory. Cloudflare resolved the incident after 82 minutes.
Cloudflare·Durable Objects increased error rates in North America
Cloudflare Durable Objects had increased error rates in North American colos. Cloudflare reports that the incident is resolved. The incident lasted about 5 hours and 5 minutes.
Follow Cloudflare
Your coding agent knows when Cloudflare is down, and tells you when a failure is theirs, not yours. You can also get Cloudflare incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudflare" and tell me if Cloudflare has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=cloudflare/feed subscribe https://outages.live/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane