Fastly incident

Retrospective: Impacted Performance in Tokyo (NRT), Chicago (CHI), Columbus (CMH), Los Angeles (BUR), Phoenix (PHX), Toronto (YYZ), Los Angeles (LAX), Los Angeles (HHR)

Notice Resolved View vendor source →

Fastly experienced a notice incident on August 23, 2026 affecting North America and Chicago (CHI) and 1 more component, lasting 45m. The incident has been resolved; the full update timeline is below.

Started
Aug 23, 2026, 01:06 AM UTC
Resolved
Aug 23, 2026, 01:51 AM UTC
Duration
45m
Detected by Pingoru
Aug 23, 2026, 01:06 AM UTC

Affected components

North AmericaChicago (CHI)Columbus (CMH)Los Angeles (HHR)Los Angeles (BUR)Los Angeles (LAX)Phoenix (PHX)Toronto (YYZ)AsiaTokyo (NRT)

Update timeline

  1. investigating Aug 23, 2026, 01:06 AM UTC

    Between 01:06 UTC and 01:51 UTC on August 23, 2026, Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT), Chicago (CHI), Columbus (CMH), Los Angeles (BUR), Phoenix (PHX), Toronto (YYZ), Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs). During this time, customers with traffic routed through these locations may have experienced elevated error rates or latency. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

  2. resolved Aug 23, 2026, 01:51 AM UTC

    This incident has been resolved.