Fastly Application Performance Issues

Incident
22 October 2025, 14:55 UTC

Fastly Application Performance Issues

Status: closed
Start: 22 October 2025, 13:56 UTC
End: 22 October 2025, 14:55 UTC
Duration: 59 minutes
Affected Components:
Fastly Fastly Application API & Configuration Management Notification Center API Services Configuration Management Services
Affected Groups:
All Public Users
Investigating

22 October 2025, 13:56 UTC

22 October 2025, 13:56 UTC

We are currently investigating performance issues affecting the availability of manage.fastly.com. CDN delivery, stats aggregation, and all other data plane services are unaffected.

Identified

22 October 2025, 14:32 UTC

22 October 2025, 14:32 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.

Monitoring

22 October 2025, 14:34 UTC

22 October 2025, 14:34 UTC

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

Resolved

22 October 2025, 14:55 UTC

22 October 2025, 14:55 UTC

Engineering has confirmed that the Fastly Application service has been fully restored. Customers may have experienced the following issues: 4xx errors, redirect loops or inability to initiate new login sessions  from 13:56  to 14:21 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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

Status Post, Created Date/Time: 2025-10-22 14:20:19 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.