Here’s what Google’s Status page saysCurrently affected location(s): Delhi (asia-south2)Date: 9 Jun 2026Time: 18:13 PDTDescriptionSummaryDescriptionSymptomsWorkaroundGoogle Cloud users in parts of India are experiencing slower network performance after a fire at a third-party data centre facility in Delhi triggered an emergency shutdown of networking equipment.
According to an update on Google's status page, network traffic originating from Delhi, Mumbai, Chennai and nearby regions has been facing intermittent periods of elevated latency and possible packet loss since this morning.
The company said the incident affected a local Point of Presence (POP) in Delhi, reducing available network capacity in the area.As stated on the status page, Google has rerouted traffic to other facilities and is working on additional measures to reduce the impact while the affected facility remains offline.
As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi.
Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs.We are investigating additional traffic mitigations and Internet Edge peering augmentation to alleviate the latency issues affecting our customers.We will provide our next update by Wednesday, 2026-06-10 17:00 PDT.Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored.There is no workaround at this time.
Here’s what Google’s Status page says
Currently affected location(s): Delhi (asia-south2)
Date: 9 Jun 2026
Time: 18:13 PDT
Description
Summary
Description
Symptoms
Workaround
Google Cloud users in parts of India are experiencing slower network performance after a fire at a third-party data centre facility in Delhi triggered an emergency shutdown of networking equipment. According to an update on Google's status page, network traffic originating from Delhi, Mumbai, Chennai and nearby regions has been facing intermittent periods of elevated latency and possible packet loss since this morning. The company said the incident affected a local Point of Presence (POP) in Delhi, reducing available network capacity in the area.As stated on the status page, Google has rerouted traffic to other facilities and is working on additional measures to reduce the impact while the affected facility remains offline. As of now, there is no workaround, the company added.Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.Incident began at 2026-06-09 11:22 (all times are US/Pacific).Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area.We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs.We are investigating additional traffic mitigations and Internet Edge peering augmentation to alleviate the latency issues affecting our customers.We will provide our next update by Wednesday, 2026-06-10 17:00 PDT.Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored.There is no workaround at this time.
