Elevated Errors for Fastly Compute Services

Incident
26 September 2024, 19:29 UTC

Elevated Errors for Fastly Compute Services

Status: closed
Start: 29 July 2024, 21:12 UTC
End: 26 September 2024, 19:29 UTC
Duration: 58 days 22 hours 17 minutes
Affected Components:
Compute Fastly Compute Config Store KV Store Secret Store
Affected Groups:
All Public Users
Investigating

29 July 2024, 21:12 UTC

29 July 2024, 21:12 UTC

Status post create date/time: 2024-09-26 17:26:36 UTC

We are currently investigating into intermittent timeout errors and increased latency for end-users attempting to connect to our Fastly Compute services.


Note: at the close of this incident, our Customer Escalation Management team will update the start date/time to reflect the possible impact window for our customer records. The status post create date/time will remain logged in this message body to reflect our Acute Incident Response practices.


Identified

26 September 2024, 17:29 UTC

26 September 2024, 17:29 UTC

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

All other services are unaffected.

Identified

26 September 2024, 18:17 UTC

26 September 2024, 18:17 UTC

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Fastly Compute services.

All other services are unaffected.

Monitoring

26 September 2024, 18:49 UTC

26 September 2024, 18:49 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to our Fastly Compute services. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

All other services were unaffected by this incident.


Resolved

26 September 2024, 19:29 UTC

26 September 2024, 19:29 UTC

Engineering has confirmed that our Fastly Compute services have been fully restored. Our customers' end-users may have experienced brief periods of intermittent timeout errors and latency when using Compute services from the 29th of July 2024 at 21:12 UTC to 26th of September 2024 at 19:00 UTC.

This incident is resolved.

Due to the intermittent nature of this incident, affected end-users would have experienced impact to varying degrees and to a shorter period of duration than as set forth above.

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