Live

R2 elevated errors and timeouts for requests from South America

0

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 updates
20:0520:3621:0721:3722:08
DegradedUpdate postedTimes in UTC

Investigating

10 min 8%

Identified

39 min 32%

Monitoring

1 h 14 min 60%

Updates

Times in UTC

As posted by Cloudflare

Resolved

This incident has been resolved.

Monitoring

A fix has been implemented and we are monitoring the results.

Identified

The issue has been identified and a fix is being implemented.

Investigating

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

1
R2

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

116

Days with an incident

83

Median duration

1 h 26 min

This incident

1.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 26 min
90 days agoToday

Other Cloudflare incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane