RESOLVED: Multiple services were experiencing issues in the europe-west2 region.

Timeline

1. 05 Nov · 06:17 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific).
   
   Incident Report
   Summary
   On Monday, 19 Oct 2026 at 22:53 US/Pacific (Tuesday, 20 Oct 2026, 06:53 BST), a data center facility that hosts europe-west2-b, a zone within the europe-west2 cloud region, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. The subsequent failover of these workloads to unaffected zones and alternate regions caused transient latency and elevated error rates across the broader europe-west2 region.
   
   The resolution of the main impact was completed within 6 hours and 8 minutes.
   
   Root Cause
   Facility architecture and background:
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—where the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders (A and B) terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Uninterruptible Power Supply (UPS) battery systems provide approximately five minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility di

2. 04 Nov · 21:15 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific).
   
   ## Incident Report
   
   ### **Summary**
   
   On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
   
   The primary impact was mitigated after 6 hours 8 minutes.
   
   ### **Root Cause**
   
   **Facility architecture and background:**
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the facility had been placed in a temp

3. 04 Nov · 21:15 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific).
   
   Incident Report
   Summary
   On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
   
   The primary impact was mitigated after 6 hours 8 minutes.
   
   Root Cause
   Facility architecture and background:
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the facility had been placed in a temporary single-feed (1N) bri

4. 04 Nov · 21:15 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific).
   
   Incident Report
   Summary
   On Monday, 19 Oct 2026 at 22:53 US/Pacific (Tuesday, 20 Oct 2026, 06:53 BST), a data center facility that hosts europe-west2-b, a zone within the europe-west2 cloud region, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. The subsequent failover of these workloads to unaffected zones and alternate regions caused transient latency and elevated error rates across the broader europe-west2 region.
   
   The resolution of the main impact was completed within 6 hours and 8 minutes.
   
   Root Cause
   Facility architecture and background:
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—where the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders (A and B) terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Uninterruptible Power Supply (UPS) battery systems provide five minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the

5. 28 Oct · 00:38 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific).
   
   ## Incident Report
   
   ### **Summary**
   
   On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
   
   The primary impact was mitigated after 6 hours 8 minutes.
   
   ### **Root Cause**
   
   **Facility architecture and background:**
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the facility had been placed in a temp

6. 28 Oct · 00:38 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific).
   
   Incident Report
   Summary
   On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
   
   The primary impact was mitigated after 6 hours 8 minutes.
   
   Root Cause
   Facility architecture and background:
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the facility had been placed in a temporary single-feed (1N) bri

7. 28 Oct · 00:37 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
   
   Incident Report
   Summary
   On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
   
   The primary impact was mitigated after 6 hours 8 minutes.
   
   Root Cause
   Facility architecture and background:
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the facility had been placed in a temporary single-feed (1N) bri

8. 28 Oct · 00:35 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
   
   Incident Report
   Summary
   On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
   
   The primary impact was mitigated after 6 hours 8 minutes.
   
   Root Cause
   Facility architecture and background:
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the facility had been placed in a temporary single-feed (1N) bri

9. 28 Oct · 00:32 UTC 🟠 Resolved atom

   Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
   
   Incident Report
   Summary
   On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
   
   The primary impact was mitigated after 6 hours 8 minutes.
   
   Root Cause
   Facility architecture and background:
   
   The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
   
   Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
   
   Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
   
   Prior to the utility disruption, the facility had been placed in a temporary single-feed (1N) bri

10. 28 Oct · 00:29 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Incident Report
    Summary
    On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
    
    The primary impact was mitigated after 6 hours 8 minutes.
    
    Root Cause
    Facility architecture and background:
    
    The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
    
    Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
    
    Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
    
    Prior to the utility disruption, the facility had been placed in a temporary single-feed (1N) bri

11. 27 Oct · 15:13 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Incident Report
    Summary
    On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. As traffic was redirected to alternative cloud regions or unaffected zones within europe-west2 cloud region, these workloads experienced transient latency and elevated errors affecting services across europe-west2. 
    
    The primary impact was mitigated after 6 hours 8 minutes.
    
    Root Cause
    Facility architecture and background:
    
    The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—meaning the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC).
    
    Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources.
    
    Static Uninterruptible Power Supply (UPS) battery systems provide 5 minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load.
    
    Prior to the utility disruption, the facility had been placed in a temporary single-feed (1N) bri

