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.

Fastly will be adding capacity at our Sao Paulo (GRU) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 19 September 2024 at 04: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 (support@fastly.com).

The scheduled maintenance has been completed.

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" 

We are currently investigating performance impacts to our Rio de Janeiro (GIG), Bogota (BOG), Buenos Aires (EZE), Santiago (SCL), and Sao Paulo (GRU) Point of Presence (POP).

All other locations and services are unaffected.

Our engineers have identified the contributing factor and are applying a fix to our Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP).

All other locations and services are unaffected.

Engineering has confirmed the impact to Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP) has been mitigated.

Engineering has confirmed that Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP) has been fully restored. Customers may have experienced increased latency and 5xxx errors from 04:22 to 05:46 UTC.

This incident is resolved.

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

We're currently investigating performance impacts in Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU).

All other locations and services are unaffected.

Our engineers have identified the contributing factor and are applying a fix to Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU).

All other locations and services are unaffected.

Engineering has confirmed the impact to Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU) has been mitigated.

Engineering has confirmed that Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU) has been fully restored. Customers may have experienced increased latency and 5xx errors from 00:15 to 02:02 UTC.

This incident is resolved.

Fastly Engineers detected a performance impacting event affecting the Sao Paulo (GRU) data center.

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

We're investigating elevated errors in Sao Paulo (GRU).

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.

Fastly will be migrating customers shielding in Sāo Paulo (CGH) to Sāo Paulo (GRU). 

As part of this expansion, customers utilizing shielding in the neighboring Edge Cloud Platform will be migrated to the new Metro POP. Once this maintenance window closes, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf after July 9th, 2023.

When this change is applied, customers may observe additional origin traffic as cache nodes retrieve content from origin.

Action for Fastly Customers:

1. Please be sure to check that your origin access lists allow the full range of Fastly IP addresses: https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges. Failure to verify origin access lists will result in origin connection disruption.
2. Access the Fastly App and modify your service's shield: https://docs.fastly.com/en/guides/shielding#enabling-shielding. 
3. Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).

The scheduled maintenance has been completed.

As part of Fastly’s global network expansion, we will be adding Sao Paulo (GRU) data center to Fastly's South America network. 

Traffic served by our Sao Paulo (GRU) data center will be aggregated into our South America region for billing and stats purposes. We expect that some traffic currently served by our data centers in neighboring regions will shift to Sao Paulo (GRU). 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.