Fastly incident

Elevated Errors for Fastly Application

Major Resolved View vendor source →

Fastly experienced a major incident on June 25, 2026 affecting Fastly Application and API & Configuration Management and 1 more component, lasting 1h 34m. The incident has been resolved; the full update timeline is below.

Started
Jun 25, 2026, 05:25 PM UTC
Resolved
Jun 25, 2026, 06:59 PM UTC
Duration
1h 34m
Detected by Pingoru
Jun 25, 2026, 05:25 PM UTC

Affected components

Fastly ApplicationAPI & Configuration ManagementAPI ServicesConfiguration Management ServicesNotification CenterFastlyFastly ApplicationAPI & Configuration ManagementNotification CenterAPI Services

Update timeline

  1. investigating Jun 25, 2026, 06:13 PM UTC

    We are investigating elevated errors with product enablements in our Fastly Application. All other products and services are unaffected by this incident.

  2. investigating Jun 25, 2026, 06:27 PM 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.

  3. monitoring Jun 25, 2026, 06:28 PM UTC

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

  4. resolved Jun 25, 2026, 06:59 PM UTC

    Engineering has confirmed that Fastly Application service has been fully restored. Customers may have experienced failures with enablement, disablement, and configuration operations, as well as enablement checks from 17:25 to 18:22 UTC. This incident is resolved. 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. Status Post, Created Date/Time: 2026-06-25 18:15:32 UTC