Elevated Errors for Fastly Application

Incident
10 November 2025, 17:53 UTC

Elevated Errors for Fastly Application

Status: closed
Start: 10 November 2025, 15:42 UTC
End: 10 November 2025, 17:53 UTC
Duration: 2 hours 11 minutes
Affected Components:
Fastly Fastly Application API & Configuration Management Notification Center API Services Configuration Management Services
Affected Groups:
All Public Users
Investigating

10 November 2025, 15:42 UTC

10 November 2025, 15:42 UTC

We are investigating elevated errors to our Fastly Application.  Customers may experience an error when attempting to access Fastly Next-Gen WAF (NGWAF) configuration pages.

All other products and services are unaffected by this incident.

Identified

10 November 2025, 17:35 UTC

10 November 2025, 17:35 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.

Our ability to deliver Network and Security products, along with API services for our Fastly Application are not affected by this incident.

Monitoring

10 November 2025, 17:41 UTC

10 November 2025, 17:41 UTC

Engineering has confirmed the impact to the Fastly Application has been mitigated.

Resolved

10 November 2025, 17:53 UTC

10 November 2025, 17:53 UTC

Engineering has confirmed that Fastly Application has been fully restored. Customers may have experienced elevated errors in our NGWAF settings and configuration webpages from 15:42 to 17:19 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback

Status Post, Created Date/Time: 2025-11-10 17:15:42 UTC 



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.