Live

Network performance issues in Los Angeles (LAX) and Frankfurt (FRA) datacenters

0

Cloudflare network performance is degraded in the Los Angeles (LAX) datacenter. Cloudflare has identified the issue and a fix is being implemented.

State

Identified

Started

Ongoing for

35 min

Worst impact

Degraded

Timeline

1 update
17:1217:2117:3017:3817:47
DegradedUpdate postedTimes in UTC

Identified

35 min 100%

Updates

Times in UTC

As posted by Cloudflare

Identified

The issue has been identified and a fix is being implemented.

Affected components

1
Network

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

109

Days with an incident

82

Median duration

1 h 24 min

This incident

58% 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 24 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Errors and stalled predictions on some models

Cloudflare reports errors and stalled predictions on the Replicate component. Some prediction requests return HTTP 500 errors, some predictions stay in a processing state, and some API responses lack version information. Cloudflare has identified the issue and a fix is in progress.

Degraded

Cloudflare·Elevated number of 5xx and 499 errors

Between 13:55-14:35 UTC customers reaching Minneapolis, MN and Saint Louis, MO would have experienced an elevated number of 499 and 5xx errors.

Resolved

Cloudflare·Cloudflare One Gateway traffic unable to connect to Cloudflare domains that are regionalized

Cloudflare One Gateway traffic could not connect to regionalized Cloudflare domains. The problem affected Zero Trust, Data Localization Suite, and Cloudflare One Client. Cloudflare reports that the incident is resolved. It lasted about 63 minutes.

Resolved

Cloudflare·Turnstile verification failures

Cloudflare Turnstile verification did not work for some users with browser fingerprinting protection enabled, including Helium. Cloudflare identified the issue, implemented a fix, and later reported the incident as resolved. The outage started at 10:24 UTC and lasted about 6 hours 12 minutes.

Resolved

Cloudflare·Elevated number of 52x origin connectivity errors in Seoul

Between 04:50 - 05:50 UTC 17th November, customers in Seoul may have experienced an elevated number of 52x origin connectivity errors. This is now resolved.

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