Google Cloud network configuration update knocks out VMware Engine stretched clusters three regions twelve hours
A Google Cloud $GOOGL network config update cut connectivity to VMware Engine stretched clusters in Sydney, Melbourne and Frankfurt for nearly 12 hours before a rollback fixed it. Stretched clusters are the feature enterprises buy to survive exactly this. Per Google's incident re
Enterprises running VMware Engine stretched clusters on Google Cloud $GOOGL in Sydney, Melbourne and Frankfurt spent nearly 12 hours cut off from a capability they specifically pay for: resilience across zones. The incident began at 17:00 UTC on July 14 and was resolved at 04:46 UTC on July 15, affecting the australia-southeast1, australia-southeast2 and europe-west3 regions. Google's investigation identified a recent network configuration update as the likely cause of the inter-zone network disruption, and the company mitigated the issue by rolling the change back to the last known good configuration. Storage and compute services were not impacted and virtual machines kept running, but the disruption hit inter-zone connectivity, which is the core function of a stretched cluster. These deployments extend compute across distributed sites precisely so that workloads survive a zonal failure. Standard VMware Engine services were not affected. The uncomfortable takeaway for cloud architects: a single configuration change at the provider level disabled the resilience feature itself, a failure mode that no amount of customer-side redundancy design protects against. Per Google Cloud's incident report, reported by The Register and SDxCentral.