Worker Deployments Delayed
Cloudflare Workers deployments were delayed. The service also affected Developer Services - Workers. Cloudflare reports the incident is resolved. It lasted 49 minutes.
State
Resolved
Started
1 h ago
2026-11-02 16:41 UTC
Lasted
49 min
until 2026-11-02 17:30 UTC
Worst impact
Degraded
Timeline
2 updatesIdentified
49 min 100%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
Some customers may see delays when deploying updates to Cloudflare Workers. Remediation is in progress.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
53
Days with an incident
67
Median duration
1 h 15 min
This incident
34% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
A partial outage affects Cloudflare components in Arica, Algiers, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Curitiba, Luanda, Mombasa, Nairobi, Fuzhou, Istanbul, Guatemala City, and Kyiv. Cloudflare reports the state as degraded components. The outage started at 17:30 UTC on 2 November 2026 and continues.
Cloudflare·Partial System Outage
Cloudflare reports a partial outage at 20 locations, including Dallas, Sydney, Bangalore, and Nairobi. Cloudflare reports that the incident is resolved. The outage lasted 32 hours and 3 minutes.
Cloudflare·Cache purge delays in Qingdao Shandong, China
This incident has been resolved.
Cloudflare·Increased Errors for Browser Run
This incident has been resolved.
Cloudflare·R2 Elevated Latency in Eastern Europe
This incident has been 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.
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