DEN (Denver) on 2026-11-06
We will be performing scheduled maintenance in DEN (Denver) datacenter on 2026-11-06 between 08:00 and 15:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
The latest update from Cloudflare.
State
Scheduled
Starts
in 3 d
2026-11-06 08:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Cloudflare
We will be performing scheduled maintenance in DEN (Denver) datacenter on 2026-11-06 between 08:00 and 15:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
59
Days with an incident
68
Median duration
1 h 15 min
This incident
Not comparable
Other Cloudflare incidents
All incidentsCloudflare·Elevated number of 5xx errors in HKG
Between 06:20-6:32 UTC customers reaching Hong Kong may have experienced an elevated number of 5xx errors or CNI timeouts due to congestion.
Cloudflare·Partial System Outage
Cloudflare reports a partial outage. The affected components include Amsterdam, Arica, Algiers, Anchorage, Annaba, Baku, Bangalore, Canberra, Austin, Hagatna, Dammam, Djibouti, Durban, Erbil, Sydney, Gaborone, Dallas, Curitiba, Luanda, and Mombasa. Cloudflare is investigating the incident.
Cloudflare·Network Performance Issues in APJC
Cloudflare reported network performance issues in the APJC region. The Network component was degraded. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and lasted about 72 minutes.
Cloudflare·Cloudflare Container Issues
Cloudflare Containers failed to start and showed an increased level of errors. Cloudflare reports that the incident is resolved. The incident lasted 71 minutes.
Cloudflare·Partial System Outage
Cloudflare reports a partial system outage. The outage affects 20 locations, including Amsterdam, Bangalore, Sydney, Dallas, and Nairobi. Cloudflare reports that the incident is resolved. The outage lasted 3 hours and 36 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