Fastly Engineers detected a performance impacting event affecting the Varanasi (VNS) data center.

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

Fastly will be adding capacity at our Los Angeles (BUR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 22 April 2026 at 11: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.

The scheduled maintenance has been completed.

Fastly Engineers detected a performance impacting event affecting the availability of manage.fastly.com and API.

CDN delivery, stats aggregation, and all other data plane services were unaffected.

Fastly Engineers detected a performance impacting event affecting the Fastly Application. 

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

We are investigating elevated errors when attempting to log into our Fastly Application user interface and sub-services.

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the ability to access our Fastly Application and it's sub-service 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.

Engineering has confirmed the impact to Fastly Application and it's sub-services has been mitigated.

Engineering is seeing a gradual recovery to our customer's ability to access their Fastly Application services. We believe that customers may see intermittent errors as we continue to fine tune our mitigation strategy further. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Our ability to deliver network and security services were unaffected by this incident.

Engineering has confirmed that Fastly Application service has been fully restored. Customers may have experienced the inability to access their Fastly Application and it's sub-services from 14:05 to 15:53 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.

We are investigating elevated errors to our Ashburn (IAD).

All other products and services are unaffected by this incident.

Engineering has confirmed the impact to Ashburn (IAD) PoP has been mitigated.

Our engineers have confirmed that traffic routing through our Ashburn (IAD) POP has been fully restored. Because a software defect caused brief node crashes, customers routing traffic through the affected nodes may have experienced a temporary increase in 5xx errors and dropped connections from 15:55 to 22:10 UTC on April 20, 2026.

This incident is resolved.

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

We are investigating elevated errors to our Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) 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 Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) 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 Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) Point of Presence (POP) has been mitigated.

We are continuing to monitor the situation closely.

Engineering has confirmed that impact for Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) Point of Presence (POP) has been fully restored. Customers may have experienced elevated errors from 07:11 to 07:55 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.

Fastly Engineers detected a performance impacting event affecting the Johannesburg (JNB) data center.

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

Fastly Engineers detected a performance impacting event affecting the Johannesburg (JNB) data center.

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

We are investigating elevated errors to our Image Optimization for traffic shielding at Points of Presence (POPs) in our west North American region.

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Image Optimization 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 our Image Optimization service has been mitigated.

Engineering has confirmed that our Image Optimization service has been fully restored. Customers may have experienced elevated 5xx errors for shield traffic routed to POPs in our west North American region from 19:20 to 21:05 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.