Third-party data centre fire forces Google Cloud outage

Google Cloud said some customers in India experienced intermittent network disruptions after a fire at a third-party data centre triggered an emergency shutdown of networking equipment. The incident isolated a Delhi point of presence, reduced metropolitan network capacity and caused elevated latency from Delhi, Chennai, Mumbai and nearby regions. For BTW readers, the signal is that cloud resilience needs facility-level redundancy evidence, not only provider-scale reputation.

• No workaround makes traffic mitigation and restoration timing the key signals
• Fire exposes single-point-of-failure risk in third-party cloud infrastructure

The fact

On 9 June, Google Cloud said customers in India experienced intermittent network disruptions after a fire at a third-party data centre triggered an emergency shutdown of networking equipment. The shutdown isolated a Delhi point of presence and reduced capacity across the metropolitan area. Traffic from Delhi, Chennai, Mumbai and nearby regions saw elevated latency, with no workaround while restoration continued.

The Assessment

The outage links Google Cloud's customer reliability to third-party facility risk, not its own backbone operations. In India's fast-growing cloud market, enterprise resilience depends on whether providers can demonstrate metro-level redundancy. For Google, competing with AWS and Azure, infrastructure dependency becomes a trust signal. See also: Grid backlash drives flexible load demands.

What to Watch

Watch Google's status page for restoration timelines and details on the affected third-party site, including fire timing and any announced changes to redundancy architecture. See also: OpenAI IPO turns compute procurement into a market test.