Fastly experienced a major incident on May 20, 2026 affecting Fastly Application and API & Configuration Management and 1 more component, lasting 1h 44m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 20, 2026, 07:28 PM UTC
We are investigating an issue causing errors and timeouts for customers using the Fastly API (api.fastly.com). 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.
- investigating May 20, 2026, 08:02 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the API Services status page component . 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.
- monitoring May 20, 2026, 08:18 PM UTC
Engineering has confirmed the impact to API Services has been mitigated.
- resolved May 20, 2026, 08:19 PM UTC
Our engineers have confirmed that the Fastly API (api.fastly.com) has been fully restored. Customers may have experienced elevated 503 errors, increased timeouts, or failures on API calls and Terraform builds from approximately 18:35 to 19:37 UTC. As a side effect of the API degradation, the following areas were also impacted during this period: Next-Gen WAF (NGWAF) rule and configuration updates may have been delayed in taking effect Fastly account sign-up may have experienced disruptions Fastly Support Portal functionality may have been affected Service has been fully restored. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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-05-20 19:31:03 UTC