Live / Elastic Cloud (Public) / Incident
Elastic Cloud (Public): Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)
Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-10-20 21:54 UTC
Public — what happened
Summary
Elastic Cloud said some Elastic Cloud Hosted deployments and Serverless projects with resources in one zone (europe-west2-b) of Google Cloud's London region were unavailable or running poorly, starting at about 06:15 UTC on 2026-10-20. The company said its cloud provider confirmed an infrastructure problem in that zone, and that it stopped placing new Serverless projects there and moved existing ones to other zones. Elastic said recovery began slowly in the morning, the provider's issue was resolved by 17:27 UTC, and some deployments still needed extra recovery work with its Support team. The incident was marked resolved at 21:54 UTC, and customers whose operations had failed were advised to retry them.
Timeline
- Started — 2026-10-20 06:51 UTC
- Investigating — 2026-10-20 06:51 UTC
- Identified — 2026-10-20 07:56 UTC (6 updates)
- Resolved — 2026-10-20 21:54 UTC · 15h 03m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Elastic Cloud (Public) against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Elastic Cloud (Public): its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Elastic Cloud (Public) report →
More from Elastic Cloud (Public)
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.