rewindex

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

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

Silent editWording only (typesafe/jev-1.13-20260917, 94%)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.

ChangedUpdateresolved#1
Before: …sources. Uninterruptible Power Supply (UPS) battery systems provide nothing here five minutes of autonomous runtime. This bridge power…
After: …sources. Uninterruptible Power Supply (UPS) battery systems provide approximately five minutes of autonomous runtime. This bridge power…
Before: …a timeout or error code during the disruption. Any workloads and resources hosted entirely within europe-west2-b became unreachable…
After: …a timeout or error code during the disruption. Workloads and resources hosted entirely within europe-west2-b became unreachable…
Before: …impact and next steps for each impacted product. **Google Compute Engine and Persistent Disk** Google Compute Engine and Persistent Disk **Impact:** Upon…
After: …impact and next steps for each impacted product. ### Google Compute Engine and Persistent Disk **Impact:** Upon…
Before: …Upon power loss, Cloud SQL detected failures and nothing here initiated automated failovers for all regional HA instances.…
After: …Upon power loss, Cloud SQL detected failures and immediately initiated automated failovers for all regional HA instances.…
Before: …immediately initiated automated failovers for all regional HA instances immediately. The failover finished successfully for 48.5% of these regional instances, mitigating their impact right away. Recovery for the remaining instances was extended primarily due to Regional Persistent Disk failures (see above), mitigating their…
After: …immediately initiated automated failovers for all regional HA instances. The failover was complete for regional instances that did not have Regional Persistent Disk failures (see above), mitigating their…
Before: …not have Regional Persistent Disk failures (see above), specifically device stalls. 99.95% of Cloud SQL zonal instances recovered automatically by 20 Oct 2026, 05:15 US/Pacific (13:15 BST), shortly after europe-west2-b recovered. **Next Steps:** Our engineering team is implementing improvements…
After: …not have Regional Persistent Disk failures (see above), mitigating their impact right away. A majority of the remaining instances recovered by 20 Oct 2026, 01:00 US/Pacific (09:00 BST) once the Regional Persistent Disk recovered, shortly after europe-west2-b recovery. A small number of remaining instances were fully recovered by 20 Oct 2026, 11:00 US/Pacific (19:00 BST). **Next Steps:** Our engineering team is implementing improvements…
Before: …with sufficient capacity to absorb the failover load. nothing here We did not identify any impact of the…
After: …with sufficient capacity to absorb the failover load. ### List of impacted services We did not identify any impact of the…

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 this record existed by then and has 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.

History of this incident

TodayThursday, November 5Thu, Nov 5

1 rewrite

YesterdayWednesday, November 4Wed, Nov 4

1 incident change

Wednesday, October 28

1 incident change

Tuesday, October 27

1 incident change

Thursday, October 22

3 rewrites, 2 incident changes

Tuesday, October 20

9 incident changes

Cite this

Incident silently edited: Multiple services were experiencing issues in the europe-west2 region. on Looker’s status page, changed 2026-11-05 06:23 UTC (change 18 of 18).

Title
Incident silently edited: Multiple services were experiencing issues in the europe-west2 region.
Vendor
Looker
Date
URL
https://rewindex.com/change/r72cda4a1ae9631

All Looker changesLooker profileMarkdownJSON