Elevated Errors for Fastly Compute

Incident
17 April 2025, 18:29 UTC

Elevated Errors for Fastly Compute

Status: closed
Start: 17 April 2025, 17:08 UTC
End: 17 April 2025, 18:29 UTC
Duration: 1 hour 21 minutes
Affected Components:
Compute Fastly Compute Config Store KV Store Secret Store
Affected Groups:
All Public Users
Investigating

17 April 2025, 17:08 UTC

17 April 2025, 17:08 UTC

We are investigating elevated errors to our Fastly Compute service.

All other products and services are unaffected by this incident.

Identified

17 April 2025, 18:10 UTC

17 April 2025, 18:10 UTC

Our engineers have identified the contributing factor and are applying a fix to our Fastly Compute service. 

All other locations and services are unaffected.

Monitoring

17 April 2025, 18:11 UTC

17 April 2025, 18:11 UTC

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

Resolved

17 April 2025, 18:29 UTC

17 April 2025, 18:29 UTC

Our engineers have confirmed that our Compute services have been fully restored. During this incident new version deployments would have been prevented, but not lost. These deployments were delayed, but our customers should begin to see their updates propagate for their services now that this incident is resolved. Our investigation in to this incident shows a possible impact window of 17:08 to 18:05 UTC on the 17th of April 2025.

The duration of impact from this incident will vary across our customers.

Our ability to deliver Network services and all other products and services were unaffected by this incident.

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

Status Post, Created Date/Time: 2025-04-17 17:46:13 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.