Live  /  Fastly  /  Incident

Fastly: Elevated Errors for Queretaro (QRO)

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

Summary

Fastly reported that customers may have seen more errors and slower responses on requests handled through its Queretaro (QRO) location. The company listed the affected window as running from 23:21 UTC on 28 October 2026 to 08:54 UTC on 29 October 2026, though its status page shows the incident starting at 02:04 UTC and being marked resolved at 03:32 UTC on 29 October. Fastly said the incident is resolved, did not state a cause, and directed people 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 40 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.