SentivelAll providers

Search

Elastic

Major outage

Is Elastic down?

Yes. Elastic is reporting a major outage right now.

Checked , from Elastic’s published status feed

Active incidents

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

Identified

Started

  1. Identified

    Update — This incident is still 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 mailto:mailto:support@elastic.co.

  2. Identified

    Update — This incident is still 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 mailto:support@elastic.co.

  3. Identified

    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.

  4. Identified

    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:support@elastic.co. Apr 20, 2026 — 00:00 UTC

  5. Identified

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

  6. Identified

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

  7. Identified

    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.

  8. Identified

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

  9. Identified

    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.

Elastic services

AWS Bahrain (me-south-1) · APM connectivity: AWS me-south-1Major outage
Azure Washington (azure-westus2) · APM connectivity: Azure azure-westus2Degraded
AWS Bahrain (me-south-1)Major outage
AWS Bahrain (me-south-1) · AWS EC2 Health: me-south-1Major outage
AWS Bahrain (me-south-1) · AWS Infrastructure health: me-south-1Major outage
Azure - Washington (azure-westus2)Degraded
Azure - Washington (azure-westus2) · Azure Infrastructure HealthDegraded
Azure Washington (azure-westus2) · Azure Infrastructure health: azure-westus2Degraded
Azure Washington (azure-westus2)Degraded
AWS Bahrain (me-south-1) · Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1Major outage
AWS Bahrain (me-south-1) · Elasticsearch connectivity: AWS me-south-1Major outage
Azure Washington (azure-westus2) · Elasticsearch connectivity: Azure azure-westus2Degraded
AWS Bahrain (me-south-1) · Kibana connectivity: AWS me-south-1Major outage
Azure Washington (azure-westus2) · Kibana connectivity: Azure azure-westus2Degraded
AWS Bahrain (me-south-1) · Snapshot Storage Infrastructure (S3): me-south-1Major outage
AWS Cape Town (af-south-1) · APM connectivity: AWS af-south-1Operational
AWS Hong Kong (ap-east-1) · APM connectivity: AWS ap-east-1Operational
AWS Tokyo (ap-northeast-1) · APM connectivity: AWS ap-northeast-1Operational
AWS Seoul (ap-northeast-2) · APM connectivity: AWS ap-northeast-2Operational
AWS Mumbai (ap-south-1) · APM connectivity: AWS ap-south-1Operational
AWS Singapore (ap-southeast-1) · APM connectivity: AWS ap-southeast-1Operational
AWS Sydney (ap-southeast-2) · APM connectivity: AWS ap-southeast-2Operational
AWS Central (ca-central-1) · APM connectivity: AWS ca-central-1Operational
AWS Frankfurt (eu-central-1) · APM connectivity: AWS eu-central-1Operational
AWS Zurich (eu-central-2) · APM connectivity: AWS eu-central-2Operational
AWS Stockholm (eu-north-1) · APM connectivity: AWS eu-north-1Operational
AWS Milan (eu-south-1) · APM connectivity: AWS eu-south-1Operational
AWS Ireland (eu-west-1) · APM connectivity: AWS eu-west-1Operational
AWS London (eu-west-2) · APM connectivity: AWS eu-west-2Operational
AWS Paris (eu-west-3) · APM connectivity: AWS eu-west-3Operational
AWS São Paulo (sa-east-1) · APM connectivity: AWS sa-east-1Operational
AWS N. Virginia (us-east-1) · APM connectivity: AWS us-east-1Operational
AWS Ohio (us-east-2) · APM connectivity: AWS us-east-2Operational
AWS N. California (us-west-1) · APM connectivity: AWS us-west-1Operational
AWS Oregon (us-west-2) · APM connectivity: AWS us-west-2Operational
Azure New South Wales (azure-australiaeast) · APM connectivity: Azure azure-australiaeastOperational
Azure São Paulo (azure-brazilsouth) · APM connectivity: Azure azure-brazilsouthOperational
Azure Toronto (azure-canadacentral) · APM connectivity: Azure azure-canadacentralOperational
Azure Pune (azure-centralindia) · APM connectivity: Azure azure-centralindiaOperational

590 more services operational

Recent incident history

Regional outage - Elastic Inference Service (EIS)

Resolved

· resolved in 2h 6m

Partial outage - Elastic Inference Service (EIS)

Resolved

· resolved in 21 min

Internal Monitoring Data Delay

Resolved

· resolved in 4h 44m

Issues delivering static assets to products

Resolved

· resolved in 26 min

Issues with creating/updating Deployments in several regions

Resolved

· resolved in 1h 43m

Ingestion issues for Managed OTLP and Managed Intake Service endpoints in the Azure Australia East region

Resolved

· resolved in 2h 5m

Issue with Kibana authentication flow

Resolved

· resolved in 39 min

Intermittent Elastic Cloud Serverless Availability Issues in AWS us-east-1

Resolved

· resolved in 1h 42m

Customers may see delays with creating Azure serverless projects

Resolved

· resolved in 7h 29m

Missing Metrics in Cloud Console - Azure North Europe

Resolved

· resolved in 6h 25m

Issue creating new projects in AWS ap-southeast-2

Resolved

· resolved in 36 min

Upstream Azure Outage Causing Service Degradation

Resolved

· resolved in 2d 15h

Missing Metrics in Cloud Console - Azure Southeast Asia

Resolved

· resolved in 1 min

Missing Metrics in Cloud Console - Azure North Europe

Resolved

· resolved in 44 min

Delayed Execution For Synthetic Monitors in Europe Germany

Resolved

· resolved in 1 min

About this page

Is Elastic down right now?
Yes. Elastic is reporting a major outage right now. This page is updated continuously from Elastic's own status feed.
Where does this Elastic status come from?
It is read directly from Elastic's own published status page. Sentivel is an independent monitoring tool and is not affiliated with or endorsed by Elastic. View Elastic’s official status page.
How do I get alerted when Elastic has an incident?
Map Elastic as a dependency in Sentivel. When it has an incident we alert your team and post a clear advisory on your own status page.

Get told the moment Elastic has an incident

Map which of your services depend on Elastic. When it has an incident, Sentivel alerts your team and posts a clear advisory on your own status page, so your customers hear it from you.

Start freeElastic status page

More Search providers

Algolia