Google Cloud customers in India continue to face intermittent latency and packet loss after a June 9 fire at a third-party Delhi data centre facility. Google has rerouted traffic, but the June 11 update shows reduced Delhi POP capacity still affects traffic from Delhi, Chennai, Mumbai and surrounding areas. Recovery depends on facility restoration, added backbone capacity, Delhi POP expansion and selected peering-partner migration.
Operates Google Cloud and manages cloud network routing for enterprise customers.
Google Cloud is a major cloud infrastructure provider whose network incidents affect enterprise connectivity, resilience planning and regional cloud operations.
Operates Google Cloud and manages cloud network routing for enterprise customers.
The Delhi fire shows how local facility disruption can continue to affect cloud traffic after rerouting when metro and peering capacity remain constrained.
The Delhi fire shows how local facility disruption can continue to affect cloud traffic after rerouting when metro and peering capacity remain constrained.
Google Cloud reroutes India traffic after a Delhi data centre fire, while some metro customers still face latency and packet loss.
The Delhi fire shows how local facility disruption can continue to affect cloud traffic after rerouting when metro and peering capacity remain constrained.
Published reporting
• Delhi POP isolation reduced capacity after a June 5 facility shutdown
• India metro capacity remains tight as rerouted traffic strains regional peering
The fact
Google Cloud customers in India continue to see intermittent latency and packet loss after a June 5 fire at a third-party data centre facility in Delhi forced an emergency shutdown of networking equipment. In a June 10 update, Google said its Delhi POP was isolated, reducing metro capacity and affecting traffic from Delhi, Chennai, Mumbai and surrounding areas. The company has rerouted traffic away from the impacted facility.
The Assessment
Google has contained the immediate facility risk, but replacement routes still do not have enough capacity for all affected demand. The remaining issue is congestion across Indian metros and regional ISPs, especially for customers using Hybrid Connectivity and VPC. Recovery now depends on Delhi facility restoration, added backbone capacity, Delhi POP expansion and selected peering-partner migration.
What to Watch
Track Google's next status update for facility restoration timelines, backbone capacity additions and whether any Delhi POP expansion or peering-partner migration is announced.
Also read: Third-party data centre fire forces Google Cloud outage
Signal Brief
- Signal: Google Cloud reroutes India traffic after Delhi data centre fire
- Signal Type: Cloud Infrastructure Outage Update
- Region: Asia Pacific
- Market Class: Cloud Service
Operating Surface
- Published sources should identify the affected parties, operating surface, and market exposure before this trend map is treated as complete.
Market Context
- The Delhi fire shows how local facility disruption can continue to affect cloud traffic after rerouting when metro and peering capacity remain constrained.
- Operational relevance: High
- Time Horizon: Next 30 days
What To Watch
- Watch for official statements, regulatory updates, customer or partner exposure, and follow-up disclosures.
Member Briefing
Deeper Trend Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock trend briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For operators, investors, and policy teams that need relationship evidence, failure paths, and source notes. Sign in to unlock.
Join Leadership Alliance