Elastic Cloud incident
Upstream Azure Outage Causing Service Degradation
Elastic Cloud is currently experiencing a major incident affecting Elasticsearch connectivity: Azure azure-westus2 and Azure Infrastructure Health and 1 more component, which began 2d ago. The vendor's full update timeline is below.
Affected components
Update timeline
- investigating May 29, 2026, 06:32 AM UTC
We are currently investigating Azure WestUS2 network services degradation that is impacting connectivity towards Elastic services and deployments healthiness. At this time, the issue appears to be related to the upstream cloud provider. Users may experience intermittent errors, delays, or inability to access certain features. Our team is actively monitoring the situation and assessing the impact on our environment. We will provide further updates as more information becomes available.
- investigating May 29, 2026, 06:35 AM UTC
We are continuing to investigate this issue.
- investigating May 29, 2026, 06:50 AM UTC
We are continuing to investigate this issue.
- identified May 29, 2026, 10:43 AM UTC
We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region. We have confirmed that impact to our service is limited to a single availability zone (westus2-2). Customers whose deployments are not configured for high availability may experience intermittent errors, delays, or inability to access certain features. Deployments configured for high availability across multiple zones are not expected to be affected. Our team is working to mitigate the situation and the impact on our environment. We will provide further updates as more information becomes available.
- identified May 29, 2026, 11:46 AM UTC
We continue to respond to an upstream Microsoft Azure outage in Azure West US 2 (azure-westus2), caused by a datacenter power event reported by Azure. Elastic impact remains limited to availability zone westus2-2. Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations (including create, edit, restart, and delete). Deployments configured for high availability across multiple availability zones are not expected to be affected. Our teams are actively remediating affected infrastructure in the impacted zone. Recovery progress is currently constrained by degraded Azure platform APIs and capacity availability in the region.
- identified May 29, 2026, 02:26 PM UTC
We continue to remediate the impact of an upstream Azure outage in Azure West US 2 (azure-westus2), limited to availability zone westus2-2. Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations. Deployments configured for high availability across multiple availability zones are not expected to be affected. Our teams remain actively engaged with Microsoft Azure and are working to restore affected infrastructure. We will provide further updates as recovery progresses
- monitoring May 29, 2026, 06:50 PM UTC
Remediation is underway and systems are recovering. We continue to monitor the situation and will post an update in the next 2 hours or earlier.
- monitoring May 30, 2026, 06:36 AM UTC
We continue to monitor the situation which has mostly recovered. A small number of deployments are still not healthy. Our support team is working on resolving these on a case-by-case basis.