We're performing maintenance

Fastly Engineers detected a performance impacting event for traffic routed through our Los Angeles (BUR), Los Angeles (LAX), Los Angeles (HHR) data centers.

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 restored service performance.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

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.

Customers may also see possible degradation in our Los Angeles (BUR) POP.

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.

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.

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.

The fix has been successfully deployed, and we have observed a recovery of network performance for affected traffic paths.

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.

Between 01:06 UTC and 01:51 UTC on August 23, 2026, Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT), Chicago (CHI), Columbus (CMH), Los Angeles (BUR), Phoenix (PHX), Toronto (YYZ), Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs).

During this time, customers with traffic routed through these locations may have experienced elevated error rates or latency. All other data centers and services were unaffected.

The issue has been resolved and we are monitoring performance closely.

We're investigating possible performance impact affecting the Amsterdam (AMS), Milan (MXP), Sofia (SOF), Fujairah (FJR), Osaka (ITM), Singapore (QPG), Tokyo (NRT), Tokyo (TYO), Los Angeles (BUR), Paris (PAR), Singapore (SIN), Amsterdam (RTM) data center.

All other locations and services are unaffected.

Our engineers are continuing to investigate confirmed periods of increased latency and elevated errors to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs.

Our engineers believe they have identified contributing factor causing the issue impacting the Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery. 

Engineering has confirmed the impact to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs has been mitigated and services are fully restored.

Engineering has confirmed that all POPs have been fully restored. Customers may have experienced elevated errors from 13:35 UTC to 14:15 UTC, a duration of 40 minutes on the 11th of December 2025. 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: 2025-12-11 14:34:14 UTC 

Fastly Engineers detected a performance impacting event affecting the Phoenix (PHX), Los Angeles (LAX), Los Angeles (HHR) data centers.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

As part of Fastly’s global network expansion, we will be adding Los Angeles (HHR) data center to Fastly's North America network. 

Traffic served by our Los Angeles (HHR) data center will be aggregated into our North America region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Los Angeles (HHR). As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https:/www.fastly.com/pricing.

The scheduled maintenance has been completed.

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