rewindex

CompaniesClickHouse CloudIncidents

ClickHouse Cloud: Google Cloud Outage

MinorStatus: resolvededitedStarted Resolved (4.3 h)6 updatesstatus.clickhouse.com (opens in new tab)
Part of an outage event

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

ClickHouse Cloud’s incident blames Google Cloud as the cause. (hop 1, posted +3 h 56 min vs Google Cloud’s own post)

“…Google Cloud Outage The issue has been resolved. All services are fully operational. Google Cloud has reported that multiple services are experiencing issues in the europe-west2 region. We are working…”

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, ClickHouseCloudLater2 vendors, 1 blamed Google CloudGrafana Cloud, ConfluentClickHouse Cloud (this incident)posted +3 h 56 min
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, ConfluentClickHouse Cloud (this incident)posted +3 h 56 min
ClickHouse Cloud 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
  me["ClickHouse Cloud (this incident)<br/>posted +3 h 56 min"]:::me
  h4 --- 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: GCP europe-west2

Timeline of updates

  1. identified

    Google Cloud has reported that multiple services are experiencing issues in the europe-west2 region. We are working closely with Google support to restore normal behavior and will provide an update as soon as we have more information.

  2. identified

    This is attributed to a Google outage in europe-west2.

    Latest updates from Google can be found at:
    https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj (opens in new tab)

    Currently only zone B is impacted. We are migrating workloads away from this zone.

  3. identified

    This is attributed to a Google outage in europe-west2.

    Latest updates from Google can be found at:
    https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj (opens in new tab)

    Currently only zone B is impacted. Clusters in this region should be operational - accepting reads and writes, but provisioning of new services currently blocked until this zone is operational.

  4. identified

    The zone is recovering. Clickpipes is fully restored but we continue to monitor until google reports all issues have been resolved.

  5. monitoring

    We do not see any current impact on clickpipes or ClickHouse services, with full service restored. Google has not marked the incident as resolved, so we continue to monitor.

  6. resolved

    The issue has been resolved. All services are fully operational.

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.

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

Rewindex captured this after the last checkpoint; the next run () commits it.

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

ClickHouse Cloud profileRecent ClickHouse Cloud incidentsMarkdownJSON