Loading...
Loading...
A preliminary incident report for a GCVE Stretched Cluster outage on July 14, 2026, was posted. The incident caused inter-site communication failures for 10h40m in australia-southeast2 and europe-west3 zones due to a network config change. The report includes root cause and remediation details.
The incident caused a 10-hour 40-minute outage for GCVE Stretched Cluster customers in two zones, severely impacting reliability. No cost, migration, quality, or compliance impacts noted.
"end": "2026-07-15T04:46:00+00:00", "modified": "2026-07-15T05:34:27+00:00", "modified": "2026-07-15T05:34:27+00:00",
"end": "2026-07-15T03:40:00+00:00", "modified": "2026-07-20T18:31:26+00:00", "created": "2026-07-20T18:31:26+00:00", "modified": "2026-07-20T18:31:26+00:00", "text": "## Preliminary Incident Report\nWe sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.\nPlease note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.\nIf you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using [**https://cloud.google.com/support**](https://cloud.google.com/support).\n## Date/Time of the Issue (All time US/Pacific)\nIncident Start: 14 July 2026 10:00\nIncident End: 14 July 2026 20:40\nDuration: 10 hours, 40 minutes\n## Summary\nOn Tuesday, 14 July 2026, Google Cloud VMware Engine (GCVE) Stretched Cluster customers in the australia-southeast2 and europe-west3 zones experienced inter-site communication failures.\nThe disruption was traced to a network configuration update that introduced a conflict, causing inter-site communication failures, which triggered VMware Stretch Cluster failover events. Google engineers successfully mitigated the disruption by rolling back the configuration change.\n## Preliminary Root Cause\nA configuration change deployed within the Google Cloud network affected traffic between the VMware Engine stretched cluster zones. This resulted in a loss of connectivity between zones in the stretched cluster deployment.\nGoogle engineers are doing a full root cause analysis and will provide additional information once it is available.\n## Remediation\nTo stabilize the environment, engineers identified the working network paths and deployed configuration changes to reroute traffic and restore connectivity. GCVE stretch cluster inter-zonal connectivity was completely restored for all supported locations on Tuesday, 14 July 2026 at 20:40 US/Pacific.\n## Description of Impact\nOn Tuesday, 14 July 2026 from 10:00 to 20:40 US/Pacific, customers utilizing GCVE stretch clusters in the affected zones (australia-southeast2, and europe-west3) experienced inter-site communication failures. For some customers, depending on their architecture, this disruption led to VMWare HA event causing VM restarts/movement across zones as designed, Host disconnects, VSAN alarms and Intermittent access to VMware Management (vCenter/NSX Manager) components.\n---", "when": "2026-07-20T18:31:26+00:00" "created": "2026-07-20T18:31:26+00:00", "modified": "2026-07-20T18:31:26+00:00", "text": "## Preliminary Incident Report\nWe sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.\nPlease note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.\nIf you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using [**https://cloud.google.com/support**](https://cloud.google.com/support).\n## Date/Time of the Issue (All time US/Pacific)\nIncident Start: 14 July 2026 10:00\nIncident End: 14 July 2026 20:40\nDuration: 10 hours, 40 minutes\n## Summary\nOn Tuesday, 14 July 2026, Google Cloud VMware Engine (GCVE) Stretched Cluster customers in the australia-southeast2 and europe-west3 zones experienced inter-site communication failures.\nThe disruption was traced to a network configuration update that introduced a conflict, causing inter-site communication failures, which triggered VMware Stretch Cluster failover events. Google engineers successfully mitigated the disruption by rolling back the configuration change.\n## Preliminary Root Cause\nA configuration change deployed within the Google Cloud network affected traffic between the VMware Engine stretched cluster zones. This resulted in a loss of connectivity between zones in the stretched cluster deployment.\nGoogle engineers are doing a full root cause analysis and will provide additional information once it is available.\n## Remediation\nTo stabilize the environment, engineers identified the working network paths and deployed configuration changes to reroute traffic and restore connectivity. GCVE stretch cluster inter-zonal connectivity was completely restored for all supported locations on Tuesday, 14 July 2026 at 20:40 US/Pacific.\n## Description of Impact\nOn Tuesday, 14 July 2026 from 10:00 to 20:40 US/Pacific, customers utilizing GCVE stretch clusters in the affected zones (australia-southeast2, and europe-west3) experienced inter-site communication failures. For some customers, depending on their architecture, this disruption led to VMWare HA event causing VM restarts/movement across zones as designed, Host disconnects, VSAN alarms and Intermittent access to VMware Management (vCenter/NSX Manager) components.\n---", "when": "2026-07-20T18:31:26+00:00" "modified": "2026-07-20T18:31:26+00:00",
"end": "2026-07-15T03:40:00+00:00",
Check your models and usage for free. See the relevant official changes, estimated cost, and a practical next step.