Gemini Major Outage - July 14, 2026

<p> Incident began at <strong>2026-07-14 10:00</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We 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.</p> <p>Our preliminary investigation indicates this is stemming from an underlying network connectivity issue affecting the infrastructure that links the zones within a stretch cluster. This disruption is causing synchronization issues between the affected zones. We believe Storage and Compute services remain unaffected, and VMs are running as expected, though connectivity to them may be degraded.</p> <p>We will provide another update by Tuesday, 2026-07-14 15:00 PDT with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.</p> <p><strong>Workaround</strong></p> <p>While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads:</p> <ul> <li>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.</li> </ul> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Melbourne (australia-southeast2), Frankfurt (europe-west3), Toronto (northamerica-northeast2)</p>

<p> Incident began at <strong>2026-07-14 10:00</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We 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.</p> <p>Our 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.</p> <p><strong>Failover / VM Migration:</strong> 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.</p> <p>We do not currently have an ETA for resolution. We will provide another update by Tuesday, 2026-07-14 16:00 PDT with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.</p> <p><strong>Workaround</strong></p> <p>While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads:</p> <ul> <li>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.</li> </ul> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Sydney (australia-southeast1), Melbourne (australia-southeast2), Frankfurt (europe-west3), Toronto (northamerica-northeast2)</p>

<p> Incident began at <strong>2026-07-14 10:00</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We 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.</p> <p>Our investigation has identified a recent configuration update that is the likely cause of the inter-zone network disruption. Teams are working on remediation.</p> <p><strong>Failover / VM Migration:</strong> 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.</p> <p>We do not currently have an ETA for resolution. We will provide another update by Tuesday, 2026-07-14 17:00 PDT with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.</p> <p><strong>Workaround</strong></p> <p>While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads:</p> <ul> <li>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.</li> </ul> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Sydney (australia-southeast1), Melbourne (australia-southeast2), Frankfurt (europe-west3), Toronto (northamerica-northeast2)</p>

<p> Incident began at <strong>2026-07-14 10:00</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We 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.</p> <p>A remediation rollout is currently in progress to address the underlying network issue.</p> <p><strong>Failover / VM Migration:</strong> 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.</p> <p>We do not currently have an ETA for resolution. We will provide another update by Tuesday, 2026-07-14 18:00 PDT with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.</p> <p>Upon further investigation we identified that the northamerica-northeast2 region was not impacted.</p> <p><strong>Workaround</strong></p> <p>While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads:</p> <ul> <li>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.</li> </ul> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Sydney (australia-southeast1), Melbourne (australia-southeast2), Frankfurt (europe-west3)</p>

<p> Incident began at <strong>2026-07-14 10:00</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We 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.</p> <p>A remediation rollout is currently in progress to address the underlying network issue.</p> <p><strong>Failover / VM Migration:</strong> 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.</p> <p>We do not currently have an ETA for resolution. We will provide another update by Tuesday, 2026-07-14 19:00 PDT with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.</p> <p><strong>Workaround</strong></p> <p>While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads:</p> <ul> <li>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.</li> </ul> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Sydney (australia-southeast1), Melbourne (australia-southeast2), Frankfurt (europe-west3)</p>

<p> Incident began at <strong>2026-07-14 10:00</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We 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.</p> <p>A remediation rollout is currently in progress to address the underlying network issue.</p> <p><strong>Failover / VM Migration:</strong> 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.</p> <p>We do not currently have an ETA for resolution. We will provide another update by Tuesday, 2026-07-14 20:30 PDT with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.</p> <p><strong>Workaround</strong></p> <p>While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads:</p> <ul> <li>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.</li> </ul> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Sydney (australia-southeast1), Melbourne (australia-southeast2), Frankfurt (europe-west3)</p>

<p> Incident began at <strong>2026-07-14 10:00</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We 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.</p> <p>A remediation rollout is currently in progress to address the underlying network issue.</p> <p><strong>Failover / VM Migration:</strong> 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.</p> <p>We do not currently have an ETA for resolution. We will provide another update by Tuesday, 2026-07-14 22:00 PDT with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones.</p> <p><strong>Workaround</strong></p> <p>While we work on restoring full connectivity, we recommend the following to restore access to your workloads:</p> <ul> <li>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 Cloud Support before proceeding.</li> </ul> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Sydney (australia-southeast1), Melbourne (australia-southeast2), Frankfurt (europe-west3)</p>

<p> Incident began at <strong>2026-07-14 10:00</strong> and ended at <strong>2026-07-14 21:46</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Google Cloud VMware Engine (GCVE) Stretched Cluster customers may have experienced zonal outages impacting network connectivity across multiple regions.</p> <p><strong>Description</strong></p> <p>We experienced an inter-site communication issue with Google Cloud VMware Engine (GCVE) Stretched Cluster customers beginning Tuesday, 2026-07-14 at 10:00 PDT. We identified the affected customers, and have worked with them to fully mitigate the issue by Tuesday, 2026-07-14 at 21:46 PDT.</p> <p>Preliminary analysis indicates that a network configuration update was the cause of the inter-zone network disruption. Our engineering team mitigated the issue by rolling back the faulty configuration to its last-known good value.</p> <p>If customers are still experiencing impact from this issue, please contact Support, and we will work with you to resolve any residual impact.</p> <p>We thank you for your patience while we worked to resolve this issue.</p> <p><strong>Customer Symptoms</strong></p> <p>Some GCVE customers using Stretched Cluster may have experienced inter-site communication failures to their GCVE environments within the affected zones.</p> <p><strong>Workaround</strong></p> <p>The issue is now mitigated.</p> </div><hr><p>Affected products: VMWare engine</p><p>Affected locations: Sydney (australia-southeast1), Melbourne (australia-southeast2), Frankfurt (europe-west3)</p>