Google Outage History

Started Jul 14, 2026, 05:00 PM UTC· resolved Jul 15, 2026, 03:40 AM UTC

1. investigating Jul 14, 2026, 08:24 PM UTC

   Description: We are experiencing an issue with Google Cloud VMware Engine (GCVE) beginning Tuesday, 2026-07-14 at 10:00 PDT. We are continuing to investigate and mitigate the issue. We believe this disruption is isolated to network connectivity issues for stretch clusters, while Storage and Compute services appear to be unaffected. GCVE VMs are running as expected but customers may experience connectivity issues to the VMs. We will provide another update by Tuesday, 2026-07-14 14:00 PDT with current details. Customer symptoms: Some GCVE customers may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: None at this time.

2. investigating Jul 14, 2026, 09:31 PM UTC

   Description: 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. 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. We will provide another update by Tuesday, 2026-07-14 15:00 PDT with current details. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

3. investigating Jul 14, 2026, 10:16 PM UTC

   Description: 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. 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. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

4. investigating Jul 14, 2026, 11:05 PM UTC

   Description: 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. Our investigation has identified a recent configuration update that is the likely cause of the inter-zone network disruption. Teams are working on remediation. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

5. investigating Jul 15, 2026, 12:13 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Upon further investigation we identified that the northamerica-northeast2 region was not impacted. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

6. investigating Jul 15, 2026, 01:15 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

7. investigating Jul 15, 2026, 01:55 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

8. investigating Jul 15, 2026, 03:27 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following to restore access to your workloads: * 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.

9. resolved Jul 15, 2026, 05:34 AM UTC

   Description: 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. 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. If customers are still experiencing impact from this issue, please contact Support, and we will work with you to resolve any residual impact. We thank you for your patience while we worked to resolve this issue. Customer symptoms: Some GCVE customers using Stretched Cluster may have experienced inter-site communication failures to their GCVE environments within the affected zones. Workaround: The issue is now mitigated.

10. resolved Jul 20, 2026, 06:31 PM UTC

    Preliminary Incident Report We 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. Please 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. If 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). Date/Time of the Issue (All time US/Pacific) Incident Start: 14 July 2026 10:00 Incident End: 14 July 2026 20:40 Duration: 10 hours, 40 minutes Summary On 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. The 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. Preliminary Root Cause A 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. Google engineers are doing a full root cause analysis and will provide additional information once it is available. Remediation To 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. Description of Impact On 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. ---

11. resolved Jul 24, 2026, 07:10 AM UTC

    Incident Report Summary On Tuesday, 14 July 2026 10:00 PT, Google Cloud VMware Engine (GCVE) Stretched Cluster customers in the australia-southeast2 and europe-west3 zones experienced inter-site communication failures. The disruption was traced to a network configuration update that introduced a conflict, causing inter-site communication failures, which triggered VMware Stretched Cluster failover events. Google engineers successfully mitigated the impact by rolling back the issue-causing configuration change and resetting the network state. We 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. Root Cause A network configuration update intended to prepare the cloud network infrastructure for new capabilities was deployed to the foundational network control plane. While the configuration payload itself was structurally valid, it exposed an implementation gap within the control plane's routing logic. This logical gap caused the underlying network hosts to misconfigure program routing tables. As a result, traffic destined for the private IP address space used by GCVE Stretched Clusters was dropped. Because Stretched Clusters rely on this private address space to establish routing sessions for inter-zonal connectivity, the traffic drops severed communications between the active zones of the clusters, triggering VMware High Availability (HA) failovers. Standard routing health-checking protocols, such as Border Gateway Protocol (BGP) and Bidirectional Forwarding Detection (BFD), remained fully functional because their control plane sessions run on separate, unaffected address spaces. Because the control plane remained healthy, standard failover mechanisms failed to detect that the selective private IP range used for inter-zonal data tunneling was being dropped. Automated safeguards did not block the deployment because the configuration passed initial payload validations. The impact only manifested once the update began routing data traffic through the specific affected IP range. Remediation and Prevention To 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. Google is committed preventing a repeat of this issue in the future and is completing the following actions: * Expanded Testing: We are adding more detailed GCVE network setups to our existing testing environments. This allows us to automatically test future network updates against these configurations before they go live. * Service-Level Data Path Failover: We are implementing additional service-level data path failover mechanisms that actively probe the specific data-tunneling traffic space. This will ensure a path failover is triggered if the data plane itself is degraded even when the BGP control plane remains functional. * Detailed Alerting: We are adding faster, more specific alerts for connection issues between zones. This builds on our current platform monitoring to catch minor disruptions early and speed up our response. * Improved Cluster Resilience: We are fine-tuning the cluster's high-availability and storage settings. This makes virtual machines more resilient to short network drops, preventing them from restarting unnecessarily if the main site is still healthy. * Workload Resilience Alignment (Shared Responsibility): We are proactively reaching out to customers utilizing non-vSAN replicated virtual machine configurations within Stretched Clusters. Because these workloads are pinned to a single zone without active cross-site replication, they cannot survive inter-site network disruptions. We are ready to assist customers in auditing their storage policies, adjusting Stretched Cluster configurations, and planning the secondary zone capacity required to enable robust high-availability failovers. Detailed Description of Impact On 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 a 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.

Read the full incident report →

Started Jul 14, 2026, 05:00 PM UTC· resolved Jul 15, 2026, 03:40 AM UTC

1. investigating Jul 14, 2026, 08:24 PM UTC

   Description: We are experiencing an issue with Google Cloud VMware Engine (GCVE) beginning Tuesday, 2026-07-14 at 10:00 PDT. We are continuing to investigate and mitigate the issue. We believe this disruption is isolated to network connectivity issues for stretch clusters, while Storage and Compute services appear to be unaffected. GCVE VMs are running as expected but customers may experience connectivity issues to the VMs. We will provide another update by Tuesday, 2026-07-14 14:00 PDT with current details. Customer symptoms: Some GCVE customers may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: None at this time.

2. investigating Jul 14, 2026, 09:31 PM UTC

   Description: 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. 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. We will provide another update by Tuesday, 2026-07-14 15:00 PDT with current details. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

3. investigating Jul 14, 2026, 10:16 PM UTC

   Description: 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. 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. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

4. investigating Jul 14, 2026, 11:05 PM UTC

   Description: 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. Our investigation has identified a recent configuration update that is the likely cause of the inter-zone network disruption. Teams are working on remediation. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

5. investigating Jul 15, 2026, 12:13 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Upon further investigation we identified that the northamerica-northeast2 region was not impacted. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

6. investigating Jul 15, 2026, 01:15 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

7. investigating Jul 15, 2026, 01:55 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following workarounds to restore access to your workloads: - 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.

8. investigating Jul 15, 2026, 03:27 AM UTC

   Description: 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. A remediation rollout is currently in progress to address the underlying network issue. 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. 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. Customer symptoms: Some GCVE customers using Stretched Cluster may experience inter-site communication failures to their GCVE environments within the affected zones. Workaround: While we work on restoring full connectivity, we recommend the following to restore access to your workloads: * 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.

9. resolved Jul 15, 2026, 05:34 AM UTC

   Description: 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. 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. If customers are still experiencing impact from this issue, please contact Support, and we will work with you to resolve any residual impact. We thank you for your patience while we worked to resolve this issue. Customer symptoms: Some GCVE customers using Stretched Cluster may have experienced inter-site communication failures to their GCVE environments within the affected zones. Workaround: The issue is now mitigated.

10. resolved Jul 20, 2026, 06:31 PM UTC

    Preliminary Incident Report We 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. Please 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. If 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). Date/Time of the Issue (All time US/Pacific) Incident Start: 14 July 2026 10:00 Incident End: 14 July 2026 20:40 Duration: 10 hours, 40 minutes Summary On 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. The 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. Preliminary Root Cause A 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. Google engineers are doing a full root cause analysis and will provide additional information once it is available. Remediation To 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. Description of Impact On 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. ---

11. resolved Jul 24, 2026, 07:10 AM UTC

    Incident Report Summary On Tuesday, 14 July 2026 10:00 PT, Google Cloud VMware Engine (GCVE) Stretched Cluster customers in the australia-southeast2 and europe-west3 zones experienced inter-site communication failures. The 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 impact by rolling back the issue-causing configuration change and resetting the network state. We 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. Root Cause A network configuration update intended to prepare the cloud network infrastructure for new capabilities was deployed to the foundational network control plane. While the configuration payload itself was structurally valid, it exposed an implementation gap within the control plane's routing logic. This logical gap caused the underlying network hosts to misconfigure program routing tables. As a result, traffic destined for the private IP address space used by GCVE Stretched Clusters was dropped. Because Stretched Clusters rely on this private address space to establish routing sessions for inter-zonal connectivity, the traffic drops severed communications between the active zones of the clusters, triggering VMware High Availability (HA) failovers. Standard routing health-checking protocols, such as Border Gateway Protocol (BGP) and Bidirectional Forwarding Detection (BFD), remained fully functional because their control plane sessions run on separate, unaffected address spaces. Because the control plane remained healthy, standard failover mechanisms failed to detect that the selective private IP range used for inter-zonal data tunneling was being dropped. Automated safeguards did not block the deployment because the configuration passed initial payload validations. The impact only manifested once the update began routing data traffic through the specific affected IP range. Remediation and Prevention To 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. Google is committed preventing a repeat of this issue in the future and is completing the following actions: * Expanded Testing: We are adding more detailed GCVE network setups to our existing testing environments. This allows us to automatically test future network updates against these configurations before they go live. * Service-Level Data Path Failover: We are implementing additional service-level data path failover mechanisms that actively probe the specific data-tunneling traffic space. This will ensure a path failover is triggered if the data plane itself is degraded even when the BGP control plane remains functional. * Detailed Alerting: We are adding faster, more specific alerts for connection issues between zones. This builds on our current platform monitoring to catch minor disruptions early and speed up our response. * Improved Cluster Resilience: We are fine-tuning the cluster's high-availability and storage settings. This makes virtual machines more resilient to short network drops, preventing them from restarting unnecessarily if the main site is still healthy. * Workload Resilience Alignment (Shared Responsibility): We are proactively reaching out to customers utilizing non-vSAN replicated virtual machine configurations within Stretched Clusters. Because these workloads are pinned to a single zone without active cross-site replication, they cannot survive inter-site network disruptions. We are ready to assist customers in auditing their storage policies, adjusting Stretched Cluster configurations, and planning the secondary zone capacity required to enable robust high-availability failovers. Detailed Description of Impact On 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 a 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.

Read the full incident report →

Started Jul 13, 2026, 03:41 PM UTC· resolved Jul 16, 2026, 04:45 AM UTC

1. investigating Jul 13, 2026, 03:42 PM UTC

   Firebase Crashlytics data is delayed for 2026-07-10

2. investigating Jul 14, 2026, 07:25 PM UTC

   Firebase Crashlytics data is delayed for 2026-07-10 and 2026-07-11

3. investigating Jul 15, 2026, 05:23 PM UTC

   Firebase Crashlytics data is currently delayed for 2026-07-12 and 2026-07-13. Processing for earlier dates has completed. Exported BigQuery batch and streaming data remain accurate.

Read the full incident report →

Started Jul 04, 2026, 07:00 AM UTC· resolved Jul 06, 2026, 06:00 AM UTC

1. investigating Jul 04, 2026, 02:45 PM UTC

   Performance Monitoring data is delayed

Read the full incident report →

Started Jul 01, 2026, 07:00 AM UTC· resolved Sep 08, 2026, 07:00 AM UTC

1. investigating Jul 14, 2026, 08:38 PM UTC

   We are investigating a system issue. To protect platform stability, we have limited the volume of collected data. Expect a visible reduction in data within Performance Monitoring dashboards and BigQuery exports.

Read the full incident report →

Started Jun 30, 2026, 09:03 AM UTC· resolved Jul 01, 2026, 03:45 AM UTC

1. investigating Jun 30, 2026, 11:56 AM UTC

   Description: We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 05:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: None at this time.

2. investigating Jun 30, 2026, 12:17 PM UTC

   Description: We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: None at this time.

3. investigating Jun 30, 2026, 12:28 PM UTC

   Description: We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: Customers can continue to use the portal to add comments / notes.

4. investigating Jun 30, 2026, 01:28 PM UTC

   Description: We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: Customers can continue to use the portal to add comments / notes.

5. investigating Jun 30, 2026, 02:06 PM UTC

   Description: We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: Customers can continue to use the portal to add comments / notes.

6. investigating Jun 30, 2026, 02:51 PM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Tuesday, 2026-06-30 08:45 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

7. investigating Jun 30, 2026, 03:48 PM UTC

   Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Tuesday, 2026-06-30 09:45 PDT. We will provide more information by Tuesday, 2026-06-30 10:00 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

8. investigating Jun 30, 2026, 04:36 PM UTC

   Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineering teams have shifted focus to replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. While there is currently no specific ETA for the email replay to finish, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 11:00 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

9. investigating Jun 30, 2026, 05:53 PM UTC

   Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 12:15 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

10. investigating Jun 30, 2026, 07:03 PM UTC

    Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 17:00 PDT. Symptoms: Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

11. investigating Jul 01, 2026, 12:44 AM UTC

    Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 21:30 PDT. Symptoms: Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

12. resolved Jul 01, 2026, 04:58 AM UTC

    Description: The issue with inbound emails to Google Cloud Support has been resolved for all affected customers as of Tuesday, 2026-06-30 20:45 PDT. From preliminary analysis, the engineering team identified a recent change which was preventing incoming emails from being processed. We have successfully rolled back the change to mitigate the impact. Backlog processing of all the affected emails is now complete. We thank you for your patience while we worked on resolving the issue. Symptoms: Inbound emails from customers to Google Support were experiencing issues. Case creation and updates continued to work without any issues. Workaround: None as the issue is resolved.

Read the full incident report →

Started Jun 24, 2026, 04:00 PM UTC· resolved Jun 26, 2026, 05:00 PM UTC

1. monitoring Jun 24, 2026, 04:03 PM UTC

   Released the June 2026 spam update , which applies globally and to all languages. The rollout may take a few days to complete.

2. resolved Jun 26, 2026, 05:58 PM UTC

   The rollout was complete as of June 26, 2026.

Read the full incident report →

Started Jun 22, 2026, 07:30 PM UTC· resolved Jun 23, 2026, 12:46 AM UTC

1. monitoring Jun 22, 2026, 10:28 PM UTC

   Description: We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified the root cause and is actively working to mitigate the issue. We will provide an update by Monday, 2026-06-22 17:30 PDT with current details. We apologize to all who are affected by the disruption. Diagnosis / customer symptoms: Some consumer Google Voice users are experiencing account suspensions

2. monitoring Jun 23, 2026, 12:29 AM UTC

   Description: We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified a mitigation strategy and is actively working on mitigation. We do not have an ETA for mitigation at this time. We will provide an update by Monday, 2026-06-22 22:30 PDT with current details. Symptoms: Some consumer Google Voice users are experiencing account suspensions Workaround: None at this time.

3. resolved Jun 23, 2026, 01:08 AM UTC

   Description: The issue with Google Voice has been resolved for all affected users as of Monday, 2026-06-22 17:46 PDT Our engineers have mitigated the issue by rolling back to a previous version and reinstating suspended accounts. We thank you for your patience while we worked on resolving the issue. Symptoms: Some consumer Google Voice users experienced account suspensions Workaround: The issue is now mitigated.

Read the full incident report →

Started Jun 15, 2026, 03:30 PM UTC· resolved Jun 15, 2026, 06:00 PM UTC

1. investigating Jun 15, 2026, 06:03 PM UTC

   We are experiencing an issue causing elevated error rates when loading data on the Crashlytics, Release Monitoring, and Performance Monitoring dashboards, within Android Studio, and via our MCP tools. The team is actively investigating.

Read the full incident report →

Started Jun 11, 2026, 04:50 AM UTC· resolved Jun 11, 2026, 06:40 AM UTC

1. investigating Jun 11, 2026, 05:20 AM UTC

   We are experiencing an issue with Firebase Cloud Messaging’s send apis in Asia beginning on Wednesday, 2026-06-10 21:50 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 23:45 PDT with current details.

2. investigating Jun 11, 2026, 06:19 AM UTC

   Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-06-11 03:00 PDT. Customers may observe requests to send messages to FCM taking longer to complete. A small number may experience 5xx errors and should retry with backoff.

3. investigating Jun 11, 2026, 06:36 AM UTC

   We are starting to see some recovery.

4. investigating Jun 11, 2026, 07:15 AM UTC

   We believe the incident was fully mitigated as of 11:40pm.

Read the full incident report →

Started Jun 10, 2026, 10:20 AM UTC· resolved Jun 10, 2026, 05:30 PM UTC

1. investigating Jun 10, 2026, 12:40 PM UTC

   Description: We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 06:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. Workaround: None at this time.

2. investigating Jun 10, 2026, 01:21 PM UTC

   Description: We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 08:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. Workaround: None at this time.

3. investigating Jun 10, 2026, 03:10 PM UTC

   Description: We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue and identify a mitigation strategy. We will provide an update by Wednesday, 2026-06-10 09:30 PDT with current details. Symptoms: The following services are experiencing “Something Went Wrong” errors.: * Gemini app in Workspace includes the following platforms; * Web, MacOS, iOS and Android * Gemini in Chrome Workaround: None at this time.

4. investigating Jun 10, 2026, 04:24 PM UTC

   Description: We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has identified a mitigation which is currently in progress. We do not have an ETA for mitigation at this time. We will provide an update by Wednesday, 2026-06-10 12:30 PDT with current details. Symptoms: The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome Workaround: None at this time.

5. investigating Jun 10, 2026, 06:37 PM UTC

   Description: We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has applied mitigations to reduce impact and continues to investigate the root cause. We are seeing signs of recovery and will continue to monitor progress. We will provide an update by Wednesday, 2026-06-10 14:30 PDT with current details. Symptoms: The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome Workaround: None at this time.

6. investigating Jun 10, 2026, 08:19 PM UTC

   Description: We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has applied mitigations to reduce impact and confirmed the majority of users are no longer observing impact as of Wednesday, 2026-06-10 10:30 PDT. We will continue to monitor the service for stability. We will provide an update by Wednesday, 2026-06-10 20:30 PDT with current details. Symptoms: The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome Workaround: None at this time.

7. resolved Jun 11, 2026, 01:07 AM UTC

   Description: The issue with Gemini has been resolved for all the affected users as of Wednesday, 2026-06-10 10:30 US/Pacific. From preliminary analysis, the issue was triggered by a performance issue in our backend database which impacted the retrieval of Gemini App tools catalog. Our engineers mitigated the issue by optimizing the load distribution across our backend database fleet. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected users may have seen "Something went wrong" errors (codes 1099, 1076) when prompting Gemini while using the following services. Gemini App in Workspace includes the following platforms: - Web, MacOS, iOS and Android - Gemini in Chrome Workaround: None as the issue is now resolved.

8. resolved Jun 12, 2026, 11:14 AM UTC

   Gemini app (web and mobile): * Users experienced a 50% error rate when attempting to send prompts, receiving "Something went wrong" messages. The issue affected both consumer accounts and enterprise Google Workspace customers . Integrations: * Google Chrome Integration: The Gemini Side Panel and integrated conversational features encountered persistent timeouts.

9. resolved Jun 16, 2026, 05:41 PM UTC

   Gemini app (web and mobile): * High Failure Rates: Users experienced a 50% error rate when attempting to send prompts, receiving "Something went wrong" messages . * Service Unavailability: The issue affected both consumer accounts and enterprise Google Workspace customers . * Enterprise Google Workspace Users encountered disruptions when attempting to attach assets from Google Drive within the web application (gemini.google.com). Affected users observed the "Add from Drive" functionality to be visually disabled and unresponsive following interaction with the "+" prompt. Integrations: * Google Chrome Integration: The Gemini Side Panel and integrated conversational features encountered persistent timeouts.

Read the full incident report →

Started Jun 09, 2026, 12:00 PM UTC· resolved Jun 16, 2026, 12:00 PM UTC

1. investigating Jun 10, 2026, 07:30 AM UTC

   We're investigating reports of an issue with Content API for Shopping. We will provide more information shortly.

Read the full incident report →

Started Jun 05, 2026, 07:00 AM UTC· resolved Jun 26, 2026, 07:00 PM UTC

1. investigating Jun 10, 2026, 01:13 AM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. We are investigating additional traffic mitigations and Internet Edge peering augmentation to alleviate the latency issues affecting our customers. We will provide our next update by Wednesday, 2026-06-10 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

2. investigating Jun 10, 2026, 10:25 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. We are investigating additional traffic mitigations and Internet Edge peering augmentation to alleviate the latency issues affecting our customers. We are continuing to work with the ISP partners in the region to mitigate any additional impact from unplanned failures. We will provide our next update by Thursday, 2026-06-11 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

3. investigating Jun 11, 2026, 11:25 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Initial traffic mitigations have yielded positive results for some Cloud customers. In parallel, we are pursuing additional Internet Edge peering capacity to reduce existing fragility in the metro. We are also optimizing capacity across network backbones to increase additional headroom for VPC customers in the affected region. Additionally, we are planning to augment our local Delhi POP and migrating select peering partners to further increase regional capacity. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Friday, 2026-06-12 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

4. investigating Jun 12, 2026, 10:50 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Initial traffic mitigations have yielded positive results for some Cloud customers. In parallel, we are pursuing additional Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are augmenting out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India (expected to be done by Wednesday, 2026-06-17 PDT). We have optimized capacity across network backbones to increase available headroom. Additionally, we are further augmenting our Delhi backbone capacity (expected to be complete by Monday, 2026-06-15 PDT). We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-15 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

5. investigating Jun 15, 2026, 11:11 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Media CDN customers may have experienced higher latencies than normal. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are augmenting out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India (expected to be done by Wednesday, 2026-06-17 PDT). We have optimized capacity across network backbones to increase available headroom. Additionally, we have augmented our Delhi backbone capacity over the weekend. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Wednesday, 2026-06-17 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

6. investigating Jun 17, 2026, 10:36 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility has caused a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers to experience intermittent latency spikes as demand exceeds regional capacity. Media CDN customers may also notice increased latencies. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are nearly finished with the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. We have optimized capacity across network backbones to increase available headroom. Additionally, we have augmented our Delhi backbone capacity. We have also restored additional capacity between Delhi-Chennai and Delhi-Mumbai. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-22 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

7. investigating Jun 22, 2026, 11:51 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility has caused a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers to experience intermittent latency spikes as demand exceeds regional capacity. Media CDN customers may also notice increased latencies. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a large portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Since the last update, we have completed the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. Following safety clearance, teams obtained access to the damaged site and will further restore additional incremental user-facing backbone capacity on Tuesday, 2026-06-23. We have optimized capacity across network backbones to increase available headroom, and augmented our Delhi user-facing backbone capacity. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Tuesday, 2026-06-23 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

8. investigating Jun 23, 2026, 10:52 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility has caused a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers to experience intermittent latency spikes as demand exceeds regional capacity. Media CDN customers may also notice increased latencies. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a large portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Since the last update, we have completed the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. Following safety clearance, our team has accessed the damaged site and is continuing to restore additional capacity throughout this week. We have optimized capacity across network backbones to increase available headroom and augmented our Delhi user-facing backbone capacity. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-29 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

9. resolved Jun 29, 2026, 11:06 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility caused a subset of Hybrid Connectivity, Virtual Private Cloud (VPC) and Media CDN customers to experience intermittent latency spikes as demand exceeded regional capacity. We completed the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. Service to a large portion of Internet Edge peering capacity has been restored to reduce latency in the local Delhi metropolitan area. We are now recovered and returned to normal service as of Friday, 2026-06-26 PDT. Following safety clearance, our team restored all lost capacity. We have restored capacity between Delhi-Chennai and Delhi-Mumbai and will continue to closely monitor latency deviations and packet drops. We thank you for your patience during the resolution of this issue. Symptoms: The impacted customers may have experienced slightly elevated latency and non-optimal network routing into Google Cloud. Workaround: None

Read the full incident report →

Started Jun 05, 2026, 07:00 AM UTC· resolved Jun 26, 2026, 07:00 PM UTC

1. investigating Jun 10, 2026, 01:13 AM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. We are investigating additional traffic mitigations and Internet Edge peering augmentation to alleviate the latency issues affecting our customers. We will provide our next update by Wednesday, 2026-06-10 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

2. investigating Jun 10, 2026, 10:25 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. We are investigating additional traffic mitigations and Internet Edge peering augmentation to alleviate the latency issues affecting our customers. We are continuing to work with the ISP partners in the region to mitigate any additional impact from unplanned failures. We will provide our next update by Thursday, 2026-06-11 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

3. investigating Jun 11, 2026, 11:25 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Initial traffic mitigations have yielded positive results for some Cloud customers. In parallel, we are pursuing additional Internet Edge peering capacity to reduce existing fragility in the metro. We are also optimizing capacity across network backbones to increase additional headroom for VPC customers in the affected region. Additionally, we are planning to augment our local Delhi POP and migrating select peering partners to further increase regional capacity. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Friday, 2026-06-12 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

4. investigating Jun 12, 2026, 10:50 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Initial traffic mitigations have yielded positive results for some Cloud customers. In parallel, we are pursuing additional Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are augmenting out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India (expected to be done by Wednesday, 2026-06-17 PDT). We have optimized capacity across network backbones to increase available headroom. Additionally, we are further augmenting our Delhi backbone capacity (expected to be complete by Monday, 2026-06-15 PDT). We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-15 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

5. investigating Jun 15, 2026, 11:11 PM UTC

   Description: A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Media CDN customers may have experienced higher latencies than normal. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are augmenting out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India (expected to be done by Wednesday, 2026-06-17 PDT). We have optimized capacity across network backbones to increase available headroom. Additionally, we have augmented our Delhi backbone capacity over the weekend. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Wednesday, 2026-06-17 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

6. investigating Jun 17, 2026, 10:36 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility has caused a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers to experience intermittent latency spikes as demand exceeds regional capacity. Media CDN customers may also notice increased latencies. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are nearly finished with the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. We have optimized capacity across network backbones to increase available headroom. Additionally, we have augmented our Delhi backbone capacity. We have also restored additional capacity between Delhi-Chennai and Delhi-Mumbai. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-22 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

