outages.live
Live
CloudflareIncident ·

Partial System Outage

Partial outageOfficial update
0

Cloudflare reports a partial outage across 20 locations, including Chicago, Dallas, Sydney, Bangalore, and Bogotá. Cloudflare is investigating the problem. The incident started at 10:45 UTC on 6 November 2026.

State

Components degraded

Started

Ongoing for

1 h 49 min

Worst impact

Partial outage

Timeline

1 update
10:4511:1211:3912:0712:34
Partial outageUpdate postedTimes in UTC

Components degraded

1 h 49 min 100%

Updates

Times in UTC

As posted by Cloudflare

Components degraded

Affected components

62
Albuquerque, United States - (ABQ)Arica, Chile - (ARI)Annaba, Algeria - (AAE)Baku, Azerbaijan - (GYD)Bangalore, India - (BLR)Canberra, Australia - (CBR)Hagatna, Guam - (GUM)Bogotá, Colombia - (BOG)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

74

Days with an incident

71

Median duration

1 h 33 min

This incident

1.2× the median

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·Wrangler Deployments, Pages, and Workers Builds failures

Cloudflare Wrangler deployments, Pages, and Workers Builds failed. The incident affected Pages, Workers Builds, Wrangler, Developer Services - Pages, and Developer Services - Workers Builds. Cloudflare reported the incident as resolved after 21 minutes.

Resolved

Cloudflare·Network Performance Issues in Singapore

Cloudflare reported network performance issues in the Singapore (SIN) region. Cloudflare reports that the incident is resolved. The incident lasted about 1 hour and 50 minutes.

Resolved

Cloudflare·Workers Builds Issues

Cloudflare Workers Builds had degraded performance. The incident is resolved. It lasted 29 minutes.

Resolved

Cloudflare·Network disruption across multiple colocations in India

Cloudflare reported a network disruption across multiple colocations in India. The disruption degraded Cloudflare services in the region and affected Cloudflare R2 in Asia Pacific. Cloudflare identified 9 impacted colocations in India and removed them from the network. The incident is resolved and lasted 72 minutes.

Resolved

Cloudflare·Increased Errors for Durable Objects in Western Europe

Cloudflare reported increased errors for Durable Objects in Western Europe. The incident is resolved and it lasted about 19 hours and 41 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.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