Elastic Status · History · Incident #4125
RESOLVEDUpstream Azure Outage Causing Service Degradation
Major · Started May 29, 2026 · 6:32 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Elastic Status · History · Incident #4125
RESOLVEDMajor · Started May 29, 2026 · 6:32 AM
Duration
2d 15h 1m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
May 29, 2026 · 6:32 AM
Resolved
May 31, 2026 · 9:33 PM
Duration
2d 15h 1m
Severity
Major
Event timeline
Investigating
May 29 · 6:32 AM ElasticWe 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.
Investigating
May 29 · 6:35 AM ElasticWe are continuing to investigate this issue.
Investigating
May 29 · 6:50 AM ElasticWe are continuing to investigate this issue.
Identified
May 29 · 10:43 AM ElasticWe 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 · 11:46 AM ElasticWe 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 · 2:26 PM ElasticWe 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 · 6:50 PM ElasticRemediation 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 · 6:36 AM ElasticWe 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.
Resolved
May 31 · 9:33 PM ElasticThis incident has been resolved.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT