Is Elastic Cloud down?
Last checked 6m agoActive incident: Connectivity disruption for AWS Bahrain (me-south-1)
Elastic Cloud is reporting a major outage right now (last checked 6m ago). 1 active incident on the official status page.
Real-time Elastic Cloud status, recent outages, and incident history — pulled directly from Elastic Cloud's official status page at https://status.elastic.co every 5 minutes. Pingoru tracks 544 Elastic Cloud services and has captured 22 incidents in the last 90 days (99.73% uptime). Get email, Slack, Discord, or webhook alerts the moment Elastic Cloud reports a new incident — free for 5 monitors, no credit card.
Active incident 1
- AWS EC2 Health: me-south-1Snapshot Storage Infrastructure (S3): me-south-1Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1APM connectivity: AWS me-south-1AWS Infrastructure health: me-south-1Elasticsearch connectivity: AWS me-south-1Kibana connectivity: AWS me-south-1
Timeline · 10 updates
- identified · Mar 02, 2026, 06:23 AM UTC
We are aware of connectivity and power issues affecting AWS Bahrain (me-south-1) due to localized power issues. We are awaiting further updates from AWS and will update here once we have more information.
- identified · Mar 09, 2026, 03:01 PM UTC
This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Mar 16, 2026, 07:46 PM UTC
This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Mar 23, 2026, 04:20 PM UTC
There are no new updates. This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Mar 24, 2026, 09:29 AM UTC
We have identified a further potential disruption to our services hosted in the AWS Bahrain (me-south-1) region. We are working to determine the scope of this impact, and have engaged with AWS as the providers in this investigation. Further updates will be posted within the hour, or when we have further information.
- identified · Mar 24, 2026, 11:09 AM UTC
This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Apr 02, 2026, 12:00 AM UTC
As this incident remains ongoing with no recovery timeline provided by AWS, we have removed AWS Bahrain (me-south-1) from the available region selection on cloud.elastic.co. The region is currently unavailable for the creation of new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS connectivity disruption. Customers in this region should continue to work through Elastic support channels. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].
- identified · Apr 20, 2026, 05:46 PM UTC
Update — This incident remains ongoing. AWS Bahrain (me-south-1) has been removed from the available region selection on cloud.elastic.co and is unavailable for new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS infrastructure disruption. AWS has not provided a recovery timeline for the region. Customers should continue to assume the region is unavailable for the foreseeable future. We continue to support impacted customers individually through our support channels. If you have not yet done so, please open a case so we can assist with your recovery options. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:[email protected]. Apr 20, 2026 — 00:00 UTC
- identified · May 18, 2026, 04:33 PM UTC
Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].
- identified · Jun 01, 2026, 05:13 PM UTC
Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].
Latest: Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infr…
-
Recent outages & incidents
Past 90 days-
Timeline · 4 updates
- investigating · Jun 04, 2026, 01:51 AM UTC
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are currently investigating the issue.
- monitoring · Jun 04, 2026, 03:44 AM UTC
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. Recovery has started and we will provide further updates as we progress.
- monitoring · Jun 04, 2026, 06:21 AM UTC
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are seeing increased recovery across as we monitor the situation. Services are being restored. Monitoring is continuing, and we will provide further updates as we progress.
- resolved · Jun 04, 2026, 09:20 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Cloud console
Timeline · 3 updates
- investigating · Jun 02, 2026, 01:25 PM UTC
Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 1 hour
- investigating · Jun 02, 2026, 03:02 PM UTC
We are seeing some signs of recovery, and have taken action to mitigate the impact and speed up recovery. Some users will still see seeing missing metrics visualizations in the Cloud console, for deployments in the Azure North Europe region. We are actively investigating and will provide another update within 1 hour
- resolved · Jun 02, 2026, 07:50 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 2 updates
- investigating · May 29, 2026, 06:00 PM UTC
We're aware of an issue with creating Serverless projects in the AWS ap-southeast-2 region. The engineering team is investigating the problem. We will post the next update in 2 hours.
- resolved · May 29, 2026, 06:36 PM UTC
This issue has been resolved.
Latest: This issue has been resolved.
-
- Elasticsearch connectivity: Azure azure-westus2Azure Infrastructure HealthKibana connectivity: Azure azure-westus2Azure Infrastructure health: azure-westus2APM connectivity: Azure azure-westus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2
Timeline · 9 updates
- investigating · May 29, 2026, 06:32 AM UTC
We are currently investigating an issue caused by a Microsoft Azure service disruption that is impacting some of our services. Users may experience intermittent errors, delays, or inability to access certain features depending on the affected Azure service and region. Our team is actively monitoring the situation and assessing the impact on our environment. At this time, the issue appears to be related to the upstream cloud provider. 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.
- resolved · May 31, 2026, 09:33 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · May 26, 2026, 09:35 PM UTC
Some users experienced missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure Southeast Asia region. We have already stabilized the situation.
Latest: Some users experienced missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure Southeast Asia region. We…
-
See the full Elastic Cloud outage history
16 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Elastic Cloud outage history →Or sign up free to get alerts when Elastic Cloud breaks · 10 free monitors · No credit card
- Started Jun 04, 2026, 01:51 AM UTC · Resolved Jun 04, 2026, 09:20 AM UTC · 7h 28m
- Started Jun 02, 2026, 01:25 PM UTC · Resolved Jun 02, 2026, 07:50 PM UTC · 6h 25m
- Started May 29, 2026, 06:00 PM UTC · Resolved May 29, 2026, 06:36 PM UTC · 35m
- Started May 29, 2026, 06:32 AM UTC · Resolved May 31, 2026, 09:33 PM UTC · 2d 15h
- Started May 26, 2026, 09:35 PM UTC · Resolved May 26, 2026, 09:35 PM UTC · —
- Started May 23, 2026, 09:42 PM UTC · Resolved May 23, 2026, 10:26 PM UTC · 44m
- Started May 22, 2026, 04:54 AM UTC · Resolved May 22, 2026, 04:54 AM UTC · —
- Started May 20, 2026, 03:29 PM UTC · Resolved May 27, 2026, 01:06 PM UTC · 6d 21h