rewindex

RewindexOutage eventsOct 20, 2026

Google Cloud europe-west2 outage, Oct 20, 2026

17 vendors posted 17 incidents between and , against about 36 incidents from 26 vendors in the same hours on an ordinary week. 11 vendors named Google Cloud in 11 incidents (10 of them blamed it), and 1 did so before Google Cloud’s own status page. Google Cloud posted “Multiple services are experiencing issues in the europe-west2 region.” at 06:08 UTC.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are in UTC; lags are from when Google Cloud posted ().

    19. Google Cloud posted first vendor named Google Cloud
Named Google CloudNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Google Cloud, grouped by when they posted, and vendors that blamed one of the vendors Google Cloud took down. Solid lines: the vendor named the other. Dashed: same window, not named.

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
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
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

Vendors that named Google Cloud

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Posted before Google Cloud did

1 vendor

Within an hour

4 vendors

1 to 4 hours later

4 vendors

  • +1 h 25 min

    Blames Google Cloud

    Minor incident

    MongoDB AtlasGCP Availability Zone europe-west2-b connectivity issues

    …GCP Availability Zone europe-west2-b connectivity issues This incident has been resolved. Since 0600 UTC we have observed cluster node connectivity issues isolated to a single availability zone, GCP e…

  • +1 h 31 min

    Blames Google Cloud

    Minor incident

    SourcegraphSourcegraph Cloud is degraded in Europe region

    …aph Cloud customers in Europe. This is related to an ongoing incident with our underlying Google Cloud infrastructure. Our team is actively monitoring the situation and working with Google Cloud as th…

  • +1 h 46 min

    Blames Google Cloud

    Major incident

    CockroachDBgcp-eu-west2-b-availability-zone-issues

    …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…

  • +3 h 56 min

    Blames Google Cloud

    Minor incident

    ClickHouse CloudGoogle Cloud Outage

    …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…

Later

2 vendors

Same window, did not name anyone

6 incidents started during the event without naming Google Cloud or another vendor. Some are part of it, some are a normal day’s background (about 36 in these hours).

Show all 6

Detected automatically from 9 status pages opening incidents in the peak hour (normally at most 8). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.