rewindex

ChangesElastic CloudDegraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)

Elastic Cloud: Incident updated: Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)

Incident updateNot classified yetChanged stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

Part of an outage event

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

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

“…Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London) The infrastructure incident at our cloud provider affecting availability zone europe-west2-b…”

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

AddedUpdateidentified#1
Before: not present
After: The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. We are seeing slight signs of recovery, both from our cloud provider and from our own mitigation work. Elastic Cloud Hosted: Some of the affected deployments are recovering. Customers whose plan changes or other operations failed during the incident are advised to retry them from the Elastic Cloud console. Operations that depend on the affected zone may take longer than usual, or fail again, until recovery progresses further. Some deployments may remain unavailable or degraded. Elastic Serverless: Some projects may remain unavailable or degraded.

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

YesterdayTuesday, October 20Tue, Oct 20

8 incident changes

All Elastic Cloud changesElastic Cloud profileMarkdownJSON