Fastly incident

Retrospective: Impacted Performance in Los Angeles (BUR), Los Angeles (LAX), Los Angeles (HHR)

Resolved after 1 hour 37 minutes, affecting North America and Los Angeles (HHR) and 1 more, on September 12, 2026.

resolved Sep 12, 2026, 10:29 PM UTC

During this incident, customers may have experienced elevated errors and increased latency from 20:52 to 21:23 UTC and again from 22:16 to 22:29 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.

Started
Sep 12, 2026, 08:52 PM UTC
Resolved
Sep 12, 2026, 10:29 PM UTC
Duration
1h 37m
Detected by Pingoru
Sep 12, 2026, 08:52 PM UTC

Affected components

North AmericaLos Angeles (HHR)Los Angeles (BUR)Los Angeles (LAX)PlatformNorth AmericaPlatformNorth AmericaPlatformNorth America

Update timeline

  1. investigating Sep 12, 2026, 08:52 PM UTC

    Fastly Engineers detected a performance impacting event for traffic routed through our Los Angeles (BUR), Los Angeles (LAX), Los Angeles (HHR) data centers. This is a third-party network event, not an issue with Fastly's platform. Our engineers have taken action to route traffic away from the affected paths and restored service performance. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

  2. resolved Sep 12, 2026, 10:29 PM UTC

    During this incident, customers may have experienced elevated errors and increased latency from 20:52 to 21:23 UTC and again from 22:16 to 22:29 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.

Your product runs on more than Fastly

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →