We are investigating elevated errors and configuration latency to our Pune (PNQ), 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), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) 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 our  Pune (PNQ), 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), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) 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.

All other products and services are unaffected by this incident.

Engineering has confirmed the impact to our Pune (PNQ), 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), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) POPs has been mitigated.

Engineering has confirmed that our Pune (PNQ), 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), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) POPs  have been fully restored.

Customers may have experienced delayed Compute configuration changes or elevated 5xx errors fetching newly deployed services from 14:50 to 18:45 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.

Traffic in Chandigarh (QAL), Kota (KTU), Ambala (QAA), Delhi (QAG), Jaipur (QAY), Meerut (QAD) has been temporarily rerouted.

All other locations and services are unaffected.

Traffic in Meerut (QAD) has been temporarily rerouted.

All other locations and services are unaffected.

As part of Fastly's ongoing global network expansion, we are announcing the addition of our new data centers in Meerut (QAD), Jamnagar (JGA), and Hyderabad (QAE). 

These facilities will initially launch as a limited availability deployment on the 24th of July, 2025, meaning not all customer traffic will be routed through this new location during this initial phase. 

Customers who have questions about this expansion may reach out to our Support team at https://support.fastly.com or by contacting your designated account management team members.

We're happy to announce that the Meerut (QAD), Jamnagar (JGA), and Hyderabad (QAE) data centers have been successfully moved from its initial limited availability phase to general availability. As of September 25, 2025, all customer traffic will now be routed through this location.

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

As part of Fastly's ongoing global network expansion, we are announcing the addition of our new data centers in Meerut (QAD), Jamnagar (JGA), and Hyderabad (QAE). 

These facilities will initially launch as a limited availability deployment on the 24th of July, 2025, meaning not all customer traffic will be routed through this new location during this initial phase. 

Customers who have questions about this expansion may reach out to our Support team at https://support.fastly.com or by contacting your designated account management team members.

The scheduled maintenance has been completed.

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