Live / Fastly / Incident
Fastly: Retrospective: Impacted Performance in Auckland (AKL), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Chicago (CHI), Columbus (CMH), Dallas (DFW), Denver (DEN), De
Fastly · fastly.comResolved2026-11-04 02:10 UTC
Public — what happened
Summary
Fastly reported an incident on its status page. It has been resolved.
Timeline
- Started — 2026-11-04 01:04 UTC
- Resolved — 2026-11-04 02:10 UTC · 1h 06m after it started
What SquidGrid measured
SquidGrid measured 40 internet paths into Fastly’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 Fastly 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 Fastly: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Fastly report →
More from Fastly
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.