Changes made to Workers may be delayed or disrupted
Cloudflare reported that changes to Workers, such as creating, editing and deleting them, were delayed or disrupted. Deployed Workers were not affected. Cloudflare resolved the incident after about 9 hours and 31 minutes.
State
Resolved
Started
Lasted
9 h 31 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
9 min 2%
Identified
12 min 2%
Monitoring
9 h 10 min 96%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
We are continuing to monitor for any further issues.
We are continuing to work on a fix for the issue.
Cloudflare is aware of and investigating issues related to creating, editing and deleting Workers. Impact is limited to changing Workers — Workers that are already deployed are unaffected.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
81
Days with an incident
75
Median duration
1 h 39 min
This incident
5.8× the median
Other Cloudflare incidents
All incidentsCloudflare·Changes to Cloudflare Workers are not producing Event Subscription events
Cloudflare Workers changes do not produce Event Subscription events. This affects Workers and Queues. Cloudflare reports that it is investigating. Cloudflare disabled the feature on purpose and is working to restore it.
Cloudflare·Network Performance Issues in Eastern North America
Cloudflare network performance was degraded in Eastern North America. The Network component was affected. Cloudflare reported the incident as identified, then monitored it. Cloudflare resolved the incident after about 3 hours and 38 minutes.
Cloudflare·Spectrum Availability issues
Cloudflare Spectrum and Network Services - Spectrum had availability problems. Cloudflare reports that the incident is resolved. The incident lasted about 6 minutes.
Cloudflare·Network Performance Issues in Chicago
Between 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.
Cloudflare·Spectrum Availability Issue in Phoenix
Cloudflare Spectrum was degraded in Phoenix. The incident is resolved and lasted about 2 days and 14 hours.
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