Is Google Cloud down? › Outage history › Oct 20, 2026

Google Cloud partial outage on Oct 20, 2026: what happened

On Oct 20, 2026, the Google Cloud status dashboard reported "Multiple services were experiencing issues in the europe-west2 region.". About 6 hours 10 min: from Oct 20, 2026, 06:00 UTC to Oct 20, 2026, 12:10 UTC, by the official start and resolution times.

Google Cloud right now

At our last refresh (Oct 22, 2026, 12:35 UTC) Google Cloud was up: No open incidents on the Google Cloud status dashboard.

Is Google Cloud down right now? →
Started
Oct 20, 2026, 06:00 UTC
Resolved
Oct 20, 2026, 12:10 UTC
Duration
6 hours 10 min
Official impact
Service disruption
Affected
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), 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)

The Google Cloud status dashboard rated the impact "Service disruption": a partial outage. Some parts or some users were affected; it was not a complete outage.

What caused the Google Cloud partial outage?

"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."

From the Google Cloud status dashboard, Oct 22, 2026, 08:42 UTC.

When was it fixed?

The Google Cloud status dashboard marked it resolved at Oct 20, 2026, 12:10 UTC, 6 hours 10 min after it started. Its resolution note: "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, ..."

Timeline of official updates

Every update the Google Cloud status dashboard posted, oldest first. Times are UTC.

  1. Oct 20, 2026, 08:35 UTC service disruption

    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

  2. Oct 20, 2026, 09:24 UTC service disruption

    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).

  3. Oct 20, 2026, 11:00 UTC service disruption

    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).

  4. Oct 20, 2026, 11:12 UTC service disruption

    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).

  5. Oct 20, 2026, 11:58 UTC service disruption

    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).

  6. Oct 20, 2026, 12:44 UTC service disruption

    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).

  7. Oct 20, 2026, 14:03 UTC service disruption

    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.

  8. Oct 22, 2026, 08:42 UTC resolved

    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 Programmable Logic Controller (PLC) automation system (both primary and backup PLCs) failed to initiate the logical automatic start/transfer operations of the generators, preventing backup generators from assuming the load. When UPS battery reserves were depleted, physical host servers, network switching fabric, and local storage arrays dedicated to europe-west2-b lost power and went offline. The sequence of events leading to customer impact was as follows: - At 22:53 US/Pacific, an electrical power disruption occurred at the datacenter facility hosting availability zone europe-west2-b, and a PLC ...

What our checks saw

Google Cloud partial outage questions

What caused the Google Cloud partial outage on Oct 20, 2026?

The Google Cloud status dashboard said (update at Oct 22, 2026, 08:42 UTC): "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."

When was the Google Cloud partial outage on Oct 20, 2026 fixed?

The Google Cloud status dashboard marked it resolved at Oct 20, 2026, 12:10 UTC, 6 hours 10 min after it started. Its resolution note: "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, ..."

How long did the Google Cloud partial outage last?

About 6 hours 10 min: from Oct 20, 2026, 06:00 UTC to Oct 20, 2026, 12:10 UTC, by the official start and resolution times.

Was Google Cloud completely down?

No. The Google Cloud status dashboard rated the impact "Service disruption": a partial outage. Some parts or some users were affected; it was not a complete outage. The affected parts listed were: 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), 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).

Which parts of Google Cloud were affected?

The Google Cloud status dashboard listed: 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), 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).

Other recent Google Cloud incidents

Full Google Cloud outage history and biggest outages → · Recent outages across all services →

Quotes are the Google Cloud status dashboard's own words, from the official incident. Is It Up or Down is independent and not affiliated with Google Cloud. Times are UTC.