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 in the GCP europe-west2 (London) region has been resolved. Engineering has completed recovery of infrastructure running in the affected availability zone. Elastic Cloud Hosted: Customers whose plan changes or other operations failed during the incident are advised to retry them from the Elastic Cloud console. Some deployments may still be unavailable or degraded, and may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support.
The latest update from Elastic Cloud.
State
Resolved
Started
12 d ago
2026-10-20 06:51 UTC
Lasted
15 h 3 min
until 2026-10-20 21:54 UTC
Worst impact
Partial outage
Timeline
8 updatesInvestigating
1 h 6 min 7%
Identified
13 h 57 min 93%
Updates
Times in UTCAs posted by Elastic Cloud
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. Engineering has completed recovery of infrastructure running in the affected availability zone. Elastic Cloud Hosted: Customers whose plan changes or other operations failed during the incident are advised to retry them from the Elastic Cloud console. Some deployments may still be unavailable or degraded, and may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support.
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. We are continuing to work towards full recovery of our services. Elastic Cloud Hosted: An increasing number of 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. Some deployments may still be unavailable or degraded, and some may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support. Operations may take longer than usual while capacity is restored.
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is recovering. Our cloud provider reports recovery of services for most workloads in the region, and we are seeing progress on our side as the affected zone comes back. Elastic Cloud Hosted: An increasing number of 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. Some deployments may still be unavailable or degraded, and some may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support. Operations may take longer than usual while capacity is restored.
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.
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. Elastic Cloud Hosted deployments and Elastic Serverless projects with resources in the affected zone may remain unavailable or degraded. Our teams are continuing to work on mitigation and recovery, and we are working closely with our cloud provider. We do not yet have an estimated time for full recovery. We will provide the next update by 12:00 UTC, or sooner if there is a significant change.
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. Elastic Cloud Hosted: Most deployments with resources in the affected zone remain unavailable or degraded. We are seeing early, limited signs of recovery, and a small number of the initially affected deployments are recovering. We are continuing our mitigation work and will share more as recovery progresses. Elastic Serverless: We have taken steps to avoid placing new projects in the affected zone, and we are now rebalancing existing projects to other availability zones. We are seeing signs of recovery - some projects remain unavailable or degraded in the meantime. Reduced capacity in the region may delay scaling and the creation of new resources. We do not yet have an estimated time for full recovery from our cloud provider. We are working closely with them and will provide the next update by 10:15am UTC.
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.
We are investigating an issue affecting one availability zone in the GCP europe-west2 (London) region. Starting at approximately 06:15 UTC, some Elastic Cloud Hosted and Serverless deployments with capacity in this zone may experience degraded availability or connectivity. Monitoring and logging for deployments in the region may also be delayed. Deployments in other zones and regions are not affected. Our engineers are actively working on the issue, and we are in contact with our cloud provider.
Elastic Cloud in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
90
Median duration
4 h 48 min
This incident
3.1× the median
Other Elastic Cloud incidents
All incidentsElastic Cloud·Elastic Support Portal is unavailable
The upstream provider has completed its fix, and access to the Elastic Support portal has been restored. Customers can authenticate to the support portal again. We are considering this issue resolved and will be providing no further updates. If you continue to have issues, please contact us.
Elastic Cloud·403 error when trying to access Autoops in newly created serverless projects
We resolved the issue affecting AutoOps at 12:30 UTC. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it.
Elastic Cloud·Elastic Cloud scaling issues in Azure
Engineers have mitigated an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. Scaling is working as expected.
Elastic Cloud·Delayed or Unavailable project operation in GCP us-central1
The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.
Elastic Cloud·Delayed Serverless Metrics in Azure UAE North region
The issue affecting metric availability for Serverless projects in Azure UAE North has been resolved. Delayed “Usage and performance” metrics are now recovering, and queued usage records are being processed. No data loss is expected.
Follow Elastic Cloud
Your coding agent knows when Elastic Cloud is down, and tells you when a failure is theirs, not yours. You can also get Elastic Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "elastic" and tell me if Elastic Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=elastic/feed subscribe https://outages.cc/feed.xml?providers=elasticFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane