Fastly incident
Elevated Errors for API & Configuration Management
Fastly experienced a major incident on August 11, 2026 affecting Fastly Control Panel and API & Configuration Management and 1 more component, lasting 3h 34m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 11, 2026, 06:20 AM UTC
We are investigating elevated errors to our API & Configuration Management service All other products and services are unaffected by this incident.
- investigating Aug 11, 2026, 08:12 AM UTC
Our engineers believe they have identified the contributing factor causing elevated 5xx errors and slowness impacting api.fastly.com and manage.fastly.com. Our engineers are actively working on a fix. We will provide another update within the hour.
- monitoring Aug 11, 2026, 08:14 AM UTC
Our engineers have deployed a fix and are actively monitoring for improvements. We have not observed any additional errors since the fix was applied. We will provide a further update once we've confirmed full resolution, or within the next hour.
- investigating Aug 11, 2026, 09:10 AM UTC
We are investigating a reoccurrence of the issue causing elevated 5xx errors and slowness for api.fastly.com and manage.fastly.com. Our engineers are actively working to diagnose the contributing factor and prevent further recurrence. We will provide another update as more information becomes available or within the next hour.
- monitoring Aug 11, 2026, 09:37 AM UTC
Following the reoccurrence, our engineers have redeployed a fix and are actively monitoring for improvements. We have not observed any additional errors since the fix was applied. We will provide a further update once we've confirmed full resolution, or within the next hour.
- resolved Aug 11, 2026, 09:54 AM UTC
This incident has been resolved. Between 06:20 and 09:27 UTC, customers may have experienced elevated 5xx errors and slowness for api.fastly.com and manage.fastly.com. Our engineers identified the contributing factor and applied a fix, and normal service has been confirmed for an extended monitoring period. We apologize for any disruption this may have caused. If you continue to experience issues, please reach out to support. 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-08-11 07:55:26 UTC