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" 

Fastly Engineers detected a performance impacting event affecting the London (LCY) data center.

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

We are investigating elevated errors and latency to our London (LCY) Point of Presence (POP).

Our engineers have identified the contributing factor and are applying a fix to our London (LCY) Point of Presence (POP).

All other locations and services are unaffected.

Engineering has confirmed the impact to London (LCY) Point of Presence (POP) has been mitigated.

Engineering has confirmed that London (LCY) Point of Presence (POP) has been fully restored. Customers may have experienced increased latency from 07:00 to 18:32 UTC.

This incident is resolved.

We are investigating a performance impact to our London (LCY) POP. 

Our engineers have identified the contributing factor and are applying a fix to London (LCY) POP.

Engineering has confirmed the impact to London (LCY) POP has been mitigated.

Engineering has confirmed that London (LCY) POP has been fully restored. Customers may have experienced some latency from 16:24 to 19:34 UTC.

This incident is resolved.

Fastly will be adding capacity at our London (LCY) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 02 April 2024 at 00:00 UTC.

Our estimated duration is 4h. 

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.

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 will be adding capacity at our London (LCY) Point of Presence (POP). End-users may observe connection resets as traffic is migrated onto new hardware, starting on 18 July 2023 at 01:00 UTC. 

Our estimated duration is 4h.

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 at https://support.fastly.com. 

In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.

The scheduled maintenance has been completed.

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.

We're currently investigating potential impact to performance with our CDN services.

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

Fastly will be adding capacity at our London (LCY) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 16 November 2022 at 00:00 UTC UTC.

• Our estimated duration is 240 minutes

In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please be sure to check 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).