outages.live
Live
CloudflareIncident · 2026-11-03 05:57 UTC

Partial System Outage

Partial outageOfficial update
0

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.

State

Components degraded

Started

2 h ago

2026-11-03 05:57 UTC

Ongoing for

1 h 57 min

Worst impact

Partial outage

Timeline

1 update
05:5706:2606:5507:2507:54
Partial outageUpdate postedTimes in UTC

Components degraded

1 h 57 min 100%

Updates

Times in UTC

As posted by Cloudflare

Components degraded2026-11-03 05:57 UTC

Affected components

61
Amsterdam, Netherlands - (AMS)Arica, Chile - (ARI)Algiers, Algeria - (ALG)Anchorage, United States - (ANC)Annaba, Algeria - (AAE)Baku, Azerbaijan - (GYD)Bangalore, India - (BLR)Canberra, Australia - (CBR)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

59

Days with an incident

68

Median duration

1 h 15 min

This incident

1.6× the median

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

56 days
median 1 h 15 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·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.

Resolvedresolved 1 h ago

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.

Resolvedresolved 2 h ago

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.

Resolvedresolved 3 h ago

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.

Resolvedresolved 4 h ago

Cloudflare·Cloudflare Gateway DNS-over-TLS Connectivity Issues over IPv4

Cloudflare Gateway DNS-over-TLS connections over IPv4 did not work. This caused 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, then monitored the results. The incident is resolved and lasted about 2 hours and 22 minutes.

Resolvedresolved 7 h ago

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane