Live  /  Fastly  /  Incident

Fastly: Retrospective: Impacted Performance in Cape Town (CPT)

Fastly · fastly.comResolved2026-10-10 03:57 UTC
Public — what happened

Summary

Fastly posted a retrospective notice about degraded performance at its Cape Town (CPT) location on October 10, 2026. The company said customers may have seen higher-than-normal error rates between 03:12 and 03:57 UTC that day. Fastly did not name a cause and reported the issue as resolved, directing anyone wanting more details to its support team.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

What SquidGrid measured

SquidGrid measured 28 internet paths into Fastly’s network during this incident. None of them ran meaningfully slower than the same paths the day before.

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 see
Customers 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 42, 2026, our weekly internet health report.

The full archive is on the Fastly status & history page.

Related: Fastly status & history. SquidGrid is not affiliated with Fastly.