We are investigating elevated errors to multiple Points of Presence:  Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX)

Customers may experience intermittent periods of increased latency and elevated errors while we investigate into the contributing factors causing this impact.

Our engineers believe they have identified contributing factor causing the issue impacting the Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX) 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.

Engineering has deployed a fix and have confirmed recovery to Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX) POPs. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

All other services were unaffected by this incident.

Our engineers have confirmed that our Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), and Los Angeles (LAX) Points of Presence have been fully restored.

Customers may have experienced intermittent periods of increased latency and elevated errors from March 28, 2026 at 00:55 to 01:33 UTC.

This incident is resolved. Affected customers would have experienced impact to varying degrees and to a shorter duration than as set forth above. 

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.

Traffic in New York (LGA) has been temporarily rerouted.

All other locations and services are unaffected.

We are investigating elevated errors to our Platform delivery services.

Our engineers are continuing to investigate the impact to our Platform delivery services.

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 UTC.

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" 

Fastly will be adding capacity at our New York (LGA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 14 August 2024 at 08:00 UTC.

Our estimated duration is 10h. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).

The scheduled maintenance has been completed.

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

At approximately 08:00 UTC our engineers began to investigate a large traffic event impacting performance within our Europe and North America regions. 

Standard traffic engineering practices have been deployed in response to this event, in an effort to reduce the potential impact to our customers within the regions. Customer may continue to see elevated errors and latency as mitigation efforts continue to be deployed.

All other products and services are unaffected by this incident.

Our engineers are implementing adjusted mitigation strategies in our North America and Europe regions to continue to balance traffic and manage performance.

Error rates and latency have improved, although customers may still experience intermittent periods of performance impact as traffic engineering continues to be deployed.

Engineering has implemented mitigation strategies and has confirmed a gradual recovery in our North America and Europe regions. 

We are closely monitoring performance in these regions as a top priority as this event continues and will provide a final update once customer and end user experience has been fully restored.

Engineering has confirmed that Europe and North America regions have been fully restored. Customers may have experienced elevated errors and latency from 08:00 to 16:37 UTC.

This incident is resolved.

Affected customers would 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" 

We're currently investigating performance impacts in Europe, North America.

Customers may experience increased errors and latency in the affected regions.

All other locations and services are unaffected.

This issue has been identified and a fix is being implemented. 

After further investigation, Fastly Engineering has narrowed the scope of impact to the following POPs: Amsterdam (AMS), Stockholm (BMA), Denver (DEN), Frankfurt (FRA), London (LCY), Newark (EWR), Atlanta (FTY), Helsinki (HEL), Palo Alto (PAO), Paris (PAR), London (LHR), Atlanta (PDK), New York (LGA), Portland (PDX), San Jose (SJC), Los Angeles (LGB), Montreal (YUL), Toronto (YYZ). 

Customers may continue to experience latency and errors in these POPs. 

All other locations and services are unaffected.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Fastly Engineering is investigating CDN performance impacting events affecting our Milan (LIN), New York (LGA) POP. Customers may see intermittent periods of latency or elevated errors as traffic has been temporarily rerouted from the POP.

All other regions and services are currently unaffected.

Please subscribe to this status post at https://www.fastlystatus.com/incident/375953 for further updates, and if errors continue or become more frequent contact our support team at https://support.fastly.com 

We're currently investigating performance impacts in Europe, North America.

All other locations and services are unaffected.

This issue has been identified and a fix is being implemented. 

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Fastly will be performing scheduled maintenance on our New York (LGA) data center from 24 May 2023, 06:00 UTC - 24 May 2023, 11:00 UTC.

During this time frame traffic will be redirected to neighboring POPs in the region.

The scheduled maintenance has been completed.

We're investigating elevated errors in New York (LGA).

All other locations and services are unaffected

Traffic in New York (LGA) has been temporarily rerouted. All other locations and services are unaffected.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.