rewindex

CompaniesLookerIncidents

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

MinorStatus: resolvededitedStarted Resolved (8.0 h)7 updatesstatus.cloud.google.com (opens in new tab)
Part of an outage event

Google Cloud europe-west2 outage, Oct 20, 2026 · 13 vendors, 13 incidents

Looker’s incident is the root of the event (the provider’s own post). (root, posted +0 min vs Google Cloud’s own post)

Swipe sideways to see the whole diagram.

Google Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed Google CloudJFrogWithin an hour4 vendors, 4 blamed Google CloudAiven, Northflank, Elastic Cloud, dbt Labs1 to 4 hours later4 vendors, 4 blamed Google CloudMongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse CloudLater2 vendors, 1 blamed Google CloudGrafana Cloud, Confluent
Google Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed GoogleCloudJFrogWithin an hour4 vendors, 4 blamed GoogleCloudAiven, Northflank, Elastic Cloud,dbt Labs1 to 4 hours later4 vendors, 4 blamed GoogleCloudMongoDB Atlas, Sourcegraph,CockroachDB, ClickHouseCloudLater2 vendors, 1 blamed GoogleCloudGrafana Cloud, Confluent
Looker is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud europe-west2<br/>posted 06:08 UTC"]:::root
  before["Posted before Google Cloud did<br/>1 vendor, 1 blamed Google Cloud<br/>JFrog"]:::blames
  root --> before
  h1["Within an hour<br/>4 vendors, 4 blamed Google Cloud<br/>Aiven, Northflank, Elastic Cloud, dbt Labs"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Google Cloud<br/>MongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse Cloud"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 1 blamed Google Cloud<br/>Grafana Cloud, Confluent"]:::blames
  root --> later
  class root me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: AlloyDB for PostgreSQLApigeeBigQuery Data Transfer ServiceCloud Data FusionCloud FilestoreCloud FirestoreCloud Load BalancingCloud MemorystoreCloud NATCloud RunCloud SpannerCloud WorkstationsDatastreamGoogle App EngineGoogle BigQueryGoogle Cloud BigtableGoogle Cloud ComposerGoogle Cloud DataflowGoogle Cloud DataprocGoogle Cloud NetApp VolumesGoogle Cloud Pub/SubGoogle Cloud SQLGoogle Cloud StorageGoogle Compute EngineGoogle Kubernetes EngineLooker (Google Cloud core)Managed Service for Apache KafkaMemorystore for MemcachedMemorystore for RedisMemorystore for Redis ClusterMemorystore for ValkeyNetwork Connectivity CenterPersistent DiskPrivate Service ConnectSpeech-to-TextStorage Transfer ServiceVirtual Private Cloud (VPC)VMWare engine

Discussed on Hacker News

Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.

Timeline of updates

  1. 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. 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. 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. 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. 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. 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. resolved

    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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.cloud.google.com (opens in new tab).

Looker profileRecent Looker incidentsMarkdownJSON