Elevated Errors for Fastly Application
Elevated Errors for Fastly Application
09 February 2026, 18:36 UTC
09 February 2026, 18:36 UTC
We are investigating elevated errors to our Fastly Application services.
All other products and services are unaffected by this incident.
09 February 2026, 19:48 UTC
09 February 2026, 19:48 UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application 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.
09 February 2026, 20:22 UTC
09 February 2026, 20:22 UTC
Engineering has deployed a fix and have confirmed a gradual recovery to both manual configuration update and those made via API request. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
This incident did contain network impact, in that configuration updates could not be made. However, our ability to deliver network and security services for active configurations were unaffected by this incident.
09 February 2026, 21:01 UTC
09 February 2026, 21:01 UTC
We have reopened this incident as our engineers have identified some lingering effects impacting a small subset of requests. While we have already seen a broad recovery, we are deploying additional mitigations to ensure that configuration updates are fully restored for all customers.
We are continuing to monitor the situation closely and will provide another update once we have confirmed that all customer services are back to 100% functionality.
Impact:
Customers may still experience intermittent 5xx/4xx errors when attempting to make configuration updates via manage.fastly.com or the API. Existing services remain unaffected and continue to operate normally.
10 February 2026, 04:47 UTC
10 February 2026, 04:47 UTC
Engineering has confirmed that the Fastly Application component has been fully restored. Customers may have experienced elevated 5xx/4xx errors when attempting configuration updates from 18:36 UTC on Monday 9 February 2026 to 03:45 UTC on Tuesday 10 February 2026 .
This incident is resolved.Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
Final Confirmation: We have confirmed with all customers known to be experiencing impact that their services and configuration update capabilities are now fully restored. All other products and services remained unaffected by this incident throughout its duration.