Elastic Cloud outage, 2 March 2026

Connectivity disruption for AWS Bahrain (me-south-1)

Started
Status
Ongoing: Identified
Impact
Major
Affected
AWS EC2 Health: me-south-1, Snapshot Storage Infrastructure (S3): me-south-1, Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1, APM connectivity: AWS me-south-1, AWS Infrastructure health: me-south-1, Elasticsearch connectivity: AWS me-south-1, Kibana connectivity: AWS me-south-1

Last update from Elastic Cloud

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 support@elastic.co.

21 Sept 2026, 15:21 UTC

Read the full incident on the official Elastic Cloud status page

Is Elastic Cloud down now?

This page is the record of one past incident. For the live status, see Is Elastic Cloud down right now? - it reads the official status page every 2 minutes.

Other Elastic Cloud incidents

  1. Delayed or Unavailable project operation in GCP us-central1

  2. Delayed Serverless Metrics in Azure UAE North region

  3. Degraded Performance: Cloud Provisioning Delays

  4. AutoOps node metrics temporarily unavailable in some regions

  5. Elastic Support Portal unavailable

  6. Delayed Metrics in Cloud Console - GCP us-east4

  7. Kibana access restored for UI-assigned Organization Owners on Hosted deployments

  8. Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output

All recorded Elastic Cloud incidents