outages.live
Live
CloudflareIncident ·

Partial System Outage

Partial outageOfficial update
0

Cloudflare reports a partial outage. The problem affects some Cloudflare systems in 20 locations, including Accra, Albuquerque, Bangalore, Sydney, Dallas, Nairobi, and Fuzhou. Cloudflare is investigating the problem.

State

Components degraded

Started

Ongoing for

1 h 4 min

Worst impact

Partial outage

Timeline

1 update
19:3919:5520:1120:2720:43
Partial outageUpdate postedTimes in UTC

Components degraded

1 h 4 min 100%

Updates

Times in UTC

As posted by Cloudflare

Components degraded

Affected components

59
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

63

Days with an incident

68

Median duration

1 h 21 min

This incident

21% shorter than 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·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·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.

Resolved

Cloudflare·Partial System Outage

Cloudflare reported a partial outage in 20 locations. These locations include Accra, Albuquerque, Arica, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Manama, Curitiba, Luanda, Mombasa, Nairobi, Fuzhou, and Istanbul. The incident is resolved, and it lasted 531 minutes.

Resolved

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.

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