Live / Fastly / Incident
Fastly: Retrospective: Impacted Performance in Auckland (AKL)
Fastly · fastly.comResolved2026-10-21 12:20 UTC
Public — what happened
Summary
Fastly reported a problem affecting performance at its Auckland (AKL) location, which it described in a retrospective post. The company said customers may have seen more errors than usual between 10:20 and 12:20 UTC on 2026-10-21. Fastly marked the incident as resolved at 12:20 UTC and did not state a cause, and it directed anyone wanting more details to contact its Support team.
Timeline
- Started — 2026-10-21 10:20 UTC
- Resolved — 2026-10-21 12:20 UTC · 2h after it started
What SquidGrid measured
SquidGrid measured 69 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 44, 2026, our weekly internet health report.