CDN Regional Performance Impact - India

Incident
04 March 2026, 20:07 UTC

CDN Regional Performance Impact - India

Status: closed
Start: 04 March 2026, 19:07 UTC
End: 04 March 2026, 20:07 UTC
Duration: 1 hour
Affected Components:
Platform Asia Ahmedabad (QAU) Dhanbad (QAM) Kochi (QAN) Sambalpur (QAK) Visakhapatnam (VTZ)
Investigating

04 March 2026, 19:07 UTC

04 March 2026, 19:07 UTC

We are investigating elevated errors to our Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) Points of Presence (POPs). 

All other products and services are unaffected by this incident.

Update

04 March 2026, 19:34 UTC

04 March 2026, 19:34 UTC

We are also investigating elevated errors at our Sambalpur (QAK) POP. 

Identified

04 March 2026, 20:04 UTC

04 March 2026, 20:04 UTC

Our engineers believe they have identified contributing factor causing the issue impacting our Sambalpur (QAK), Dhanbad (QAM) , Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) 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.

Monitoring

04 March 2026, 20:05 UTC

04 March 2026, 20:05 UTC

Engineering has confirmed the impact to our Sambalpur (QAK), Dhanbad (QAM) , Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) POPs has been mitigated.

Resolved

04 March 2026, 20:07 UTC

04 March 2026, 20:07 UTC

Engineering has confirmed that our Sambalpur (QAK), Dhanbad (QAM) , Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) POPs have been fully restored. Customers may have experienced elevated errors or increased latency from 19:07 to 19:29 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.

Status Post, Created Date/Time:   2026-03-04 19:27:53 UTC