Palo Alto (PAO)

18 November 2026, 01:50 UTC
Platform North America Ashburn (IAD) Atlanta (PDK) Boston (BOS) Calgary (YYC) Chicago (CHI) Chicago (ORD) Columbus (CMH) Dallas (DFW) Denver (DEN) Detroit (DTW) Honolulu (HNL) Houston (IAH) Jacksonville (JAX) Kansas City (MCI) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) McAllen (MFE) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) New York (TSS) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
18 November 2026, 01:50 UTC

We're investigating possible performance impact affecting the North America data centers.

All other locations and services are unaffected.

 
18 November 2026, 03:51 UTC

Our engineers have identified the contributing factor causing the issue impacting our services in North America.

Mitigation actions are in progress, and we are seeing early signs of improvement. We will post a new update once recovery is confirmed.

All other products and services remain unaffected by this incident.

 
18 November 2026, 03:57 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to North America POPs. We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.

All other networks and services were unaffected by this incident.

 
18 November 2026, 04:07 UTC

Engineering has confirmed that North America POPs have been fully restored. Customers may have experienced elevated errors and latency from 1:50 to 3:34 UTC.

This incident is resolved.

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.

Status Post, Created Date/Time:   2026-11-18 02:57:01 UTC  

Platform North America Asia Australia / New Zealand Auckland (AKL) Ashburn (IAD) Dubai (DXB) Atlanta (PDK) Boston (BOS) Chicago (CHI) Columbus (CMH) Dallas (DFW) Denver (DEN) Detroit (DTW) Jacksonville (JAX) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Portland (PDX) San Jose (SJC) Seattle (BFI) Toronto (YYZ)
 
04 November 2026, 01:04 UTC

Between 00:21 UTC and 00:24 UTC on November 4, 2026, we experienced a performance impact to the  Auckland (AKL), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Chicago (CHI), Columbus (CMH), Dallas (DFW), Denver (DEN), Detroit (DTW) , Dubai (DXB),  Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Newark (EWR), Palo Alto (PAO), Portland (PDX), San Jose (SJC), Seattle (BFI), Toronto (YYZ), New York (NYC), Los Angeles (LAX), Los Angeles (HHR), Jacksonville (JAX) Point of Presence (POPs).

During this time, customers may have experienced elevated errors and latency.

The issue has been resolved, and all services are operating normally. No other POPs or services were affected.

Platform North America Palo Alto (PAO)
 
02 July 2026, 18:34 UTC

We are investigating elevated errors with Compute at our Palo Alto (PAO) Point of Presence (POP).

All other products and services are unaffected by this incident.

 
02 July 2026, 19:16 UTC

Our engineers believe they have identified contributing factor causing the issue impacting our Palo Alto (PAO) POP.

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.

 
02 July 2026, 19:28 UTC

Engineering has confirmed the impact to our Palo Alto (PAO) POP has been mitigated.

 
02 July 2026, 19:38 UTC

Engineering has confirmed that our Palo Alto (PAO) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 18:34 to 19:12 UTC.

This incident is resolved.



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.

Status Post, Created Date/Time:   2026-07-02 18:53:40 UTC  

Platform Compute North America Fastly Compute Asia KV Store Singapore (QPG) Singapore (SIN) Palo Alto (PAO) San Jose (SJC)
 
20 August 2025, 20:34 UTC

We are investigating elevated errors to our KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs).

All other products and services are unaffected by this incident.

 
20 August 2025, 22:42 UTC

Our engineers have identified the contributing factor and are developing a fix for the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs)

All other locations and services are unaffected.

 
20 August 2025, 22:54 UTC

Engineering has confirmed the impact to  the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been mitigated.

 
20 August 2025, 23:03 UTC

Engineering has confirmed that the impact to the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been fully restored. Customers may have experienced elevated errors and latency from 20:34 to 22:37 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-08-20 22:26:51 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.


