London (LHR)

Platform North America Europe Amsterdam (AMS) Brussels (BRU) Ashburn (IAD) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Frankfurt (HHN) Atlanta (PDK) Helsinki (HEL) Boston (BOS) London (LCY) Calgary (YYC) London (LON) Chicago (CHI) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Milan (LIN) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Denver (DEN) Paris (CDG) Detroit (DTW) Paris (PAR) Rome (FCO) Gainesville (GNV) Sofia (SOF) Honolulu (HNL) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) 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 (LHR)
 
08 July 2024, 23:00 UTC

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

 
09 July 2024, 03:00 UTC

The scheduled maintenance has been completed.

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

05 June 2024, 23:12 UTC
Platform Europe London (LHR)
 
05 June 2024, 23:12 UTC

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

 
06 June 2024, 00:32 UTC

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


 
06 June 2024, 01:09 UTC

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

 
06 June 2024, 01:32 UTC

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

Platform Europe London (LHR)
 
30 May 2024, 00:00 UTC

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

 
30 May 2024, 06:00 UTC

The scheduled maintenance has been completed.

28 August 2023, 19:47 UTC
Platform North America Europe Amsterdam (AMS) Frankfurt (FRA) Atlanta (PDK) Helsinki (HEL) London (LCY) London (LHR) Denver (DEN) Paris (PAR) Stockholm (BMA) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Portland (PDX) San Jose (SJC) Toronto (YYZ)
 
28 August 2023, 19:47 UTC

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.

 
28 August 2023, 20:00 UTC

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

 
28 August 2023, 20:05 UTC

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.

 
28 August 2023, 21:07 UTC

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

 
28 August 2023, 21:35 UTC

This incident has been resolved.

29 June 2023, 18:46 UTC
Platform North America Europe Amsterdam (AMS) Brussels (BRU) Ashburn (IAD) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Frankfurt (HHN) Atlanta (PDK) Helsinki (HEL) Boston (BOS) London (LCY) Calgary (YYC) London (LON) Chicago (CHI) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Milan (LIN) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Denver (DEN) Detroit (DTW) Paris (PAR) Rome (FCO) Gainesville (GNV) Sofia (SOF) Honolulu (HNL) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) 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)
 
29 June 2023, 18:46 UTC

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

All other locations and services are unaffected.

 
29 June 2023, 19:56 UTC

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

 
29 June 2023, 21:54 UTC

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

 
29 June 2023, 23:54 UTC

This incident has been resolved.

Platform Europe London (LHR)
 
28 June 2023, 10:16 UTC

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.

 
28 June 2023, 11:13 UTC

This incident has been resolved.

19 January 2023, 23:05 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Brussels (BRU) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dublin (DUB) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Sydney (SYD) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) Chicago (CHI) Sao Paulo (GRU) London (LHR) Manila (MNL) Mumbai (BOM) Lisbon (LIS) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Seoul (ICN) Milan (LIN) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Detroit (DTW) Rome (FCO) Tokyo (TYO) Gainesville (GNV) Sofia (SOF) Honolulu (HNL) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) 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)
 
19 January 2023, 23:05 UTC

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

 
19 January 2023, 23:06 UTC

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

 
19 January 2023, 23:48 UTC
On the 19th of January at 23:00 UTC a configuration change was deployed which impacted performance to global CDN delivery. Fastly Engineering reverted the change resulting in immediate recovery at 23:06 UTC. Fastly's Customer Incident Response team is currently preparing a Fastly Service Advisory of today's incident, and will be made available to Fastly Customers.
Platform Europe London (LHR)
 
18 November 2022, 00:00 UTC

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

  • Our estimated duration is 480 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).

04 November 2022, 00:00 UTC
Platform Europe London (LHR)
 
04 November 2022, 00:00 UTC

Fastly will be performing scheduled maintenance on our London (LHR) data center from 04 November 2022, 00:00 UTC - 04 November 2022, 04:00 UTC.

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

 
04 November 2022, 00:00 UTC

Scheduled maintenance is currently in progress. We will provide updates as necessary.

 
04 November 2022, 08:17 UTC

The scheduled maintenance has been completed.