Cloudflare incident: Elevated errors in Los Angeles (LAX)

Affected components

• Los Angeles, CA, United States - (LAX)

1. resolvedOct 13, 2026, 17:40 UTC

   This incident has been resolved.

2. identifiedOct 12, 2026, 21:41 UTC

   We are continuing to work on a fix for the issue.

3. investigatingOct 12, 2026, 08:52 UTC

   Customers reaching Los Angeles (LAX) colo may see an elevate number of errors. Our team is investigating and working on mitigating the issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cloudflare's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• LiveKit: Observability upload and Agent Simulations failuresCritical · Oct 13, 2026, 10:01 UTC
• Anthropic: Elevated errors on platform.claude.comMajor · Oct 7, 2026, 13:25 UTC
• Shippo: UPS Tracking disruptionMajor · Oct 11, 2026, 03:22 UTC
• Telnyx: Email API messages rejected with gw_reject// injection_failedMajor · Oct 12, 2026, 08:31 UTC
• Grafana Cloud: Elevated Errors Ingesting Metrics in AWS US East (VA)Major · Oct 12, 2026, 09:45 UTC
• Vercel: Increased build and deployment failuresMajor · Oct 12, 2026, 13:35 UTC
• Contentful: [INCIDENT] https://www.contentful.com/developers/docs/ is not workingMajor · Oct 12, 2026, 18:22 UTC
• Shippo: La Poste Service DegradationMajor · Oct 12, 2026, 21:42 UTC
• Shippo: Elevated error rate on Canada post Shipment APIMajor · Oct 13, 2026, 08:58 UTC
• ElevenLabs: Multiple US endpoints experiencing timeouts and latencyMajor · Oct 13, 2026, 09:21 UTC

How often does Cloudflare have incidents?

Cloudflare reported 97 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 1h 46m. See Cloudflare's uptime and incident history