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

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 data centers within the Europe region.

All other locations and services are unaffected

Our engineers have identified the contributing factor and have applied a fix. Our investigation has confirmed that impact within the Europe region was limited to the London (LCY and LHR), Manchester (MAN) and Paris (CDG and PAR) data centers.

All other locations and services are unaffected.

Engineering has confirmed the impact to Europe data centers has been mitigated.

Engineering has confirmed that our Europe POPs have been fully restored. Customers may have experienced performance degradation from 17:15 to 19:00 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" 

Status Post, Created Date/Time: 2025-01-28 19:18:00 UTC 

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 London (LHR) has been temporarily rerouted.

All other locations and services are unaffected.

We are investigating elevated errors to our London (LCY) and London (LHR) POPs for Compute.

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our London (LCY) and London (LHR) service for Compute.

All other products and services are unaffected by this incident.

Engineering has confirmed that London (LCY), London (LHR) POPs has been fully restored. Customers may have experienced latency for Compute from 15:34 to 19:02 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2024-11-14 18:02:38 UTC 

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.

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" 

We are investigating elevated errors to our London (LCY), London (LHR) Points of Presence (POPs).

Our engineers have identified the contributing factor and are applying a fix to our London (LCY), London (LHR) POPs.

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our London (LCY), London (LHR) POPs.

Engineering has confirmed the impact to our London (LCY), London (LHR) POPs has been mitigated.

Engineering has confirmed that our London (LCY), London (LHR) POPs have been fully restored. Customers may have experienced elevated errors and latency from 08:41 to 18:29 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" 

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 will be adding capacity at our London (LHR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 09 July 2024 at 23: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.

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

We are investigating elevated errors to our London (LHR) Point of Presence (POP).

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

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

Engineering has confirmed that London (LHR) POP has been fully restored. Customers may have experienced elevated errors and latency from 23:12 on the 5th of June to 00:45 on the 6th of June 2024 UTC.

This incident is resolved.

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

Fastly will be adding capacity at our London (LHR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on the 30th of May 2024 at 00:00 to 06:00 UTC.

Our estimated duration is 6 hours. 

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 configuration 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).

The scheduled maintenance has been completed.