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

Our engineers are continuing to investigate a performance impact to  Europe, Global POP Network (SEV1/0) service.

All other locations and services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Europe, Global POP Network (SEV1/0) 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 Europe, Global POP Network (SEV1/0) service  has been mitigated.

To provide further clarity on this incident: we initially posted to global components out of an abundance of caution while we investigated. Following further investigation, we can confirm the performance impact was isolated to our Amsterdam (RTM), London (LON), Marseille (MRS), Paris (PAR) and Vienna (VIE) POPs.

We've updated both the status post title and listed components to reflect these findings. This incident remains mitigated.

Engineering has confirmed that London (LON), Marseille (MRS), Vienna (VIE), Paris (PAR), Amsterdam (RTM) POPs has been fully restored. Customers may have experienced elevated errors and/or latency from 17:50 to 18:15 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-11-12 18:17:01 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 are investigating elevated errors to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) 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  Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) 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.

Our engineers have identified an additional  contributing factor and are developing an adjusted mitigation strategy to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs.

All other locations and services are unaffected.

Engineering has deployed a fix and have confirmed a gradual recovery to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs.  We will continue to monitor until we’ve confirmed that the customer  experience has been fully restored.

All other locations and services are unaffected.

Engineering has confirmed that our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs have been fully restored. Customers may have experienced increased latency or elevated timeout errors from 11:30 on the 10th of October 2025 to 00:30 on the 11th of October 2025 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-10-10 21:10:07 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.

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

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

All other locations and services are unaffected.

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

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.

As part of Fastly’s global network expansion, we will be adding Amsterdam (RTM) data center to Fastly's Europe network. 

Traffic served by our Amsterdam (RTM) data center will be aggregated into our Europe region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Amsterdam (RTM). As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https:/www.fastly.com/pricing.

The scheduled maintenance has been completed.

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