{"id":10233,"date":"2026-07-15T23:30:38","date_gmt":"2026-07-16T03:30:38","guid":{"rendered":"https:\/\/hostingdiscussion.com\/news\/?p=10233"},"modified":"2026-07-15T20:42:36","modified_gmt":"2026-07-16T00:42:36","slug":"google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for","status":"publish","type":"post","link":"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/","title":{"rendered":"Google Cloud’s own config change broke the resilience feature customers pay for"},"content":{"rendered":"

Google Cloud<\/a> spent six hours on July 14 trying to figure out why its own network broke a feature specifically designed not to break, before admitting the company had done it to itself.<\/p>\n

The trouble started around 10:00 PDT, when customers using Google Cloud VMware Engine’s stretched cluster feature began losing network connectivity across multiple regions. Stretched clusters exist for one reason: they pool resources across two physical sites and keep both in sync so a failure at one location doesn’t take down a customer’s virtual servers.<\/p>\n

Storage and compute stayed up throughout the incident, and virtual machines kept running, but customers simply couldn’t reach them, which somewhat defeats the purpose of paying for a resilience feature in the first place.<\/p>\n

Google’s incident report initially pointed to “an underlying network connectivity issue affecting the infrastructure that links the zones within a stretch cluster,” warning that the problem was causing synchronization issues between zones. A later update got more specific, blaming inter-zone communication failures and something called BGP session flapping, essentially unstable routing between the cluster zones and a component called the witness appliance. Without a stable connection to that witness appliance, the affected clusters couldn’t safely confirm which zone held the accurate, up-to-date state, so synchronization stalled entirely.<\/p>\n

By 16:05 PDT, Google came clean: the company traced the disruption to a recent configuration change on its own end. As of this writing, Google hasn’t given customers a timeline for full remediation, leaving businesses in the four affected regions, Australia Southeast 1 and 2, Europe West 3, and North America Northeast 2, waiting to find out when the resilience they’re paying for actually comes back online.<\/p>\n

Customers running VMware<\/a> elsewhere have their own reason to move quickly right now, regardless of Google’s outage. Broadcom disclosed seven vulnerabilities in VMware’s Avi Load Balancer<\/a> this week, including one, CVE-2026-47865, that scored a near-maximum 9.8 on the severity scale.<\/p>\n

The flaw is an authentication bypass that could let an attacker with network access slip past the login mechanism entirely and reach the Avi control plane, a serious problem given the tool connects to VMware Cloud Foundation<\/a>, Kubernetes Service, and resources spread across public clouds. Broadcom has already shipped patches for all seven flaws.<\/p>\n","protected":false},"excerpt":{"rendered":"

Google Cloud spent six hours on July 14 trying to figure out why its own network broke a feature specifically designed not to break, before admitting the company had done it to itself. The trouble started around 10:00 PDT, when customers using Google Cloud VMware Engine’s stretched cluster feature began losing network connectivity across multiple […]<\/p>\n","protected":false},"author":20624,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[7402,7399,1793,7401,7400,7398],"class_list":["post-10233","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-cve-2026-47865","tag-gcve-stretched-cluster-failure","tag-google-cloud","tag-network-incident","tag-vmware-avi-load-balancer","tag-vmware-outage"],"acf":[],"yoast_head":"\nGoogle Cloud's own config change broke the resilience feature customers pay for - Web Hosting News<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Google Cloud's own config change broke the resilience feature customers pay for - Web Hosting News\" \/>\n<meta property=\"og:description\" content=\"Google Cloud spent six hours on July 14 trying to figure out why its own network broke a feature specifically designed not to break, before admitting the company had done it to itself. The trouble started around 10:00 PDT, when customers using Google Cloud VMware Engine’s stretched cluster feature began losing network connectivity across multiple […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/\" \/>\n<meta property=\"og:site_name\" content=\"Web Hosting News\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-16T03:30:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-16T00:42:36+00:00\" \/>\n<meta name=\"author\" content=\"Justine Juyad\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Justine Juyad\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/\",\"url\":\"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/\",\"name\":\"Google Cloud's own config change broke the resilience feature customers pay for - Web Hosting News\",\"isPartOf\":{\"@id\":\"https:\/\/hostingdiscussion.com\/news\/#website\"},\"datePublished\":\"2026-07-16T03:30:38+00:00\",\"dateModified\":\"2026-07-16T00:42:36+00:00\",\"author\":{\"@id\":\"https:\/\/hostingdiscussion.com\/news\/#\/schema\/person\/3a1732732b90f8c57c2a0ec68d3c49e3\"},\"breadcrumb\":{\"@id\":\"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/hostingdiscussion.com\/news\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Google Cloud’s own config change broke the resilience feature customers pay for\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/hostingdiscussion.com\/news\/#website\",\"url\":\"https:\/\/hostingdiscussion.com\/news\/\",\"name\":\"Web Hosting News\",\"description\":\"Cloud and web hosting industry daily news\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/hostingdiscussion.com\/news\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/hostingdiscussion.com\/news\/#\/schema\/person\/3a1732732b90f8c57c2a0ec68d3c49e3\",\"name\":\"Justine Juyad\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/hostingdiscussion.com\/news\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/96df33d01870f85226adf8492251fbefe00bc349b10bb7679b094f3fa086999c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/96df33d01870f85226adf8492251fbefe00bc349b10bb7679b094f3fa086999c?s=96&d=mm&r=g\",\"caption\":\"Justine Juyad\"},\"description\":\"HostingDiscussion.com senior reporter\",\"sameAs\":[\"https:\/\/hostingdiscussion.com\/news\/\"],\"url\":\"https:\/\/hostingdiscussion.com\/news\/author\/justine-juyad\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Google Cloud's own config change broke the resilience feature customers pay for - Web Hosting News","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/","og_locale":"en_US","og_type":"article","og_title":"Google Cloud's own config change broke the resilience feature customers pay for - Web Hosting News","og_description":"Google Cloud spent six hours on July 14 trying to figure out why its own network broke a feature specifically designed not to break, before admitting the company had done it to itself. The trouble started around 10:00 PDT, when customers using Google Cloud VMware Engine’s stretched cluster feature began losing network connectivity across multiple […]","og_url":"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/","og_site_name":"Web Hosting News","article_published_time":"2026-07-16T03:30:38+00:00","article_modified_time":"2026-07-16T00:42:36+00:00","author":"Justine Juyad","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Justine Juyad","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/","url":"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/","name":"Google Cloud's own config change broke the resilience feature customers pay for - Web Hosting News","isPartOf":{"@id":"https:\/\/hostingdiscussion.com\/news\/#website"},"datePublished":"2026-07-16T03:30:38+00:00","dateModified":"2026-07-16T00:42:36+00:00","author":{"@id":"https:\/\/hostingdiscussion.com\/news\/#\/schema\/person\/3a1732732b90f8c57c2a0ec68d3c49e3"},"breadcrumb":{"@id":"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/hostingdiscussion.com\/news\/google-clouds-own-config-change-broke-the-resilience-feature-customers-pay-for\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/hostingdiscussion.com\/news\/"},{"@type":"ListItem","position":2,"name":"Google Cloud’s own config change broke the resilience feature customers pay for"}]},{"@type":"WebSite","@id":"https:\/\/hostingdiscussion.com\/news\/#website","url":"https:\/\/hostingdiscussion.com\/news\/","name":"Web Hosting News","description":"Cloud and web hosting industry daily news","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/hostingdiscussion.com\/news\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/hostingdiscussion.com\/news\/#\/schema\/person\/3a1732732b90f8c57c2a0ec68d3c49e3","name":"Justine Juyad","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/hostingdiscussion.com\/news\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/96df33d01870f85226adf8492251fbefe00bc349b10bb7679b094f3fa086999c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/96df33d01870f85226adf8492251fbefe00bc349b10bb7679b094f3fa086999c?s=96&d=mm&r=g","caption":"Justine Juyad"},"description":"HostingDiscussion.com senior reporter","sameAs":["https:\/\/hostingdiscussion.com\/news\/"],"url":"https:\/\/hostingdiscussion.com\/news\/author\/justine-juyad\/"}]}},"views":2,"_links":{"self":[{"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/posts\/10233","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/users\/20624"}],"replies":[{"embeddable":true,"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/comments?post=10233"}],"version-history":[{"count":1,"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/posts\/10233\/revisions"}],"predecessor-version":[{"id":10234,"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/posts\/10233\/revisions\/10234"}],"wp:attachment":[{"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/media?parent=10233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/categories?post=10233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hostingdiscussion.com\/news\/wp-json\/wp\/v2\/tags?post=10233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}