CDN Regional Performance Impact - India
CDN Regional Performance Impact - India
14 February 2026, 13:36 UTC
14 February 2026, 13:36 UTC
We're currently investigating performance impacts in 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), Jaipur (QAY), 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).
All other locations and services are unaffected.
14 February 2026, 20:29 UTC
14 February 2026, 20:29 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), Jaipur (QAY), 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) 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.
14 February 2026, 22:49 UTC
14 February 2026, 22:49 UTC
Traffic in 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), Jaipur (QAY), 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) has been temporarily rerouted.
All other locations and services are unaffected.
14 February 2026, 23:24 UTC
14 February 2026, 23:24 UTC
Our engineers are coordinating with ISPs local to the Indian region and developing an adjusted mitigation strategy 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), Jaipur (QAY), 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) POPs.
All other locations and services are unaffected.
15 February 2026, 05:30 UTC
15 February 2026, 05:30 UTC
Engineering has confirmed the impact 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), Jaipur (QAY), 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) POPs has been mitigated.
The fix has been successfully deployed, and we have observed a recovery. Our team will continue to monitor the platform to ensure stability before we resolve this incident.
We will provide a final update once the incident is fully resolved.
15 February 2026, 05:37 UTC
15 February 2026, 05:37 UTC
Engineering has confirmed that 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), Jaipur (QAY), 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) Points of Presence (POPs) has been fully restored. Customers may have experienced increased latency from February 14th, 2026 at 13:36 UTC to February 15th, 2026 at 04:20 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.