GCVE Stretched Cluster outage in australia-southeast1

"modified": "2026-07-14T21:31:53+00:00",
"modified": "2026-07-14T21:31:53+00:00",

"id": "australia-southeast1",
"title": "Sydney (australia-southeast1)"
"modified": "2026-07-14T22:16:55+00:00",
"id": "australia-southeast1",
"title": "Sydney (australia-southeast1)"
"created": "2026-07-14T22:16:55+00:00",
"modified": "2026-07-14T22:16:55+00:00",
"text": "**Summary**\nGoogle Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.\n**Description**\nWe are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched cluster customers beginning Tuesday, 2026-07-14 at 10:00 PDT. We have identified the customers that are affected by this issue and we are working with them on mitigation.\nOur investigation has identified underlying inter-zone communication failures and Border Gateway Protocol (BGP) session flapping between cluster zones. Specifically, network connectivity has been lost between the affected zones and the witness appliance. Because the witness appliance is currently unreachable, the cluster zones are unable to safely synchronize state. As a result, VMs on the affected sites are becoming isolated and may be left without writable data.\n**Failover / VM Migration:** Migrating affected VMs to the healthy, secondary zone of your stretch cluster remains the primary mitigation strategy. Because of the complexities surrounding failover risks and secondary zone health, we highly encourage you to open a ticket with Google Cloud Support if you are severely impacted.\nWe do not currently have an ETA for resolution. We will provide another update by Tuesday, 2026-07-14 16:00 PDT with current details.\n**Customer Symptoms**\nSome GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.\n**Workaround**\nWhile we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads:\n- VM Migration (recommended): Where possible, migrate your affected VMs to the healthy and unaffected side of the stretch cluster. We strongly recommend consulting with Google Support before proceeding.",
"when": "2026-07-14T22:16:55+00:00"
"id": "australia-southeast1",
"title": "Sydney (australia-southeast1)"
"created": "2026-07-14T22:16:55+00:00",