Cloudflare Worker Builds Issue
Cloudflare Worker Builds did not work. The issue affected the Workers, Containers, and Workers Builds components. Cloudflare reports that the incident is resolved. The outage lasted 12 minutes, from 06:29 to 06:41 UTC on 11 November 2026.
State
Resolved
Started
Lasted
12 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
4 min 34%
Identified
3 min 24%
Monitoring
5 min 42%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Cloudflare is aware of and investigating an issue with Cloudflare Worker Builds which potentially impacts multiple customers. Further detail will be provided as more information becomes available. Existing Workers and Containers are unaffected.
Affected components
3Cloudflare in the last 90 days
Full historyIncidents in 90 days
90
Days with an incident
76
Median duration
1 h 26 min
This incident
86% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·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
Cloudflare·SSL Certificate Provisioning Issue
Cloudflare had a problem with SSL Certificate Provisioning that affected the deployment of some custom certificates. Cloudflare advised customers to pause certificate redeployments during the incident. The incident is resolved and lasted 142 minutes.
Cloudflare·Elevated number of 5xx errors in Hong Kong
Between 07:30-07:45 UTC customers reaching Hong Kong, may have experienced an elevated number of 5xx errors.
Cloudflare·Replicate Input Upload Issue
Cloudflare reports that Replicate input uploads are degraded. Model builds and pushes through r8.im do not work. Cloudflare identified the problem and continues to implement a fix.
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