Live / Fastly / Incident
Fastly: Cape Town (CPT), Johannesburg (JNB) with Possible Impact
Fastly · fastly.comResolved2026-10-27 18:54 UTC
Public — what happened
Summary
Fastly said its network services in the Johannesburg (JNB) and Cape Town (CPT) locations were possibly affected on October 27, 2026. In Johannesburg, the company said customers may have seen errors and slower response times from 13:55 to 17:31 UTC, while Cape Town customers were briefly affected between 14:35 and 14:54 UTC. Fastly said its engineers confirmed service was fully restored, with the update posted at 18:54 UTC, and that individual customers may have experienced less impact or a shorter disruption than those windows. Fastly did not state a cause in the text provided.
Timeline
- Started — 2026-10-27 13:55 UTC
- Resolved — 2026-10-27 18:54 UTC · 4h 59m after it started
What SquidGrid measured
SquidGrid measured 91 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 45, 2026, our weekly internet health report.