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 updateNormal progress (rule, 100%)Changed 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.

ChangedStatus#1
Before: investigating
After: identified
AddedUpdateidentified#2
Before: not present
After: Our cloud provider has confirmed an infrastructure incident affecting a single availability zone (europe-west2-b) in the GCP europe-west2 (London) region, causing network connectivity loss and resource unavailability in that zone. Elastic Cloud Hosted deployments and Elastic Serverless projects with resources in the affected zone may be unavailable or experience degraded performance. We have taken steps to avoid placing new Serverless projects in the affected zone, and we are working to restore services that depend on it. Reduced capacity in the region may delay scaling and the creation of new resources. We do not yet have an estimated time for recovery from our cloud provider. We are working closely with them and will provide the next update within an hour.

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