7. investigating Jun 22, 2026, 11:51 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility has caused a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers to experience intermittent latency spikes as demand exceeds regional capacity. Media CDN customers may also notice increased latencies. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a large portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Since the last update, we have completed the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. Following safety clearance, teams obtained access to the damaged site and will further restore additional incremental user-facing backbone capacity on Tuesday, 2026-06-23. We have optimized capacity across network backbones to increase available headroom, and augmented our Delhi user-facing backbone capacity. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Tuesday, 2026-06-23 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

8. investigating Jun 23, 2026, 10:52 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility has caused a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers to experience intermittent latency spikes as demand exceeds regional capacity. Media CDN customers may also notice increased latencies. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a large portion of Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Since the last update, we have completed the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. Following safety clearance, our team has accessed the damaged site and is continuing to restore additional capacity throughout this week. We have optimized capacity across network backbones to increase available headroom and augmented our Delhi user-facing backbone capacity. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-29 at 17:00 PDT. Symptoms: Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. Workaround: There is no workaround at this time.

9. resolved Jun 29, 2026, 11:06 PM UTC

   Description: Traffic rerouting from the impacted Delhi facility caused a subset of Hybrid Connectivity, Virtual Private Cloud (VPC) and Media CDN customers to experience intermittent latency spikes as demand exceeded regional capacity. We completed the augmentation of out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India. Service to a large portion of Internet Edge peering capacity has been restored to reduce latency in the local Delhi metropolitan area. We are now recovered and returned to normal service as of Friday, 2026-06-26 PDT. Following safety clearance, our team restored all lost capacity. We have restored capacity between Delhi-Chennai and Delhi-Mumbai and will continue to closely monitor latency deviations and packet drops. We thank you for your patience during the resolution of this issue. Symptoms: The impacted customers may have experienced slightly elevated latency and non-optimal network routing into Google Cloud. Workaround: None

Read the full incident report →

Started Jun 01, 2026, 06:30 PM UTC· resolved Jun 02, 2026, 03:30 AM UTC

1. investigating Jun 01, 2026, 09:36 PM UTC

   Android physical tests delayed in FTL. Mitigation in progress.

Read the full incident report →

Started May 31, 2026, 03:28 AM UTC· resolved May 31, 2026, 04:24 AM UTC

1. investigating May 31, 2026, 04:59 AM UTC

   Description: We are experiencing an issue with Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, Google Docs beginning on Saturday, 2026-05-30 20:28 PDT. Our engineering team continues to investigate the issue. We will provide an update by Saturday, 2026-05-30 22:10 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Customers may experience issues loading the application/ intermittent high latency or errors while using the application. Workaround: None at this time.

2. resolved May 31, 2026, 05:11 AM UTC

   Description: The issue with Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, Google Docs has been resolved for all affected users as of Saturday, 2026-05-30 21:30 PDT. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have experienced issues loading the application/ intermittent high latency or errors while using the application. Workaround: None at this time as the issue stands mitigated

3. resolved Jun 02, 2026, 03:50 AM UTC

   Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Workspace, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future. Please 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. If you have experienced impact outside of what is listed below, please reach out to Google Workspace Support using help article https://support.google.com/a/answer/1047213 Date/Time of the Issue (All time US/Pacific) Incident Start: 30 May 2026 20:15 Incident End: 30 May 2026 21:30 Duration: 1 hour, 15 minutes Summary Starting on Saturday, 30 May 2026 at 20:15 US/Pacific, multiple Google Workspace products experienced service disruptions for a duration of 1 hour and 15 minutes. The affected services included Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, and Google Docs. During this incident, customers encountered difficulties loading applications, as well as intermittent high latency or errors. Preliminary Root Cause The disruption originated from failures in a regional infrastructure component responsible for Google's distributed lock service. This critical system facilitates resource synchronization, manages shared data access, and coordinates background tasks for numerous Google services. A high volume of rapid configuration changes triggered the regional failure, preventing Workspace servers from reliably processing traffic. To mitigate the impact, Google Workspace traffic was redirected to alternative regions. Google engineers have begun a full root cause analysis and will provide additional information once it is available. Remediation Google engineers were alerted to the issue via automated monitoring at 20:28 US/Pacific on Saturday, 30 May 2026, and immediately began an investigation. The investigation identified elevated error rates and high latency affecting multiple Google Workspace backend services. Upon investigation our engineering team confirmed errors were primarily originating from some regional servers due to coordination service failures in the region. To mitigate the impact, Google engineers redirected traffic away from the affected servers. Description of Impact Affected customers encountered difficulties loading applications or experienced failures when performing tasks within the following products: * Gmail * Google Calendar * Google Chat * Google Docs * Google Drive * Google Meet * Google Voice

