Elevated error rate for workers startup
Cloudflare Workers show a degraded service. The problem causes more errors when Workers that use large amounts of memory start. Cloudflare identified the issue and is working on a fix.
State
Identified
Started
Ongoing for
56 min
Worst impact
Degraded
Timeline
1 updateIdentified
56 min 100%
Updates
Times in UTCAs posted by Cloudflare
Cloudflare is investigating an elevated error rate for workers startup, for workers that use large amounts of memory We have identified the issue and are working on a solution to fix the issue. More updates to follow shortly.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
94
Days with an incident
78
Median duration
1 h 36 min
This incident
42% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·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.
Cloudflare·Replicate Issue
Cloudflare Replicate customers saw more 500 errors for predictions in the Replicate component. Cloudflare identified the issue and put a fix in place. The incident is resolved and lasted 3 hours and 4 minutes.
Cloudflare·DNSSEC Configuration Change Issues
Cloudflare reported degraded DNSSEC Updates. Customers could not enable or disable DNSSEC signing. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and lasted 33 minutes.
Cloudflare·Network Performance Degraded
Cloudflare reported network performance degradation near LAX and Western North America. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and it lasted 26 minutes.
Cloudflare·Workers deployments errors with D1 bindings
Cloudflare has identified and resolved an issue impacting Workers deployments with D1 bindings. Customers may have seen issues deploying their Workers between 12:42 UTC - 13:03 UTC 11th November 2026
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