12. 27 Oct · 15:13 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific).
    
    Preliminary Incident Report
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue
    Incident Start:19 Oct 2026 23:00 US/Pacific / 20 Oct 2026 07:00 BST
    
    Incident End: 20 Oct 2026 05:10 US/Pacific / 20 Oct 2026 13:10 BST
    
    Duration: 6 hours, 10 minutes
    
    Summary
    On Monday, 19 October 2026 (Tuesday, 20 October BST), multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure. 
    
    Preliminary Root Cause
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up

13. 27 Oct · 15:13 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Preliminary Incident Report
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue
    Incident Start:19 Oct 2026 23:00 US/Pacific / 20 Oct 2026 07:00 BST
    
    Incident End: 20 Oct 2026 05:10 US/Pacific / 20 Oct 2026 13:10 BST
    
    Duration: 6 hours, 10 minutes
    
    Summary
    On Monday, 19 October 2026 (Tuesday, 20 October BST), multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure. 
    
    Preliminary Root Cause
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up

14. 22 Oct · 16:19 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Preliminary Incident Report
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue
    Incident Start:19 Oct 2026 23:00 US/Pacific / 20 Oct 2026 07:00 BST
    
    Incident End: 20 Oct 2026 05:10 US/Pacific / 20 Oct 2026 13:10 BST
    
    Duration: 6 hours, 10 minutes
    
    Summary
    On Monday, 19 October 2026 (Tuesday, 20 October BST), multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure. 
    
    Preliminary Root Cause
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up

15. 22 Oct · 09:24 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

16. 22 Oct · 09:21 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

17. 22 Oct · 09:20 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

18. 22 Oct · 09:18 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

19. 22 Oct · 09:16 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

20. 22 Oct · 09:14 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

21. 22 Oct · 09:12 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

22. 22 Oct · 09:10 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

23. 22 Oct · 09:08 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

24. 22 Oct · 09:04 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

25. 22 Oct · 08:42 UTC 🟠 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Preliminary Incident Report
    
    We recognize that Google Cloud services are critical to your organization, and we sincerely apologize for the disruption this incident may have caused to your business. 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.
    
    Date/Time of the Issue (All time US/Pacific)
    
    Incident Start: 19 October 2026 23:00
    
    Incident End: 20 October 2026 05:10
    
    Duration: 6 hours, 10 minutes
    
    Summary
    
    On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2 region experienced service disruptions, elevated error rates, Application Programming Interface (API) timeouts, and processing latency for a duration of 6 hours and 10 minutes. The disruption was triggered by an electrical power interruption at the datacenter facility hosting availability zone europe-west2-b, which temporarily took physical host servers, network routing hardware, and storage systems offline. This subsequently caused secondary failover and queuing delays across unimpacted regional infrastructure.
    
    Preliminary Root Cause
    
    The incident was triggered when a power grid disruption occurred at the datacenter facility hosting availability zone europe-west2-b. To maintain continuous power during the disruption, automatic transfer to facility backup power systems was triggered immediately. The facility load was transferred to the Uninterruptible Power Supply (UPS) battery banks during the start up sequence of on-site emergency diesel generators. The Programma

26. 22 Oct · 08:42 UTC 🟡 Monitoring atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:10 (all times are US/Pacific).
    
    Summary
    
    Multiple services were experiencing issues in the europe-west2 region.
    
    Description
    
    The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it.
    
    If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
    
    No further updates will be provided here.
    
    We will publish an analysis of this incident once we have completed our internal investigation.
    
    We thank you for your patience while we're working on resolving the issue.
    
    Symptoms
    
    Google Cloud services were unavailable in europe-west2-b zone; some services in europe-west2 region might experienced elevated errors and intermittent network issues.
    
    Workaround
    
    None as the issue has been mitigated.
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

27. 22 Oct · 08:42 UTC 🟡 Monitoring atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services were experiencing issues in the europe-west2 region.
    
    Description
    
    The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it.
    
    If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
    
    No further updates will be provided here.
    
    We will publish an analysis of this incident once we have completed our internal investigation.
    
    We thank you for your patience while we're working on resolving the issue.
    
    Symptoms
    
    Google Cloud services were unavailable in europe-west2-b zone; some services in europe-west2 region might experienced elevated errors and intermittent network issues.
    
    Workaround
    
    None as the issue has been mitigated.
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

28. 22 Oct · 07:51 UTC 🟡 Resolved atom

    Incident began at 2026-10-19 23:00 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services were experiencing issues in the europe-west2 region.
    
    Description
    
    The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it.
    
    If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
    
    No further updates will be provided here.
    
    We will publish an analysis of this incident once we have completed our internal investigation.
    
    We thank you for your patience while we're working on resolving the issue.
    
    Symptoms
    
    Google Cloud services were unavailable in europe-west2-b zone; some services in europe-west2 region might experienced elevated errors and intermittent network issues.
    
    Workaround
    
    None as the issue has been mitigated.
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

