Resolved after 1 hour 57 minutes, affecting Fastly Control Panel and API & Configuration Management and 1 more, on July 31, 2026.
Engineering has confirmed that api.fastly.com and manage.fastly.com have been fully restored. Customers may have experienced possible errors, including elevated 503 responses and slow or failed access, from 06:03 to 07:37 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-07-31 07:12:55 UTC
Affected components
Update timeline
- investigating Jul 31, 2026, 06:03 AM UTC
We are investigating an issue causing elevated 503 errors and slowness affecting api.fastly.com and manage.fastly.com. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available.
- monitoring Jul 31, 2026, 07:39 AM UTC
We have observed a recovery of our API and configuration management services (api.fastly.com and manage.fastly.com). Error rates and response times have returned to nominal levels. Our engineers are continuing to monitor the platform closely to ensure stability before we resolve this incident. All other products and services are unaffected by this incident.
- resolved Jul 31, 2026, 08:00 AM UTC
Engineering has confirmed that api.fastly.com and manage.fastly.com have been fully restored. Customers may have experienced possible errors, including elevated 503 responses and slow or failed access, from 06:03 to 07:37 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-07-31 07:12:55 UTC
Your product runs on more than Fastly
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services