Fastly experienced a notice incident on May 17, 2026 affecting Asia and Ambala (QAA) and 1 more component, lasting 1h 59m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 17, 2026, 01:51 AM UTC
Traffic in Ambala (QAA) has been temporarily rerouted. All other locations and services are unaffected.
- investigating May 17, 2026, 02:59 AM UTC
Update: The responding escalation manager erroneously marked the incorrect status page component in their original post which caused the wrong title to appear within customer support chat and email threads. This was corrected to display the proper component (Ambala (QAA)). All other components, locations and services were unaffected by this event.
- resolved May 17, 2026, 03:26 AM UTC
Engineering has confirmed that Ambala (QAA) POP has been fully restored. Customers may have experienced elevated intermittent errors or periods of latency while traffic was rerouted from 01:27 to 03:26 UTC. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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-05-17 01:53:50 UTC