ATL (Atlanta) on 2026-11-05
We will be performing scheduled maintenance in ATL (Atlanta) datacenter on 2026-11-05 between 07:00 and 11: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 2 d
2026-11-05 07:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Cloudflare
We will be performing scheduled maintenance in ATL (Atlanta) datacenter on 2026-11-05 between 07:00 and 11: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
54
Days with an incident
67
Median duration
1 h 17 min
This incident
Not comparable
Other Cloudflare incidents
All incidentsCloudflare·Cloudflare Gateway DNS-over-TLS Connectivity Issues over IPv4
Cloudflare Gateway DNS-over-TLS connections over IPv4 do not work. This affects the Gateway and Zero Trust Gateway components. Cloudflare reports that it is investigating the issue.
Cloudflare·Partial System Outage
Cloudflare reported a partial outage across several locations, including Ahmedabad, Arica, Algiers, Bangalore, Canberra, Sydney, Dallas, and other listed cities. Cloudflare reports that the incident is resolved. The outage lasted 4 hours and 45 minutes.
Cloudflare·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.
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.
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