rewindex

ChangesGoogle CloudMultiple services were experiencing issues in the europe-west2 region.

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

Silent editWording only (typesafe/jev-1.13-20260917, 96%)Changed status.cloud.google.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Discussed on Hacker News

Top 3 of 6 linked threads by points and comments. 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

Google Cloud’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 Google Cloud removed; blue is what they added. Muted text is unchanged context.

ChangedUpdateresolved#1
Before: …please reach out to Google Cloud Support using https://cloud.google.com/support. **Date/Time of the Issue (All time US/Pacific)** Incident Start: 19 October 2026 23:00 Incident End: 20 October 2026 05:10 Duration: 6 hours, 10 minutes **Summary** On Monday, 19 October 2026, multiple Google Cloud Platform services in the europe-west2…
After: …please reach out to Google Cloud Support using [**https\://cloud.google.com/support**](https://cloud.google.com/support). ## Date/Time of the Issue Incident Start:19 Oct 2026 23:00 US/Pacific / 20 Oct 2026 07:00 BST Incident End: 20 Oct 2026 05:10 US/Pacific / 20 Oct 2026 13:10 BST Duration: 6 hours, 10 minutes ## Summary On Monday, 19 October 2026 (Tuesday, 20 October BST), multiple Google Cloud Platform services in the europe-west2…
Before: …events leading to customer impact was as follows: - At 22:53 US/Pacific, an electrical power disruption occurred at the datacenter…
After: …events leading to customer impact was as follows: * At 22:53 US/Pacific (20 Oct, 06:53 BST), an electrical power disruption occurred at the datacenter…
Before: …until the batteries were depleted, starting at 23:00 US/Pacific. - When the physical host servers, local storage infrastructure,…
After: …until the batteries were depleted, starting at 23:00 US/Pacific (20 Oct, 07:00 BST). * When the physical host servers, local storage infrastructure,…
Before: …monitoring systems and probers at 23:08 US/Pacific on Monday, 19 October 2026, which detected elevated API error ratios, job submission…
After: …monitoring systems and probers at 23:08 US/Pacific on 19 Oct (20 Oct, 07:08 BST), which detected elevated API error ratios, job submission…
Before: …clear smoothly. By 05:10 US/Pacific on Tuesday, 20 October 2026, service availability had recovered for the vast majority…
After: …clear smoothly. By 05:10 US/Pacific on Tuesday, 20 Oct(13:10 BST), service availability had recovered for the vast majority…
Before: …notification for the incident was posted by 07:03 US/Pacific. **Description of Impact** Between Monday, 19 October 2026, 23:00 and Tuesday, 20 October 2026, 05:10 US/Pacific (13:10…
After: …notification for the incident was posted by 07:03 US/Pacific (15:03 BST). ## Description of Impact Between Monday, 19 Oct 2026, 23:00 US/Pacific (Tuesday, 20 Oct 2026, 07:00 BST) and Tuesday, 20 October 2026, 05:10 US/Pacific (13:10…
Before: …07:00 BST) and Tuesday, 20 October 2026, 05:10 US/Pacific, customers utilizing Google Cloud Platform services in the…
After: …07:00 BST) and Tuesday, 20 October 2026, 05:10 US/Pacific (13:10 BST), customers utilizing Google Cloud Platform services in the…
Before: …the initial phase from 23:00 to 04:29 US/Pacific nothing here (duration 5 hours, 29 minutes), customers experienced elevated…
After: …the initial phase from 23:00 to 04:29 US/Pacific (07:00 to 12:29 BST) (duration 5 hours, 29 minutes), customers experienced elevated…
Before: …experienced a longer recovery tail. By 04:46 US/Pacific nothing here new Virtual Machine creation resumed and by 05:10…
After: …experienced a longer recovery tail. By 04:46 US/Pacific (12:46 BST) new Virtual Machine creation resumed and by 05:10…
Before: …Virtual Machine creation resumed and by 05:10 US/Pacific nothing here over 99% of Compute Engine Virtual Machines were…
After: …Virtual Machine creation resumed and by 05:10 US/Pacific (13:10 BST) over 99% of Compute Engine Virtual Machines were…
Before: …in a healthy state. Any remaining customers that are experiencing Virtual Machine problems should file a customer support issue as per normal…
After: …in a healthy state. Any remaining customers that were experiencing Virtual Machine problems were directed to file a customer support issue as per normal…

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

Wednesday, October 28

1 incident change

Tuesday, October 27

1 incident change

Thursday, October 22

3 rewrites, 2 incident changes

Tuesday, October 20

10 incident changes

Cite this

Incident silently edited: Multiple services were experiencing issues in the europe-west2 region. on Google Cloud’s status page, changed 2026-10-22 16:23 UTC (change 15 of 17).

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

All Google Cloud changesGoogle Cloud profileMarkdownJSON