Fastly incident
Update: Confirmed third-party network event impacting our Los Angeles region
Fastly experienced a major incident on September 2, 2026 affecting North America and Los Angeles (HHR) and 1 more component, lasting 1d 6h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 02, 2026, 04:08 PM UTC
We're investigating possible performance impact affecting the Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs). All other locations and services are unaffected.
- investigating Sep 02, 2026, 04:10 PM UTC
Customers may also see possible degradation in our Los Angeles (BUR) POP.
- investigating Sep 02, 2026, 04:13 PM UTC
Our engineers believe they have identified the contributing factor causing the issue impacting origin pull and shielding performance for customers with traffic routed through the affected region. Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.
- monitoring Sep 02, 2026, 04:28 PM UTC
We are currently monitoring a network issue caused by a third-party network provider serving the Los Angeles region. This is a third-party network event, not an issue with Fastly's platform. Our engineers have taken action to route traffic away from the affected paths and are coordinating directly with the third-party provider as they work to restore full service. For additional information about this network event, please see: https://ecogent.cogentco.com/network-status Customers with traffic paths through the affected region may see intermittent delays or errors for origin pull or shielding traffic. All other products and services are unaffected. Workaround & next steps: No action is needed on your part. We will share another update here as the third-party provider makes progress, or within the hour.
- monitoring Sep 02, 2026, 05:29 PM UTC
Our engineering teams have deployed traffic engineering changes that are successfully mitigating the network congestion affecting origin pull and shielding traffic in the Los Angeles region. Error rates and latency have returned to nominal levels for the majority of affected traffic. We continue to work closely with our third-party network provider while they resolve the underlying issue. Our team will continue to monitor the platform closely to ensure continued stability before we resolve this incident.
- monitoring Sep 02, 2026, 06:56 PM UTC
The fix has been successfully deployed, and we have observed a recovery of network performance for affected traffic paths. Error rates and latency have returned to nominal levels. Our team will continue to monitor the platform to ensure stability before we resolve this incident.
- resolved Sep 03, 2026, 08:18 PM UTC
Engineering has confirmed that network performance for traffic routed through the Los Angeles (LAX), Los Angeles (HHR) and Los Angeles (BUR) POP's has been fully restored. Customers may have experienced intermittent delays or errors on origin pull and shielding traffic from September 2, 2026, 13:43 UTC to September 3, 2026, 09:11 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-09-02 16:09:33 UTC