India
Fastly will be performing scheduled maintenance on our Delhi (QAG), Ranchi (IXR), Sambalpur (QAK) and Varanasi (VNS) data centers from 27 October 2026, 20:00 UTC - 28 October 2026, 00:00 UTC.
During this time frame traffic will be redirected to neighboring POPs in the region.
The scheduled maintenance has been completed.
Fastly Engineers detected a performance impacting event affecting the Mumbai (BOM) data center from 07:00 to 11:00 UTC on October 22, 2026.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly will be performing scheduled maintenance on our Bhopal (QBL) and Sambalpur (QAK) data centers from 10 October 2026, 19:20 UTC - 10 October 2026, 21:00 UTC .
During this time frame traffic will be redirected to neighboring POPs in the region.
The scheduled maintenance has been completed.
Traffic in Sambalpur (QAK) has been temporarily rerouted.
All other locations and services are unaffected.
Traffic in Delhi (QAG) has been temporarily rerouted.
All other locations and services are unaffected.
Traffic in Ambala (QAA) 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.
Fastly Engineers detected a performance impacting event affecting the India region.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Traffic in Port Blair (IXZ) has been temporarily rerouted.
All other locations and services are unaffected.
Traffic in Srinagar-Nahota (QBG) has been temporarily rerouted.
All other locations and services are unaffected.