outages.live
Live
CloudflareIncident · 2026-11-03 00:36 UTC

Partial System Outage

Partial outageOfficial update
0

Cloudflare reports a partial outage that affects 20 points of presence. The affected sites include Amsterdam, Bangalore, Sydney, Dallas, Nairobi, and others. Cloudflare is investigating the problem.

State

Components degraded

Started

1 h ago

2026-11-03 00:36 UTC

Ongoing for

1 h 17 min

Worst impact

Partial outage

Timeline

1 update
00:3600:5501:1401:3301:53
Partial outageUpdate postedTimes in UTC

Components degraded

1 h 17 min 100%

Updates

Times in UTC

As posted by Cloudflare

Components degraded2026-11-03 00:36 UTC

Affected components

62
Amsterdam, Netherlands - (AMS)Accra, Ghana - (ACC)Arica, Chile - (ARI)Algiers, Algeria - (ALG)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

55

Days with an incident

68

Median duration

1 h 21 min

This incident

About the median

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

56 days
median 1 h 21 min
90 days agoToday

Other Cloudflare incidents

All incidents

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 1 h ago

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.

Resolvedresolved 4 h ago

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.

Resolvedresolved 8 h ago

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.

Resolvedresolved 9 h ago

Cloudflare·Cache purge delays in Qingdao Shandong, China

This incident has been resolved.

Resolvedresolved 3 d 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