Live

DFW (Dallas) on 2026-11-05

MaintenanceOfficial update

We will be performing scheduled maintenance in DFW (Dallas) datacenter on 2026-11-05 between 07:00 and 13: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

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Cloudflare

Scheduled

We will be performing scheduled maintenance in DFW (Dallas) datacenter on 2026-11-05 between 07:00 and 13: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

2
Dallas, United States - (DFW)North America - Dallas, United States - (DFW)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

68

Days with an incident

70

Median duration

1 h 33 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 33 min
90 days agoToday

Other Cloudflare incidents

All incidents

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.

Resolved

Cloudflare·Partial System Outage

Cloudflare reports a partial outage. The affected components include Albuquerque, Arica, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Manama, Curitiba, Luanda, Mombasa, Helsinki, Nairobi, Fuzhou, and Guatemala City. Cloudflare is investigating the problem.

Partial outage

Cloudflare·Network latency issues in NRT

Cloudflare reported network latency issues in Tokyo, Japan (NRT) that affected the Network component. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and it lasted 114 minutes.

Resolved

Cloudflare·Partial System Outage

Cloudflare reported a partial system outage that affected 20 locations, including Albuquerque, Sydney, Dallas, Bangalore, and Nairobi. Cloudflare reports that the incident is resolved. The outage lasted about 18 hours.

Resolved

Cloudflare·Increased Durable Object Errors in the Dallas, TX US region

Cloudflare Durable Objects had more errors than usual in the Dallas, TX US region. Cloudflare reports that the incident is resolved. The incident lasted about 64 minutes.

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.cc/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane