outages.live
Live
CloudflareIncident ·

Partial System Outage

Partial outageOfficial update
0

Cloudflare reports a partial outage in 20 locations, including Dallas, Sydney, Bangalore, Helsinki, and Nairobi. Cloudflare is investigating the issue.

State

Components degraded

Started

Ongoing for

1 h 33 min

Worst impact

Partial outage

Timeline

1 update
15:3315:5616:2016:4317:06
Partial outageUpdate postedTimes in UTC

Components degraded

1 h 33 min 100%

Updates

Times in UTC

As posted by Cloudflare

Components degraded

Affected components

58
Albuquerque, United States - (ABQ)Arica, Chile - (ARI)Annaba, Algeria - (AAE)Baku, Azerbaijan - (GYD)Bangalore, India - (BLR)Canberra, Australia - (CBR)Belo Horizonte, Brazil - (CNF)Hagatna, Guam - (GUM)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

67

Days with an incident

69

Median duration

1 h 36 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 36 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Network latency issues in NRT

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

Resolved

Cloudflare·Partial System Outage

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

Resolved · 1 affected

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

Cloudflare reported increased errors from Durable Objects in the Dallas, Texas, USA region. Cloudflare monitored the issue and then resolved it. The incident lasted 64 minutes.

Resolved

Cloudflare·Cloudflare Workers and Pages build errors

Cloudflare Workers Builds had build failures and longer queue times. The problem affected the Workers Builds component. Cloudflare reports that the incident is resolved. It lasted about 4 hours and 51 minutes. Customers with failed builds can retry in the Dashboard or push a new commit.

Resolved

Cloudflare·Increased Latency and Errors for R2 and Downstream Services in Western North America (WNAM)

Cloudflare has resolved an issue affecting R2 and downstream services in the Western North America region. Some customers may have seen elevated latency and errors between approximately 13:00 and 22:15 UTC on November 3, 2026. This may also have affected downstream services such as Stream and Pipelines.

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