Live

R2 and Durable Objects availability issues

0

R2 and Durable Objects in Eastern North America have intermittent errors and failed requests. Cloudflare reports that a fix is in place and monitoring is in progress.

State

Monitoring

Started

Ongoing for

1 h 29 min

Worst impact

Degraded

Timeline

2 updates
02:5203:1503:3703:5904:21
DegradedUpdate postedTimes in UTC

Investigating

1 h 10 min 79%

Monitoring

18 min 21%

Updates

Times in UTC

As posted by Cloudflare

Monitoring

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

Investigating

Customers using R2 and Durable Objects in Eastern North America may be experiencing intermittent errors and failed requests. We are investigating the cause and working to confirm that service availability has stabilized. We will provide updates as more information becomes available.

Affected components

2
Durable ObjectsR2

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

123

Days with an incident

85

Median duration

1 h 30 min

This incident

About the median

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

56 days
median 1 h 30 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Observability ingestion delay and query failures

Cloudflare Workers Observability and Cloudflare Traces had delays in new data ingestion and increased query errors. The incident affected the Workers and Workers Observability components. Cloudflare reports that the incident is resolved, and it lasted about 5 hours and 26 minutes.

Resolved

Cloudflare·Durable Objects and D1 – Increased Errors

Cloudflare reported increased errors and latency on Durable Objects and D1 for a subset of customers; Workers that do not use these components were not affected. Cloudflare identified the problem and implemented a fix. The incident is resolved and lasted about 32 minutes.

Resolved

Cloudflare·Cloudflare Access Issue

Cloudflare Access had degraded performance that can cause authentication failures for applications that strictly validate token claims. Cloudflare reports that the incident is resolved and lasted 2 hours and 8 minutes.

Resolved

Cloudflare·Degraded connectivity between Europe and Asia Pacific

Cloudflare reported degraded connectivity between Europe and Asia Pacific. This affected Cache Reserve, D1, and R2. Cloudflare reported the incident as resolved after 4 hours and 53 minutes.

Resolved

Cloudflare·Increased latency on Analytics API (GraphQL) queries

Cloudflare reports increased latency on Analytics API GraphQL queries. The incident is resolved and lasted about 2 hours and 47 minutes.

Resolved

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