rewindex

CompaniesCockroachDBIncidents

CockroachDB: gcp-eu-west2-b-availability-zone-issues

MajorStatus: resolvededitedStarted Resolved (7.0 h)4 updatesstspg.io (opens in new tab)
Part of an outage event

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

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

“…gcp-eu-west2-b-availability-zone-issues GCP has mitigated the power event that caused this disruption in the europe-west2 region. All GCP and CRL services has returned to normal operation. No further…”

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, ConfluentCockroachDB (this incident)posted +1 h 46 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, ConfluentCockroachDB (this incident)posted +1 h 46 min
CockroachDB 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["CockroachDB (this incident)<br/>posted +1 h 46 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: CockroachDB AdvancedCockroachDB Cloud - CockroachDB AdvancedCockroachDB Basic/StandardCockroachDB Cloud - CockroachDB Basic/Standard

Timeline of updates

  1. investigating

    GCP europe-west2-b and availability zone is currently experiencing issues.
    We will continue to monitor this situation and update status once we have more information.

  2. identified

    GCP has mitigated the power event that caused this disruption in the europe-west2 region and is working on mitigating impacted services. We will update once we have confirmation of mitigation.

  3. monitoring

    GCP has mitigated the power event that caused this disruption in the europe-west2 region and most GCP services have recovered. We will continue to track and ensure impacted CRL services return to normal operation before resolving.

  4. resolved

    GCP has mitigated the power event that caused this disruption in the europe-west2 region. All GCP and CRL services has returned to normal operation.
    No further action is required.

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 stspg.io (opens in new tab).

CockroachDB profileRecent CockroachDB incidentsMarkdownJSON