🚨Google Cloud VMware Outage Due to Config Update
VMware outage hits multi-region clusters hard
TL;DR
A Google Cloud VMware service outage hit stretched clusters, causing zonal outages. The issue stemmed from a recent config update and affected multiple regions.
Google Cloud's VMware service experienced an outage due to a configuration update on July 14th at 10:00 PDT. This impacted customers using stretched clusters across multiple regions, leading to network connectivity issues. VMs remained operational but were inaccessible. The root cause was identified as inter-zone communication failures and BGP session flapping between cluster zones. Affected regions included australia-southeast1, europe-west3, and northamerica-northeast2. This outage highlights the importance of robust failover mechanisms in multi-region deployments.
Key Points
Outage began at 10:00 PDT on July 14th and was caused by a configuration update.
Stretched clusters in australia-southeast1, europe-west3, northamerica-northeast2 were impacted.
VMware Avi Load Balancer had seven flaws, including an authentication bypass with CVSS score of 9.8 (CVE-2026-47865).
Five additional CVEs affected VMware Cloud Foundation and Kubernetes Service, ranging from 8.8 to 7.1.
Broadcom released updates fixing the Avi Load Balancer flaws in recent patches.
Why It Matters
If you're running multi-region stretched clusters on Google Cloud's VMware service, this outage is a wake-up call for failover planning. Affected regions saw VMs become inaccessible despite remaining operational. The high CVSS scores of the Avi Load Balancer flaws mean unauthorized access risks are significant.
Frequently Asked Questions
Why does this matter?
If you're running multi-region stretched clusters on Google Cloud's VMware service, this outage is a wake-up call for failover planning. Affected regions saw VMs become inaccessible despite remaining operational. The high CVSS scores of the Avi Load Balancer flaws mean unauthorized access risks are significant.
What happened?
A Google Cloud VMware service outage hit stretched clusters, causing zonal outages. The issue stemmed from a recent config update and affected multiple regions.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.