Elevated Errors for India region

Incident

20 April 2026, 08:39 UTC

Elevated Errors for India region

Status: closed

Start: 20 April 2026, 07:10 UTC

End: 20 April 2026, 08:39 UTC

Duration: 1 hour 29 minutes

Affected Components:

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

Investigating

20 April 2026, 07:10 UTC

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.

Identified

20 April 2026, 08:18 UTC

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.

Monitoring

20 April 2026, 08:20 UTC

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.

Resolved

20 April 2026, 08:39 UTC

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.

Status Post, Created Date/Time: 2026-04-20 08:08:51 UTC