29. 20 Oct · 14:05 UTC 🟡 Resolved atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services were experiencing issues in the europe-west2 region.
    
    Description
    
    The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it.
    
    If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
    
    No further updates will be provided here.
    
    We will publish an analysis of this incident once we have completed our internal investigation.
    
    We thank you for your patience while we're working on resolving the issue.
    
    Symptoms
    
    Google Cloud services were unavailable in europe-west2-b zone; some services in europe-west2 region might experienced elevated errors and intermittent network issues.
    
    Workaround
    
    None as the issue has been mitigated.
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

30. 20 Oct · 14:05 UTC 🟡 Resolved atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    **Summary**
    
    Multiple services were experiencing issues in the europe-west2 region.
    
    **Description**
    
    The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it.
    
    If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
    
    No further updates will be provided here.
    
    We will publish an analysis of this incident once we have completed our internal investigation.
    
    We thank you for your patience while we're working on resolving the issue.
    
    **Symptoms**
    
    Google Cloud services were unavailable in europe-west2-b zone; some services in europe-west2 region might experienced elevated errors and intermittent network issues.
    
    **Workaround**
    
    None as the issue has been mitigated.Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

31. 20 Oct · 14:05 UTC 🟡 Resolved atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services were experiencing issues in the europe-west2 region.
    
    Description
    
    The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it.
    
    If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
    
    No further updates will be provided here.
    
    We will publish an analysis of this incident once we have completed our internal investigation.
    
    We thank you for your patience while we're working on resolving the issue.
    
    Symptoms
    
    Google Cloud services were unavailable in europe-west2-b zone; some services in europe-west2 region might experienced elevated errors and intermittent network issues.
    
    Workaround
    
    None as the issue has been mitigated.
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

32. 20 Oct · 14:03 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT.
    
    We will provide an update by Tuesday, 2026-10-20 07:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

33. 20 Oct · 13:22 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT.
    
    We will provide an update by Tuesday, 2026-10-20 07:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

34. 20 Oct · 13:09 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT.
    
    We will provide an update by Tuesday, 2026-10-20 07:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

35. 20 Oct · 13:05 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT.
    
    We will provide an update by Tuesday, 2026-10-20 07:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

36. 20 Oct · 12:58 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT.
    
    We will provide an update by Tuesday, 2026-10-20 07:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

37. 20 Oct · 12:52 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT.
    
    We will provide an update by Tuesday, 2026-10-20 07:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

38. 20 Oct · 12:45 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT.
    
    We will provide an update by Tuesday, 2026-10-20 07:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

39. 20 Oct · 12:44 UTC 🟠 Monitoring atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    **Summary**
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    **Description**
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    A power event caused an outage within europe-west2-b zone. The power event is mitigated. We are seeing the recovery of services and are prioritizing the recovery of existing workloads.Customers may not be able to yet create new workloads.
    
    Full recovery of existing workloads should be completed, tentatively by Tuesday, 2026-10-20 06:00.
    
    We will provide an update by Tuesday, 2026-10-20 06:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    **Symptoms**
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    **Workaround**
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-w

40. 20 Oct · 12:44 UTC 🟠 Monitoring atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    A power event caused an outage within europe-west2-b zone. The power event is mitigated. We are seeing the recovery of services and are prioritizing the recovery of existing workloads.Customers may not be able to yet create new workloads.
    
    Full recovery of existing workloads should be completed, tentatively by Tuesday, 2026-10-20 06:00.
    
    We will provide an update by Tuesday, 2026-10-20 06:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

41. 20 Oct · 12:44 UTC 🟠 Monitoring atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    A power event caused an outage within europe-west2-b zone. The power event is mitigated. We are seeing the recovery of services and are prioritizing the recovery of existing workloads.Customers may not be able to yet create new workloads.
    
    Full recovery of existing workloads should be completed, tentatively by Tuesday, 2026-10-20 06:00.
    
    We will provide an update by Tuesday, 2026-10-20 06:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

42. 20 Oct · 11:58 UTC 🟠 Investigating atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Due to a power event we had suffered an outage within europe-west2-b zone. The power event is mitigated. Partial mitigation to infrastructure services will be observed within the next 30 minutes and the remaining services will be mitigated there after.
    
    We will provide an update by Tuesday, 2026-10-20 05:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

