Live  /  Fastly  /  Incident

Fastly: Elevated Errors for API & Configuration Management

Fastly · fastly.comResolved2026-10-06 00:47 UTC
Public — what happened

Summary

Fastly reported a problem affecting its API and Configuration Management services on October 6, 2026. According to the company, customers may have seen higher error rates and slower responses between 00:12 and 00:35 UTC, though some may have been affected less or for a shorter time. Fastly did not give a cause, and it said at 00:47 UTC that the service had been fully restored and the incident was resolved.

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 26 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.