We're investigating possible performance impact affecting the Amsterdam (AMS), Milan (MXP), Sofia (SOF), Fujairah (FJR), Osaka (ITM), Singapore (QPG), Tokyo (NRT), Tokyo (TYO), Los Angeles (BUR), Paris (PAR), Singapore (SIN), Amsterdam (RTM) data center.

All other locations and services are unaffected.

Our engineers are continuing to investigate confirmed periods of increased latency and elevated errors to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs.

Our engineers believe they have identified contributing factor causing the issue impacting the Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) 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. 

Engineering has confirmed the impact to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs has been mitigated and services are fully restored.

Engineering has confirmed that all POPs have been fully restored. Customers may have experienced elevated errors from 13:35 UTC to 14:15 UTC, a duration of 40 minutes on the 11th of December 2025. 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-12-11 14:34:14 UTC 

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.

We are investigating elevated errors to our Chennai (MAA), New Delhi (DEL), Amsterdam (AMS), Johannesburg (JNB) Points of Presence (POPs).

Our engineers have identified the contributing factor and are applying a fix to our Amsterdam (AMS) Point of Presence (POP).

Fastly's Engineering team has confirmed that the impact has been mitigated for our Chennai (MAA), New Delhi (DEL), and Johannesburg (JNB) POPs.

Engineering has confirmed the impact to our Amsterdam (AMS) Point of Presence (POP) has been mitigated.

Engineering has confirmed that our Chennai (MAA), New Delhi (DEL), Amsterdam (AMS), and Johannesburg (JNB) Points of Presence (POPs) have been fully restored. Customers may have experienced an increase in errors and latency from 17:10 to 18:45 UTC.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

This incident is resolved.

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

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" 

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 performing scheduled maintenance on our Amsterdam (AMS) data center from 05 June 2024, 00:00 UTC - 05 June 2024, 04:00 UTC.

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

Fastly continues to perform scheduled maintenance on our Amsterdam (AMS) data center for an extended duration. This maintenance is estimated to conclude on 05 June 2024 at 07:00 UTC.

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

The scheduled maintenance has been completed.

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

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

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

Engineering has deployed a fix and have confirmed a gradual recovery to Amsterdam (AMS) POP. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Engineering has confirmed that our Amsterdam (AMS) POP has been fully restored. Customers may have experienced latency from 04:20 to 5:50 UTC.

This incident is resolved.

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.

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

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.

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

This incident has been resolved.

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

All other locations and services are unaffected.

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

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

This incident has been resolved.