Fastly incident

Elevated Errors for Compute

Major Resolved View vendor source →

Fastly experienced a major incident on September 9, 2026 affecting Fanout and Fastly Compute and 1 more component, lasting 3h 37m. The incident has been resolved; the full update timeline is below.

Started
Sep 09, 2026, 06:28 PM UTC
Resolved
Sep 09, 2026, 10:05 PM UTC
Duration
3h 37m
Detected by Pingoru
Sep 09, 2026, 06:28 PM UTC

Affected components

FanoutFastly ComputeConfig StoreKV StoreSecret StoreAI AcceleratorEdge Cloud ServicesWebsocketsComputeEdge Cloud Services

Update timeline

  1. investigating Sep 09, 2026, 07:14 PM UTC

    We are investigating an issue causing elevated 5xx errors for some customers using our Compute services. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the next hour. All other products and services are unaffected by this incident.

  2. investigating Sep 09, 2026, 07:20 PM UTC

    Our engineers believe they have identified the contributing factor causing the issue impacting our Compute services. Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.

  3. monitoring Sep 09, 2026, 08:33 PM UTC

    Engineering has deployed a fix and have confirmed a gradual recovery to Compute services. We will continue to monitor until we’ve confirmed that customer experience has been fully restored. All other products and services remain unaffected by this incident.

  4. resolved Sep 09, 2026, 10:05 PM UTC

    Engineering has confirmed that Compute services has been fully restored. Customers may have experienced elevated 5xx errors from 18:28 to 21:52 UTC. This incident is resolved. Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team. Status Post, Created Date/Time: 2026-09-09 19:15:48 UTC