Live / Cloudflare / Incident
Cloudflare: Network Performance Degraded
Cloudflare · cloudflare.comMinor incidentResolved2026-11-11 16:18 UTC
Public — what happened
Summary
Cloudflare reported a minor incident it titled Network Performance Degraded, affecting network performance near Los Angeles (LAX) and across Western North America. The company said it first became aware of the problem at 15:53 UTC on 2026-11-11 and began working on it. By 16:00 UTC Cloudflare said the issue had been identified and that a fix was being put in place. As of the latest update, the incident had not been marked resolved.
Timeline
- Started — 2026-11-11 15:53 UTC
- Investigating — 2026-11-11 15:53 UTC
- Identified — 2026-11-11 16:00 UTC
- Monitoring — 2026-11-11 16:10 UTC
- Resolved — 2026-11-11 16:18 UTC · 26 min after it started
What SquidGrid measured
SquidGrid measured 117 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Cloudflare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Cloudflare: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Cloudflare report →
More from Cloudflare
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.