Fastly will be adding capacity at our Miami (MIA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 05 February 2026 at 07: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.

Fastly will be adding capacity at our Boston (BOS) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 30 January 2026 at 06: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 Jacksonville (JAX) data center to Fastly's North America network. 

Traffic served by our  Jacksonville (JAX) data center will be aggregated into our North America region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Jacksonville (JAX). 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" 

We are investigating elevated errors to our Atlanta (PDK), Miami (MIA) point of presence (POP). 

All other products and services are unaffected by this incident. 

Our engineers believe they have identified contributing factor causing the issue impacting the  Atlanta (PDK), Miami (MIA) 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.

Engineering has confirmed the impact to Atlanta (PDK), Miami (MIA) POP have been mitigated.

Engineering has confirmed that the Atlanta (PDK) and Miami (MIA) POPs have been fully restored.

Customers served by the Atlanta (PDK) POP may have experienced elevated errors and intermittent periods of latency from 01:05 to 02:40 UTC on January 25, 2026. Customers served by the Miami (MIA) POP may have experienced similar impact from 01:05 to 03:30 UTC.

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

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 will be adding capacity at our Atlanta (PDK) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 19 December 2025 at 06:00 UTC.

Our estimated duration is 8h. 

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" 

Traffic in Vancouver (YVR) has been temporarily rerouted.

All other locations and services are unaffected.

Traffic in New York (LGA) has been temporarily rerouted.

All other locations and services are unaffected.

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 

As part of Fastly’s global network expansion, we will be adding the Chicago (ORD) data center to Fastly's North American network. 

Traffic served by our Chicago (ORD) data center will be aggregated into our North American region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Chicago (ORD). 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 Engineers detected a performance impacting event affecting our Frankfurt (FRA), London (LCY), Ashburn (IAD) data centers.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.