43. 20 Oct · 11:58 UTC 🟠 Monitoring atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Due to a power event we had suffered an outage within europe-west2-b zone. The power event is mitigated. Partial mitigation to infrastructure services will be observed within the next 30 minutes and the remaining services will be mitigated there after.
    
    We will provide an update by Tuesday, 2026-10-20 05:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

44. 20 Oct · 11:58 UTC 🟠 Monitoring atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    A power event caused an outage within europe-west2-b zone. The power event is mitigated. We are seeing the recovery of services and are prioritizing the recovery of existing workloads.Customers may not be able to yet create new workloads.
    
    Full recovery of existing workloads should be completed, tentatively by Tuesday, 2026-10-20 06:00.
    
    We will provide an update by Tuesday, 2026-10-20 06:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

45. 20 Oct · 11:12 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 05:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

46. 20 Oct · 11:12 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 05:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

47. 20 Oct · 11:12 UTC 🟠 Monitoring atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Due to a power event we had suffered an outage within europe-west2-b zone. The power event is mitigated. Partial mitigation to infrastructure services will be observed within the next 30 minutes and the remaining services will be mitigated there after.
    
    We will provide an update by Tuesday, 2026-10-20 05:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Google Cloud services are unavailable in europe-west2-b zone; some services in europe-west2 region may experience elevated errors and intermittent network issues.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

48. 20 Oct · 11:00 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 05:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

49. 20 Oct · 11:00 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Cloud Run, Cloud Spanner, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

50. 20 Oct · 11:00 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Cloud Run, Cloud Spanner, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

51. 20 Oct · 10:01 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

52. 20 Oct · 09:50 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

53. 20 Oct · 09:48 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

54. 20 Oct · 09:24 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: Google Kubernetes Engine
    
    Affected locations: London (europe-west2)

55. 20 Oct · 09:24 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: Google Kubernetes Engine
    
    Affected locations: London (europe-west2)

56. 20 Oct · 09:24 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and
    intermittent network failures in europe-west2 region.
    
    Note: Looker Studio is not impacted by this outage.
    
    Workaround
    
    If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region).
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Cloud Run, Cloud Spanner, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

57. 20 Oct · 09:01 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Cloud Run, Cloud Spanner, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

58. 20 Oct · 08:55 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

59. 20 Oct · 08:51 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: AlloyDB for PostgreSQL, BigQuery Data Transfer Service, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service, Virtual Private Cloud (VPC)
    
    Affected locations: London (europe-west2)

60. 20 Oct · 08:49 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: BigQuery Data Transfer Service, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Cloud Run, Cloud Spanner, Google App Engine, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service
    
    Affected locations: London (europe-west2)

61. 20 Oct · 08:46 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: BigQuery Data Transfer Service, Cloud Filestore, Cloud Memorystore, Cloud Run, Google App Engine, Google Cloud Dataflow, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Persistent Disk, Storage Transfer Service
    
    Affected locations: London (europe-west2)

62. 20 Oct · 08:45 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: BigQuery Data Transfer Service, Cloud Filestore, Cloud Run, Google App Engine, Google Cloud Dataflow, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Persistent Disk, Storage Transfer Service
    
    Affected locations: London (europe-west2)

63. 20 Oct · 08:43 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: BigQuery Data Transfer Service, Cloud Filestore, Cloud Run, Google App Engine, Google Cloud NetApp Volumes, Google Kubernetes Engine, Looker (Google Cloud core), Managed Airflow, Google Cloud Composer, Managed Service for Apache Kafka, Persistent Disk
    
    Affected locations: London (europe-west2)

64. 20 Oct · 08:40 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: BigQuery Data Transfer Service, Cloud Filestore, Cloud Run, Google App Engine, Google Cloud NetApp Volumes, Google Kubernetes Engine
    
    Affected locations: London (europe-west2)

65. 20 Oct · 08:37 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: Cloud Filestore, Google Kubernetes Engine
    
    Affected locations: London (europe-west2)

66. 20 Oct · 08:36 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 01:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: Cloud Filestore, Google Kubernetes Engine
    
    Affected locations: London (europe-west2)

67. 20 Oct · 08:35 UTC 🟡 Investigating atom

    Incident began at 2026-10-19 23:08 (all times are US/Pacific).
    
    Summary
    
    Multiple services are experiencing issues in the europe-west2 region.
    
    Description
    
    We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.
    
    Our engineering team continues to investigate the issue.
    
    We will provide an update by Tuesday, 2026-10-20 01:30 PDT with current details.
    
    We apologize to all who are affected by the disruption.
    
    Symptoms
    
    Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region.
    
    Workaround
    
    None for now
    
    Affected products: Google Kubernetes Engine
    
    Affected locations: London (europe-west2)