rewindex

ChangesLookerMultiple services are experiencing issues in the europe-west2 region.

Looker: Incident updated: Multiple services are experiencing issues in the europe-west2 region.

Incident updateNormal progress (rule, 100%)Changed status.cloud.google.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Discussed on Hacker News

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

Incident page: the full timeline of updates

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)

See the cascade chart and every vendor →

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.

What changed

Struck in red is what Looker removed; blue is what they added. Muted text is unchanged context.

AddedUpdateservice_disruption#1
Before: not present
After: **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).

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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.

History of this incident

TodayThursday, October 22Thu, Oct 22

2 rewrites

Tuesday, October 20

9 incident changes

All Looker changesLooker profileMarkdownJSON