4. resolved Jun 04, 2026, 08:11 PM UTC

   Incident Report Summary Starting at 20:15 US/Pacific on Saturday, 30 May 2026, various Google Workspace services encountered service-level disruptions lasting approximately 75 minutes. The scope of impact spanned several products, specifically affecting Gmail, Google Docs, Drive, Calendar, Chat, Meet, and Google Voice. Throughout the duration of this event, users faced obstacles while attempting to initialize applications, in addition to experiencing sporadic instances of elevated latency and request failures. Google offers a sincere apology for the operational interference this issue introduced to your organization. Recognizing the critical nature of Google Cloud to your daily operations, we deeply regret any resulting loss in productivity. Engineering efforts are currently focused on remediating the underlying cause to ensure future stability. Root Cause The disruption originated from failures in a critical cluster infrastructure component responsible for Google's service discovery and configuration management systems. This system facilitates resource synchronization, manages shared data access, and coordinates background tasks for numerous Google services. A high volume of rapid configuration changes triggered the regional failure in Workspace Services, preventing Workspace servers from reliably processing traffic. To mitigate the impact, Google Workspace traffic was redirected to alternative regions. Remediation and Prevention Google engineers were alerted to the issue via automated monitoring on Saturday, 30 May 2026 at 20:28 US/Pacific and immediately began an investigation. The investigation identified elevated error rates and high latency affecting multiple Google Workspace backend services. Upon investigation our engineering team confirmed errors were primarily originating from some regional servers due to coordination service failures in the region. To mitigate the impact, Google engineers redirected traffic away from the affected servers. Google is committed preventing a repeat of this issue in the future and is completing the following actions: - Prevent recurrence of this incident by rolling out the fix for the latent encryption library issue, which improves the handling of internal log compaction compactions during active file writes, to prevent recurrence of the cluster instability. - Investigating additional resilience in our database layer. Detailed Description of Impact On 30 May 2026 from 20:15 to 21:30 US/Pacific, affected customers encountered difficulties while loading applications or experienced failures when performing tasks within the following products: - Gmail - Google Calendar - Google Chat - Google Docs - Google Drive - Google Meet - Google Voice

Read the full incident report →

Started May 31, 2026, 03:26 AM UTC· resolved May 31, 2026, 04:21 AM UTC

1. investigating May 31, 2026, 05:25 AM UTC

   We're investigating reports of an issue with Play Billing Purchases and Play Developer Subscriptions and In-App Purchases API. We will provide more information shortly.

2. resolved May 31, 2026, 05:49 AM UTC

   The problem with Play Billing Purchases and Play Developer Subscriptions and In-App Purchases API has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Started May 21, 2026, 03:40 PM UTC· resolved Jun 02, 2026, 12:40 PM UTC

1. monitoring May 21, 2026, 03:43 PM UTC

   Released the May 2026 core update . The rollout may take up to 2 weeks to complete.

2. resolved Jun 02, 2026, 12:43 PM UTC

   The rollout was complete as of June 2, 2026.

Read the full incident report →

Started May 21, 2026, 07:00 AM UTC· resolved May 21, 2026, 03:47 PM UTC

1. investigating May 21, 2026, 03:37 PM UTC

   Description: We are experiencing an issue with Gmail beginning on Thursday, 2026-05-21 at 00:00 PDT. Mitigation efforts are currently underway by our engineering team. We will provide the next update by Thursday, 2026-05-21 at 09:30 PDT. Diagnosis / customer symptoms: Gmail users are experiencing delayed delivery of messages sent from the bank.in domains. Workaround: None at this time.

2. resolved May 21, 2026, 04:09 PM UTC

   Description: Our internal telemetry shows that the issue with Gmail has been resolved for all affected users as of Thursday, 2026-05-21 at 08:47 US/Pacific. Our engineering team is actively monitoring the system to ensure continued stability. Diagnosis / customer symptoms: Customers should expect new messages to be delivered normally, older emails could take some time as the senders continue to retry. Workaround: This issue is now mitigated.

Read the full incident report →

Started May 19, 2026, 10:29 PM UTC· resolved May 20, 2026, 04:04 AM UTC

1. monitoring May 20, 2026, 01:07 AM UTC

   Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 20:30 PDT with current details. Customer symtomps: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time

2. investigating May 20, 2026, 03:20 AM UTC

   Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 22:00 PDT with current details. Symptoms: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.

3. resolved May 20, 2026, 04:38 AM UTC

   Description: The issue with NotebookLM has been resolved for all affected users as of Tuesday, 2026-05-19 21:04 PDT. From preliminary analysis, the issue was triggered by a recent software update resulting in accounts on premium plans being incorrectly recognized as free accounts. The issue was mitigated by restoring the system to a previous stable state, which successfully reinstated the appropriate service tiers for all affected accounts. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have noticed lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.

Read the full incident report →

Started May 19, 2026, 01:30 PM UTC· resolved May 22, 2026, 12:00 PM UTC

1. investigating May 21, 2026, 01:32 PM UTC

   The issue was triaged and a fix has been found. We will update soon on expected end of this disruption.

2. investigating May 21, 2026, 04:45 PM UTC

   The fix has mitigated the issue and we are actively rolling it out. We expect the rollout to complete within 6 hours.

3. resolved May 22, 2026, 05:55 PM UTC

   The fix has been rolled out and service has returned to normal

Read the full incident report →

Started May 12, 2026, 04:01 PM UTC· resolved May 12, 2026, 10:16 PM UTC

1. resolved May 13, 2026, 05:55 PM UTC

   Description: We were experiencing an issue with Cameyo by Google, beginning on Tuesday, 12 May 2026 09:01 US/Pacific. The issue was mitigated on Tuesday, 12 May 2026 15:16 US/Pacific by restarting the RAP system service, and performing full server reboots. From preliminary investigation, this was caused by a faulty code for logging improvement on the Player VMs. Log files were unexpectedly duplicated until the disk was full leading to the session failures. Some customers were recovered automatically after the channel binaries were rolled back, while the others were required to restart their VMs manually. Currently, the issue is fully mitigated and change is rolled back. We apologise to those who were impacted by this issue. Customer symptoms: The customers were experiencing an issue that couldn’t connect to the Player VMs normally. The disk utilization on the affected VMs reaches 99% or even 100%. Workaround: Not needed because all affected servers have been mitigated.

