Live

Durable Objects and D1 – Increased Errors

0

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.

State

Resolved

Started

Lasted

32 min

Worst impact

Degraded

Timeline

3 updates
13:0513:1313:2113:2913:37
DegradedUpdate postedTimes in UTC

Investigating

22 min 70%

Identified

10 min 30%

Updates

Times in UTC

As posted by Cloudflare

Resolved

This incident has been resolved.

Identified

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

Investigating

Cloudflare is investigating an increased level of errors and latency affecting a subset of Durable Objects and D1 customers. Affected customers may see storage operations fail or take longer than usual to complete. Workers that don't use Durable Objects or D1 are not affected. We are working to analyse and mitigate this problem. More updates to follow shortly.

Affected components

2
Durable ObjectsD1

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

64% shorter than 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

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