R2 elevated errors and timeouts for requests from South America
Cloudflare R2 had elevated errors and read timeouts for requests from South America. The affected datacenters include GRU, GIG, EZE, and SCL. Cloudflare reports that the incident is resolved. It lasted about 2 hours and 3 minutes.
State
Resolved
Started
Lasted
2 h 3 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
10 min 8%
Identified
39 min 32%
Monitoring
1 h 14 min 60%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are investigating elevated errors and read timeouts affecting R2 requests originating from South America (impacting datacenters such as GRU, GIG, EZE, and SCL). Our team is actively working to identify and resolve the issue.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
116
Days with an incident
83
Median duration
1 h 26 min
This incident
1.4× the median
Other Cloudflare incidents
All incidentsCloudflare·Network disruption across multiple colocations in India
A network disruption degraded some Cloudflare services in Ahmedabad, Hyderabad, Kanpur, Mumbai, Nagpur, New Delhi, and Patna, India. Cloudflare identified the issue and implemented a fix, then monitored the results. The incident is resolved and lasted 42 minutes.
Cloudflare·Network Performance Issues in North America
Between approximately 07:00 UTC and 10:00 UTC Cloudflare investigated issues with network performance in North America. This has since been resolved.
Cloudflare·Network Performance Issues in Paris
Cloudflare reported degraded network performance in Paris, France (CDG). The incident affected the Network and Cloud Network Interconnect (CNI) components. Cloudflare reported the incident as resolved after 1 hour and 12 minutes.
Cloudflare·Elevated 5xx error rates and latency in Mumbai
Between 02:31-03:04 UTC on November 18, a subset of customers reaching Mumbai, IN, may have experienced an elevated number of 5xx errors and increased latency. This has been resolved.
Cloudflare·Cloudflare Access Issue
Cloudflare Access had degraded performance. Customers may have seen a delay when they made configuration changes to Access. Cloudflare reports that the incident is resolved. It lasted about 90 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