Fastly incident

KV Store, Object Storage with Possible Impact

Major Resolved View vendor source →

Fastly experienced a major incident on April 24, 2026 affecting Object Storage and Fastly Compute and 1 more component, lasting 18h 39m. The incident has been resolved; the full update timeline is below.

Started
Apr 24, 2026, 09:42 PM UTC
Resolved
Apr 25, 2026, 04:21 PM UTC
Duration
18h 39m
Detected by Pingoru
Apr 24, 2026, 09:42 PM UTC

Affected components

Object StorageFastly ComputeKV StoreNetwork ServicesObject Storage

Update timeline

  1. investigating Apr 24, 2026, 09:42 PM UTC

    We are investigating elevated errors to our KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions. All other products and services are unaffected by this incident.

  2. investigating Apr 25, 2026, 02:05 PM UTC

    Our engineers believe they have identified contributing factor causing the issue impacting the KV Store, Object Storage for Asia Pacific (APAC) and South Asia regions. We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery. All other products and services are unaffected by this incident.

  3. monitoring Apr 25, 2026, 02:35 PM UTC

    Engineering has confirmed the impact to KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions has been mitigated.

  4. resolved Apr 25, 2026, 04:21 PM UTC

    Engineering has confirmed that KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions has been fully restored. Customers may have experienced increased latency observed when accessing KV Store and Object Storage from 14:42 UTC on April 24, 2026 to 14:49 UTC on April 25, 2026 . 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-04-25 16:19:58 UTC