Live  /  Fastly  /  Incident

Fastly: Cape Town (CPT), Johannesburg (JNB) with Possible Impact

Fastly · fastly.comResolved2026-10-27 17:28 UTC
Public — what happened

Summary

Fastly reported a possible impact on its Cape Town (CPT) and Johannesburg (JNB) locations, with the incident starting at 15:46 UTC on 2026-10-27. The company said customers in Cape Town were temporarily affected between 14:35 and 14:54 UTC, and that service there has fully recovered. For Johannesburg, Fastly said its engineers took steps to recover the affected systems and were gradually returning traffic to the site. As of its 17:28 UTC update, which marked the incident resolved, Fastly said some customers might still see intermittent problems while things stabilize and that the team was continuing to monitor.

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 44 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 45, 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.