Companies / Elastic Cloud / incidents

Elastic Cloud: Upstream Azure Outage Causing Service Degradation

Impact: majorStatus: resolvedStarted Resolved (3 d)9 updatesSource: stspg.io (opens in new tab)
Summary

An upstream Azure outage caused major degradation in Azure West US 2 (azure-westus2), limited to westus2-2, including Elastic Serverless projects. Non-high-availability deployments experienced connectivity errors, degraded performance and deployment-operation delays. The incident lasted 2 days 15 h, from 2026-05-29 06:32 UTC to 2026-05-31 21:33 UTC, with remediation and case-by-case support before resolution.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Azure Washington (azure-westus2) - APM connectivity: Azure azure-westus2Azure Washington (azure-westus2) - Kibana connectivity: Azure azure-westus2Azure Washington (azure-westus2) - Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Azure - Washington (azure-westus2) - Azure Infrastructure HealthAzure Washington (azure-westus2) - Azure Infrastructure health: azure-westus2Azure Washington (azure-westus2) - Elasticsearch connectivity: Azure azure-westus2

Timeline of updates

  1. investigating

    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.

  2. investigating

    We are continuing to investigate this issue.

  3. investigating

    We are continuing to investigate this issue.

  4. identified

    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.

  5. identified

    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.

  6. identified

    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

  7. monitoring

    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.

  8. monitoring

    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.

  9. resolved

    This incident has been resolved.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Elastic Cloud profile · Recent Elastic Cloud incidents · Markdown · JSON