Between 13:00 UTC and 19:12 UTC on June 25, 2026, customers routing traffic through our London City (LCY) and London Heathrow (LHR) Points of Presence (POPs) may have experienced elevated Time to First Byte (TTFB), request timeouts, and HTTP 503 errors. Customers using LHR as a shield origin — including those routing through LCY — were most affected. The highest concentration of errors occurred between approximately 16:00 and 16:40 UTC.

Service degradation began to improve at approximately 16:40 UTC and was fully resolved by 19:12 UTC.

Customer impact: Customers in the affected traffic paths may have observed increased latency, elevated error rates, and in some cases failed requests during this window.

Current status: This incident is fully resolved. All services at LCY and LHR are operating normally.

If you have questions about how this incident affected your services, please contact our support team by emailing us at support@fastly.com.

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 26 May 2026 at 00:30 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.

The scheduled maintenance has been completed.

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

The scheduled maintenance has been completed.

We are investigating elevated errors to our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) Points of Presence (POPs)

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs.

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 confirmed the impact to our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs has been mitigated.

Engineering has confirmed that our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs  have been fully restored. Customers may have experienced elevated errors and increased latency  from 20:13  to 21:20  UTC.

This incident is resolved.

12/12 A retrospective into this incident identified that London (LHR) had also experienced elevated errors and increased periods of latency as a result of this incident. Component has been added to reflect accurate data.

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

Status Post, Created Date/Time: 2025-11-29 20:35:29 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 London (LCY), London (LHR), Manchester (MAN) Points of Presence (POPs). 

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting our London (LCY), London (LHR), Manchester (MAN) POPs.

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 confirmed the impact to our London (LCY), London (LHR), Manchester (MAN) POPs has been mitigated.

Engineering has confirmed that our London (LCY), London (LHR), Manchester (MAN) POPs have been fully restored. Customers may have experienced elevated errors and increased latency from 16:06 to 17:09 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-11-11 16:24:05 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're investigating possible performance impact affecting the Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ) data center.

All other locations and services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ) 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 confirmed the impact to Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ) POPs has been mitigated.

Engineering has confirmed that Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ) POPs has been fully restored. Customers may have experienced elevated latency, errors and timeouts from 16: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-11-01 16:54:05 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're currently investigating performance impacts in Europe.

All other locations and services are unaffected.

Our engineers have identified the contributing factor and are developing a fix to our Europe POPs.

All other locations and services are unaffected.

Engineering has confirmed the impact to Europe POPs has been mitigated.

Engineering has confirmed that Europe POPs has been fully restored. Customers may have experienced latency from 17:08 to 18:00 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-09-15 17:35:41 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.

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.

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.