Update: Confirmed third-party network event impacting our Los Angeles region
Update: Confirmed third-party network event impacting our Los Angeles region
02 September 2026, 16:08 UTC
02 September 2026, 16:08 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.
02 September 2026, 16:10 UTC
02 September 2026, 16:10 UTC
Customers may also see possible degradation in our Los Angeles (BUR) POP.
02 September 2026, 16:13 UTC
02 September 2026, 16:13 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.
02 September 2026, 16:28 UTC
02 September 2026, 16:28 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.
02 September 2026, 17:29 UTC
02 September 2026, 17:29 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.
02 September 2026, 18:56 UTC
02 September 2026, 18:56 UTC
The fix has been successfully deployed, and we have observed a recovery of network performance for affected traffic paths.
Our team will continue to monitor the platform to ensure stability before we resolve this incident.