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

Traffic served by our  Berlin (BER) 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  Berlin (BER) . 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" 

Fastly will be adding capacity at our Frankfurt (FRA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 03 March 2026 at 00: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.

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

As part of Fastly’s global network expansion, we will be adding London (BQH) data center to Fastly's European (EMEA) network. 

This facility will initially launch as a limited availability deployment on the 26th of February 2026, meaning not all customer traffic will be routed through this new location during this initial phase. 

Our estimated duration is 4 hours, starting at 00:00 UTC.

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 Public IP List | Fastly Documentation. 

Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.

The scheduled maintenance has been completed.

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

As part of Fastly’s global network expansion, we will be adding London (QQP) data center to Fastly's European (EMEA) network. 

This facility will initially launch as a limited availability deployment on the 26th of February 2026, meaning not all customer traffic will be routed through this new location during this initial phase. 

Our estimated duration is 4 hours, starting at 00:00 UTC.

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 Public IP List | Fastly Documentation. 

Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.

The scheduled maintenance has been completed.

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

As part of Fastly’s global network expansion, we will be adding Surrey (LGW) data center to Fastly's European (EMEA)  network. 

This facility will initially launch as a limited availability deployment on the 25th of February 2026, meaning not all customer traffic will be routed through this new location during this initial phase. 

Our estimated duration is 4 hours, starting at 01:00 UTC.

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 Public IP List | Fastly Documentation. 

Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.

The scheduled maintenance has been completed.

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

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

Traffic served by our  Milan (BGY)  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  Milan (BGY) . 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.

As part of Fastly’s global network expansion, we will be adding London (LTN) data center to Fastly's European (EMEA) network. 

This facility will initially launch as a limited availability deployment on the 22nd of January 2026, meaning not all customer traffic will be routed through this new location during this initial phase. 

Our estimated duration is 4 hours, starting at 00:00 UTC.

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 Public IP List | Fastly Documentation. 

Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.

The scheduled maintenance has been completed.

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

Fastly will be adding capacity at our Madrid (TOJ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 20 January 2026 at 01:00 UTC.

Our estimated duration is 2h. 

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.

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

Fastly will be adding capacity at our Madrid (TOJ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 24 December 2025 at 03: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.

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

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