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.

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.

Elastic

Major outage

Is Elastic down?

Yes. Elastic is reporting a major outage right now.

Checked 3 min ago, from Elastic’s published status feed

Active incidents

Elasticsearch 9.5.1: false-positive matches in certain boolean queries

Identified

Started 6 days ago

Identified6 days ago
Elasticsearch 9.5.1 contains a known issue where boolean queries containing a must, filter, or should clause using a multi-value terms query, alongside a must_not clause on fields with disabled indexing, can still return false-positive matches. While the patch in 9.5.1 (https://github.com/elastic/elasticsearch/pull/155936) resolved the bulk-scorer defect for term and range query paths; multi-value terms queries utilize a different Lucene query type that was not covered by that fix. Time Series Data Streams (TSDB) and columnar indices/data streams remain affected for this query pattern, as indexing is disabled by default on those fields. Affected terms queries may return false-positive matches (including documents that should have been excluded) and report higher document counts than expected. No error is raised, so queries will appear to complete successfully. What you can do: - If you have not yet upgraded to 9.5.*, we recommend deferring the upgrade until version 9.5.2 is available. - If you are already running 9.5.*, contact Elastic Support if you need help determining whether your searches are affected. We have identified the root cause, a fix is in progress, and we are preparing a patch release. We will provide a further update when the fix is ready.

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

Identified

Started Mar 2

IdentifiedJun 29
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.
IdentifiedJun 15
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.
IdentifiedJun 1
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.
IdentifiedApr 20
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
IdentifiedApr 2
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.
IdentifiedMar 24
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.
IdentifiedMar 24
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.
IdentifiedMar 23
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.
IdentifiedMar 2
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

GCP Mumbai (asia-south1) · Elasticsearch connectivity: GCP asia-south1Degraded

GCP Mumbai (asia-south1)Degraded

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

620 more services operational

From Sentivel’s records

Incidents in the last 90 days

14.8 h

Average time to resolve

Incidents by month (6 months)

Recent incident history

Increased error rates for microsoft-multilingual-e5-large

Resolved

Thu, 13 Aug 2026 08:32:50 GMT · resolved in 4d 3h

Serverless project creation delayed or failing

Resolved

Thu, 13 Aug 2026 03:57:56 GMT · resolved in 4h 43m

GCP asia-south1 high latency

Resolved

Thu, 06 Aug 2026 17:41:39 GMT · resolved in 1 min

Elasticsearch 9.5.0 contains a query-correctness defect

Resolved

Wed, 05 Aug 2026 22:59:15 GMT · resolved in 6d 10h

Metering issue with Elastic Cloud Hosted Deployments

Resolved

Tue, 21 Jul 2026 14:24:05 GMT · resolved in 1d 8h

AutoOps monitoring data not ingested for subset of deployments

Resolved

Tue, 21 Jul 2026 13:45:49 GMT · resolved in 35 min

AutoOps monitoring data not ingested for subset of deployments

Resolved

Tue, 21 Jul 2026 12:10:50 GMT · resolved in 1 min

Elastic Cloud - Email MFA Delivery Delays (Gmail)

Resolved

Tue, 21 Jul 2026 09:36:40 GMT · resolved in 2d 7h

Cloud Console Deployment Errors

Resolved

Wed, 15 Jul 2026 00:15:42 GMT · resolved in 57 min

Elastic Cloud authentication issues using Microsoft login credentials

Resolved

Mon, 13 Jul 2026 12:15:22 GMT · resolved in 4 min

Regional outage - Elastic Inference Service (EIS)

Resolved

Thu, 02 Jul 2026 00:54:12 GMT · resolved in 2h 6m

Partial outage - Elastic Inference Service (EIS)

Resolved

Wed, 01 Jul 2026 22:43:53 GMT · resolved in 21 min

Internal Monitoring Data Delay

Resolved

Wed, 01 Jul 2026 15:39:15 GMT · resolved in 4h 44m

Issues delivering static assets to products

Resolved

Mon, 29 Jun 2026 16:32:48 GMT · resolved in 26 min

Issues with creating/updating Deployments in several regions

Resolved

Wed, 17 Jun 2026 15:52:18 GMT · resolved in 1h 43m

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 free Elastic status page

Embed this status

https://www.sentivel.com/badge/elastic.svg

More Search providers

Algolia