Cloudflare Container Issues
Cloudflare Containers failed to start and gave an increased level of errors. Cloudflare identified the problem and put a fix in place. The incident is resolved and it lasted 71 minutes.
State
Resolved
Started
1 h ago
2026-11-03 04:12 UTC
Lasted
1 h 11 min
until 2026-11-03 05:23 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
57 min 80%
Identified
6 min 8%
Monitoring
8 min 11%
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 investigating an increased level of errors for Containers failing to start. We are working to analyse and mitigate this problem. More updates to follow shortly.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
57
Days with an incident
68
Median duration
1 h 21 min
This incident
About the median
Other Cloudflare incidents
All incidentsCloudflare·Network Performance Issues in APJC
Cloudflare reports network performance issues in the APJC region. The Network component is degraded. Cloudflare identified the issue and is implementing a fix.
Cloudflare·Partial System Outage
Cloudflare reported a partial outage on 20 points of presence. The affected locations include Amsterdam, Bangalore, Sydney, Dallas, and Nairobi. Cloudflare reports that the incident is resolved. The outage lasted 219 minutes.
Cloudflare·Cloudflare Gateway DNS-over-TLS Connectivity Issues over IPv4
Cloudflare Gateway DNS-over-TLS connections over IPv4 had connection timeouts and failed DNS resolution. DoT over IPv6, DNS-over-HTTPS, and standard DNS over UDP/TCP were not affected. Cloudflare identified and applied a fix, monitored the results, and resolved the incident. It lasted about 2 hours and 22 minutes.
Cloudflare·Partial System Outage
Cloudflare reports a partial system outage at 20 points of presence. The affected locations include Ahmedabad, Arica, Algiers, Annaba, Baku, Bangalore, Canberra, Hagatna, Doha, Djibouti, Erbil, Sydney, Gaborone, Dallas, Curitiba, Luanda, Dhaka, Mombasa, Nairobi, and Fuzhou. Cloudflare reports that the incident is resolved. The outage lasted 282 minutes, from 17:33 to 22:15 UTC on 2 November 2026.
Cloudflare·Worker Deployments Delayed
Cloudflare Workers deployments were delayed. The incident affected Workers and Developer Services - Workers. Cloudflare reports that the incident is resolved. It lasted 49 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.cc/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.cc/feed.xml?providers=cloudflare/feed subscribe https://outages.cc/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane