Traffic in Honolulu (HNL) has been temporarily rerouted.

All other locations and services are unaffected.

We are investigating increased latency for purging at our Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) Points of Presence (POPs). 

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) status page components.

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.

Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to the Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) status page components. 

All other locations and services are unaffected.

Engineering has confirmed the impact to the Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) status page components has been mitigated.

Engineering has confirmed that our Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) POPs and Purging service has been fully restored.

Customers may have experienced delayed cache purge propagation, with some purge requests lost from 17:02 to 23:24 UTC. 

Customers who purged content during this window should expect that some previously purged content may have been served as stale until the fix was applied.

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.

We have identified an issue that caused elevated error rates (HTTP 429/503) and timeouts for Object Storage in the Frankfurt (FRA), Ashburn (IAD) Points of Presence (POP)s.

All other products and services are unaffected by this incident.

Traffic in St. Louis (STL) has been temporarily rerouted.

All other locations and services are unaffected.

Fastly will be adding capacity at our Toronto (YYZ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 21 July 2026 at 03:00 UTC.

Our estimated duration is 1d. 

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.

This maintenance has been cancelled and will be rescheduled at a later date.

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.

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.

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

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.

Fastly will be adding capacity at our Ashburn (IAD) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 1st July 2026 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 at https://support.fastly.com.

The scheduled maintenance has been completed.

Fastly will be adding capacity at our Vancouver (YVR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 June 2026 at 07:30 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 Toronto (YYZ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 June 2026 at 02: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.

We are investigating elevated errors to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) status page components .

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.

The fix has been successfully deployed, and we have observed recovery to only our DFW, DEN, MSP, and EWR POPs. Error rates and latency have returned to nominal levels and we are monitoring stability at these locations.

Our engineers have identified an additional  contributing factor and are developing an adjusted mitigation strategy to our MIA and PDK POPs specifically.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) Points of Presence (POPs) has been mitigated.

Engineering has confirmed that our our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) POPs have been fully restored.

Customers may have experienced increased latency from 00:50 to 01:50 UTC at our DFW, DEN, MSP, and EWR POPs and from 00:50 to 02:13 UTC at our PDK and MIA POPs. 

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.