05 September 2024, 19:48 UTC
Platform North America Europe Asia Australia / New Zealand South America Africa Amsterdam (AMS) Adelaide (ADL) Seoul (ICN) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Auckland (AKL) Ghana (ACC) Ashburn (IAD) Dubai (FJR) Brisbane (BNE) Dubai (DXB) Buenos Aires (EZE) Johannesburg (JNB) Brussels (BRU) Christchurch (CHC) Fujairah (FJR) Curitiba (CWB) Copenhagen (CPH) Hong Kong (HKG) Melbourne (MEL) Fortaleza (FOR) Dublin (DUB) Perth (PER) Lima (LIM) Atlanta (PDK) Sydney (SYD) Rio de Janeiro (GIG) Boston (BOS) Frankfurt (FRA) Kuala Lumpur (KUL) Santiago (SCL) Calgary (YYC) Wellington (WLG) Chicago (CHI) Helsinki (HEL) Manila (MNL) Sao Paulo (GRU) Osaka (ITM) London (LCY) London (LHR) London (LON) Chicago (ORD) Chennai (MAA) Singapore (QPG) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Tokyo (NRT) Tokyo (TYO) Honolulu (HNL) Hyderabad (HYD) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Kolkata (CCU) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) Montreal (YUL) Newark (EWR) Mumbai (BOM) New York (LGA) New York (NYC) Palo Alto (PAO) New Delhi (DEL) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

Our engineers are continuing to investigate the impact to our Platform delivery services.

 
05 September 2024, 22:01 UTC

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

 
05 September 2024, 23:00 UTC

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

 
05 September 2024, 23:34 UTC

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.

 
06 September 2024, 00:48 UTC

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" 

Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Atlanta (PDK) Boston (BOS) Frankfurt (FRA) Calgary (YYC) Chicago (CHI) Helsinki (HEL) London (LCY) London (LHR) London (LON) Chicago (ORD) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Honolulu (HNL) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
23 July 2024, 12:48 UTC

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.

 
23 July 2024, 14:29 UTC

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.

 
23 July 2024, 16:37 UTC

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.

 
23 July 2024, 23:52 UTC

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" 

Platform North America Los Angeles (BUR) Palo Alto (PAO)
 
04 June 2024, 02:00 UTC

We are investigating elevated errors to our Palo Alto (PAO), Los Angeles (BUR) Point of Presence (POP).

 
04 June 2024, 03:01 UTC

Our engineers have identified the contributing factor and are applying a fix to our Los Angeles (BUR), Palo Alto (PAO) Point of Presence (POP).

All other locations and services are unaffected.

 
04 June 2024, 03:10 UTC

Engineering has confirmed the impact to Los Angeles (BUR), Palo Alto (PAO) Point of Presence (POP) has been mitigated.

 
04 June 2024, 03:19 UTC

Engineering has confirmed that Los Angeles (BUR), Palo Alto (PAO) Point of Presence (POP) has been fully restored. Customers may have experienced increased latency and timeouts from 02:00 to 02:50 UTC.

This incident is resolved.

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

28 August 2023, 19:47 UTC
Platform North America Europe Amsterdam (AMS) Atlanta (PDK) Frankfurt (FRA) Helsinki (HEL) London (LCY) London (LHR) Denver (DEN) Paris (PAR) Stockholm (BMA) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Portland (PDX) San Jose (SJC) Toronto (YYZ)
 
28 August 2023, 19:47 UTC

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.

 
28 August 2023, 20:00 UTC

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

 
28 August 2023, 20:05 UTC

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.

 
28 August 2023, 21:07 UTC

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

 
28 August 2023, 21:35 UTC

This incident has been resolved.

29 June 2023, 18:46 UTC
Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Atlanta (PDK) Boston (BOS) Frankfurt (FRA) Calgary (YYC) Chicago (CHI) Helsinki (HEL) London (LCY) London (LHR) London (LON) Chicago (ORD) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Honolulu (HNL) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
29 June 2023, 18:46 UTC

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

All other locations and services are unaffected.

 
29 June 2023, 19:56 UTC

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

 
29 June 2023, 21:54 UTC

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

 
29 June 2023, 23:54 UTC

This incident has been resolved.

Platform North America Palo Alto (PAO)
 
17 May 2023, 08:00 UTC

Fastly will be adding capacity at our Palo Alto (PAO) data center. End-users may observe connection resets as traffic is migrated onto new hardware. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).

 
17 May 2023, 12:00 UTC

The scheduled maintenance has been completed.