Elevated Errors for Fastly Application

Incident
08 October 2024, 01:18 UTC

Elevated Errors for Fastly Application

Status: closed
Start: 07 October 2024, 23:12 UTC
End: 08 October 2024, 01:18 UTC
Duration: 2 hours 6 minutes
Affected Components:
Fastly Observability Fastly Application Historical Stats Real-time Analytics API & Configuration Management Message Portal API Services Configuration Management Services
Affected Groups:
All Public Users
Investigating

07 October 2024, 23:12 UTC

07 October 2024, 23:12 UTC

We are investigating elevated errors to our Fastly Application, Historical Stats, and Real-time Analytics services.

All other products and services are unaffected by this incident.


Update

08 October 2024, 00:05 UTC

08 October 2024, 00:05 UTC

Our engineers are continuing to investigate elevated errors to our Fastly Application, Historical Stats, Real-time Analytics services.

Identified

08 October 2024, 00:54 UTC

08 October 2024, 00:54 UTC

Our engineers have identified the contributing factor and are applying a fix to our Fastly Application, Historical Stats, Real-time Analytics services.

All other locations and services are unaffected.

Monitoring

08 October 2024, 01:04 UTC

08 October 2024, 01:04 UTC

Engineering has confirmed the impact to our Fastly Application, Historical Stats, Real-time Analytics services have been mitigated.

Resolved

08 October 2024, 01:18 UTC

08 October 2024, 01:18 UTC

Engineering has confirmed that our Fastly Application, Historical Stats, Real-time Analytics services have been fully restored. Customers may have experienced elevated errors and issues when attempting access these services from 23:12 on the 7th of October to 00:55 UTC on the 8th of October .

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: 2024-10-07 23:26:03 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.