Live / Google Cloud / Incident
Google Cloud: Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possi
Google Cloud · cloud.google.comMinor incidentResolved2026-06-29 23:06 UTC
Public — what happened
Summary
Google Cloud reported that some network traffic coming from Delhi, Chennai, Mumbai and nearby areas saw intermittent slowdowns and possible data loss starting on 2026-06-05, mainly affecting a subset of Hybrid Connectivity and Virtual Private Cloud customers, with Media CDN customers also possibly seeing higher delays. The company said a fire at a third-party data center forced an emergency power cut to networking equipment in Delhi, and the traffic it shifted elsewhere as a result ran into more demand than available capacity across Indian cities and regional internet providers. Over the following weeks Google Cloud described adding and restoring network capacity in Delhi and Chennai, noting early improvements for some customers, and it marked the incident resolved on 2026-06-26.
Timeline
- Started — 2026-06-05 07:00 UTC
- Investigating — 2026-06-10 01:13 UTC (8 updates)
- Resolved — 2026-06-26 19:00 UTC · 22 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Google Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Google Cloud: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Google Cloud report →
More from Google Cloud