London (LCY)

02 May 2025, 03:25 UTC
Platform Europe London (LCY)
 
02 May 2025, 03:25 UTC

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

All other products and services are unaffected by this incident.

 
02 May 2025, 04:09 UTC

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

 
02 May 2025, 04:12 UTC

Engineering has confirmed that our London (LCY) POP has been fully restored. Customers may have experienced elevated errors and latency from 03:25 to 03:42 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-05-02 03:48:08 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.


Platform Europe Amsterdam (RTM) London (LCY)
 
16 April 2025, 19:27 UTC

We are investigating elevated errors to our Amsterdam (RTM) Point of Presence (POP).

 
16 April 2025, 20:25 UTC

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

All other locations and services are unaffected.

 
16 April 2025, 20:26 UTC

Engineering has confirmed the impact to Amsterdam (RTM) (POP) has been mitigated.

 
16 April 2025, 21:27 UTC

Engineering has confirmed that Amsterdam (RTM) (POP) has been fully restored. Customers may have experienced elevated errors and latency  from 19:27 to 20:44  UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-04-16 20:18:45 UTC

Update added by Escalation Management on 16th of April 2025

Retrospective investigations have identified similar degraded performance to Compute Services within the LCY POP as a result of this incident. This information has been added to ensure data accuracy and transparency for affected customers.



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.


Platform Europe London (LCY) London (LHR) Manchester (MAN) Paris (CDG) Paris (PAR)
 
28 January 2025, 17:15 UTC

We're investigating possible performance impact affecting the data centers within the Europe region.

All other locations and services are unaffected


 
28 January 2025, 19:22 UTC

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.

 
28 January 2025, 19:33 UTC

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

 
28 January 2025, 21:03 UTC

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.


Platform Europe London (LCY) London (LHR)
 
14 November 2024, 15:34 UTC

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.


 
14 November 2024, 18:05 UTC

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.

 
14 November 2024, 19:18 UTC

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.


05 September 2024, 19:48 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Brussels (BRU) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dubai (FJR) Copenhagen (CPH) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Dublin (DUB) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (FRA) Perth (PER) Atlanta (PDK) Frankfurt (HHN) Hong Kong (HKG) Rio de Janeiro (GIG) Boston (BOS) Kolkata (CCU) Helsinki (HEL) Sydney (SYD) Santiago (SCL) Calgary (YYC) London (LCY) Kuala Lumpur (KUL) Wellington (WLG) Sāo Paulo (CGH) Chicago (CHI) London (LON) Manila (MNL) Sao Paulo (GRU) Mumbai (BOM) London (LHR) New Delhi (DEL) Lisbon (LIS) Osaka (ITM) Madrid (MAD) Seoul (ICN) Manchester (MAN) Marseille (MRS) Singapore (QPG) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Tokyo (HND) Denver (DEN) Palermo (PMO) Tokyo (NRT) Detroit (DTW) Tokyo (TYO) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

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

 
05 September 2024, 22:01 UTC

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

 
05 September 2024, 23:00 UTC

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

 
05 September 2024, 23:34 UTC

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.

 
06 September 2024, 00:48 UTC

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

Platform Europe London (LCY) London (LHR)
 
31 August 2024, 08:41 UTC

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

 
31 August 2024, 17:18 UTC

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

 
31 August 2024, 18:16 UTC

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

 
31 August 2024, 20:07 UTC

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

 
31 August 2024, 20:12 UTC

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

Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Atlanta (PDK) Frankfurt (HHN) Boston (BOS) Helsinki (HEL) Calgary (YYC) London (LCY) Chicago (CHI) London (LON) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Denver (DEN) Palermo (PMO) Detroit (DTW) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
23 July 2024, 12:48 UTC

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.

 
23 July 2024, 14:29 UTC

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.

 
23 July 2024, 16:37 UTC

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.

 
23 July 2024, 23:52 UTC

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

Platform Europe London (LCY)
 
16 June 2024, 15:48 UTC

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.

24 May 2024, 07:00 UTC
Platform Europe London (LCY)
 
24 May 2024, 07:00 UTC

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

 
24 May 2024, 18:05 UTC

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.

 
24 May 2024, 19:52 UTC

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

 
24 May 2024, 21:10 UTC

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.

03 April 2024, 17:56 UTC
Platform Europe London (LCY)
 
03 April 2024, 17:56 UTC

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

 
03 April 2024, 18:23 UTC

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


 
03 April 2024, 19:54 UTC

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

 
03 April 2024, 20:06 UTC

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.