Cloudflare outage on October 12, 2026: Elevated errors in Los Angeles (LAX)
Cloudflare reported an incident affecting Cloudflare for 1 day 8 hours on 12 October 2026, from 08:52 to 17:40 UTC.
Resolved
Official incident reported by Cloudflare
- Started
- 08:52
- 12 Oct 2026 UTC
- Resolved
- 17:40
- 13 Oct 2026 UTC
- Duration
- 1d 8h
- 1 day 8 hours
- Impact
- Minor
- as rated by Cloudflare
- Updates
- 3
- posted by Cloudflare
Timeline
All times UTC.
Official incident from Cloudflare
Elevated errors in Los Angeles (LAX)
-
Official
Investigating
Customers reaching Los Angeles (LAX) colo may see an elevate number of errors. Our team is investigating and working on mitigating the issue.
-
Official
Identified
We are continuing to work on a fix for the issue.
-
Official
Resolved
This incident has been resolved.
"Official" rows are quoted from Cloudflare's public status page, www.cloudflarestatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test cloudflare.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Cloudflare status shows what our checks see right now.
Does your product depend on Cloudflare?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Cloudflare. Official updates are quoted from Cloudflare's public status page and remain Cloudflare's own words.