Workers Builds Issues
Cloudflare Workers Builds had degraded performance. The incident is resolved. It lasted 29 minutes.
State
Resolved
Started
Lasted
29 min
Worst impact
Degraded
Timeline
3 updatesIdentified
6 min 20%
Monitoring
23 min 80%
Updates
Times in UTCAs posted by Cloudflare
Queue times have returned to normal.
Builds are being processed and we're working through backlog
Cloudflare is aware of and investigating an issue with Cloudflare Workers Builds which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
71
Days with an incident
70
Median duration
1 h 29 min
This incident
68% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Network disruption across multiple colocations in India
Cloudflare reported a network disruption across multiple colocations in India. The disruption degraded Cloudflare services in the region and affected Cloudflare R2 in Asia Pacific. Cloudflare identified 9 impacted colocations in India and removed them from the network. The incident is resolved and lasted 72 minutes.
Cloudflare·Increased Errors for Durable Objects in Western Europe
Durable Objects do not work correctly in Western Europe. Cloudflare reports that it identified an issue that caused more errors and that the fix is in place. Cloudflare is now monitoring the results.
Cloudflare·Increased Errors for Durable Objects and Downstream Services in Eastern North America (ENAM)
Cloudflare has resolved an issue affecting Durable Objects and downstream services in the Eastern North America (ENAM) region. Some customers may have seen elevated errors between approximately 21:20 and 21:22 UTC on November 4, 2026. This also affected downstream services such as R2.
Cloudflare·Partial System Outage
Cloudflare reports a partial outage across 20 locations, including Albuquerque, Sydney, Dallas, Bangalore, and Nairobi. Cloudflare reports that the incident is resolved. The outage lasted about 21 hours and 51 minutes.
Cloudflare·Network latency issues in NRT
Cloudflare reported network latency issues in the Network component and the Tokyo, Japan (NRT) region. Cloudflare identified the issue and implemented a fix. The incident is resolved and lasted 114 minutes.
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