Read the full incident report →

Started May 11, 2026, 03:15 PM UTC· resolved May 11, 2026, 11:00 PM UTC

1. investigating May 11, 2026, 05:27 PM UTC

   Firebase Test Lab is experiencing higher wait times on ARM devices. We are currently investigating the cause. Next update in when something significantly changes.

2. resolved May 12, 2026, 04:42 PM UTC

   Firebase Test Lab is no longer experiencing delays for tests on ARM devices. Unless something unexpected happens, this is the last update.

Read the full incident report →

Started May 06, 2026, 04:00 PM UTC· resolved May 21, 2026, 10:00 PM UTC

1. monitoring May 16, 2026, 02:05 AM UTC

   Description: We are experiencing an issue with Gmail beginning on Saturday 2026-05-06. Our engineering team continues to investigate the issue. We will provide more information by Monday, 2026-05-18 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer symptoms: Impacted users may experience authentication failures while logging in to Microsoft Exchange Online through Gmail App on Android devices. Workaround: Affected users can use Microsoft web app to access the Inbox.

2. monitoring May 18, 2026, 09:45 PM UTC

   Description: We are experiencing an issue with Gmail Android client connecting with Microsoft Exchange Online accounts beginning on Saturday 2026-05-06. Our engineering team has identified the issue and is actively working on rolling out a fix to unblock all the affected customers. We will provide more information by Tuesday, 2026-05-19 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer symptoms: Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. Workaround: Affected users can use Microsoft Web App to access the Inbox.

3. monitoring May 19, 2026, 09:55 PM UTC

   Description: We are experiencing an issue with Gmail Android client connecting with Microsoft Exchange Online accounts beginning on Saturday 2026-05-06. Our engineering team has identified the issue and started rolling out a new version of Gmail Android release that contains the fix to unblock users. Users already on the new app version will be able to Log In and Sync their accounts successfully. We will provide more information by Thursday, 2026-05-21 17:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer symptoms: Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. Workaround: Affected users can use Microsoft Web App to access the Inbox.

4. monitoring May 22, 2026, 12:04 AM UTC

   Description: Our engineering team identified the issue and released a new version of the Gmail Android application (version 2026.05.11) to the Google Play Store, which contains a fix to unblock affected users. If you are currently encountering this issue, please upgrade to the latest version of the Gmail Android app. Users operating on the new app version should be able to successfully log in and sync their accounts. We will provide more information by Friday, 2026-05-22 17:00 US/Pacific with current details. We thank you for your patience while we are working on resolving the issue. Symptoms: Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. Workaround: Affected users could update to the latest version of Gmail Android (version 2026.05.11) in Google Play Store.

5. resolved May 22, 2026, 06:57 PM UTC

   Description: The issue with Gmail has been resolved in the new Gmail android release (version 2026.05.11) as of Thursday, 2026-05-21 15:00 PDT. Our engineering team identified the issue and released a new version of the Gmail Android application to the Google Play Store, which contains a fix to unblock affected users. If you are currently encountering this issue, please upgrade to the latest version of the Gmail Android app. Users operating on the new app version will be able to successfully log in and sync their accounts. We thank you for your patience while we worked on resolving the issue. Symptoms: Impacted users might have experienced authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. Workaround: Update to the latest version of Gmail Android (2026.05.11) in Google Play Store.

Read the full incident report →

Started May 04, 2026, 04:40 PM UTC· resolved May 08, 2026, 06:53 PM UTC

1. monitoring May 05, 2026, 11:35 PM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Tuesday, 2026-05-05 20:30 PDT. Symptoms: Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

2. monitoring May 06, 2026, 03:22 AM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2026-05-06 09:00 PDT. Symptoms: Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

3. monitoring May 06, 2026, 07:11 PM UTC

   Description: Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-05-07 17:00 PDT. Symptoms: Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

4. monitoring May 07, 2026, 11:52 PM UTC

   Description: Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-05-07 20:30 PDT. Symptoms: Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

5. resolved May 08, 2026, 01:00 AM UTC

   Description: The issue with Gemini has been resolved for all affected users as of Thursday, 2026-05-07 17:00 PDT. The issue was triggered due to a combination of insufficient database resources, and application bugs. The database capacity issues were resolved, and further code changes are being made to mitigate the application issue. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected customers may have experienced the "Something went wrong(13)" error message in their Gemini conversations.

6. monitoring May 08, 2026, 05:16 AM UTC

   Description: Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-05-08 01:00 PDT. Symptoms: Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

7. monitoring May 08, 2026, 07:29 AM UTC

   Description: Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 04:00 PDT. Symptoms: Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

8. monitoring May 08, 2026, 10:23 AM UTC

   Description: Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 09:00 PDT. Symptoms: Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

9. monitoring May 08, 2026, 03:53 PM UTC

   Description: Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 12:00 PDT. Symptoms: Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

10. resolved May 08, 2026, 06:58 PM UTC

    Description: The issue with Gemini has been resolved for all affected users as of Friday, 2026-05-08 11:53 PDT. The issue was triggered due to a combination of insufficient database resources, and application bugs. The database capacity issues were resolved, and further code changes are being made to mitigate the application issue. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected customers may have experienced "Something went wrong(13)" error message in their Gemini conversations. Workaround: None at this time.

Read the full incident report →