Get email notifications whenever Elastic Cloud (Public) creates, updates or resolves an incident.
Get text message notifications whenever Elastic Cloud (Public) creates or resolves an incident.
Get webhook notifications whenever Elastic Cloud (Public) creates an incident, updates an incident, resolves an incident or changes a component status.
Update - 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.
Update - 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.
Update - 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.
Update - 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.
Update - 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.
Update - 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.
Update - 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.
Update - 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.
Update - 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.
Mar 24, 2026 - 11:09 UTC
Update - 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.
Mar 24, 2026 - 09:29 UTC
Update - 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.
Mar 23, 2026 - 16:20 UTC
Update - 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.
Mar 16, 2026 - 19:46 UTC
Update - 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.
Mar 09, 2026 - 15:01 UTC
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.
Mar 02, 2026 - 06:23 UTC
Resolved -
This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident.
Aug 20, 22:13 UTC
Identified -
We have identified the root cause of the elevated error rates affecting serverless managed OTLP. A mitigation has been applied and we are monitoring to confirm error rates return to baseline.
Based on our investigation, customer workloads were not affected.
Aug 20, 21:59 UTC
Update -
We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless.
We will provide an update within 1 hour.
Aug 20, 20:53 UTC
Investigating -
We are currently investigating elevated error rates affecting the managed OTLP on Elastic Cloud Serverless.
Our team is actively investigating the root cause.
We will provide an update within 30 minutes.
Aug 20, 20:22 UTC
Resolved -
Elasticsearch 9.5.2 has been released and contains the fix for this issue. Customers running 9.5.0 or 9.5.1 should upgrade to 9.5.2. At this time we are considering this issue resolved and will be providing no further updates.
Aug 20, 17:09 UTC
Identified -
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.
Aug 14, 09:22 UTC
Resolved -
Azure's storage component issues in the eastus region have been resolved. Consequently, Serverless project creation times have returned to normal and are functioning as expected.
Aug 20, 16:22 UTC
Monitoring -
We have determined that the issue stems from an upstream problem with Azure's storage component. Upon examination, the impact is limited strictly to new project initialization times, resulting in longer creation times for Serverless projects in the Azure eastus region.
We will provide a further update once the issue has been resolved.
Aug 20, 14:05 UTC
Investigating -
An issue affecting the creation of new Serverless projects in Azure's eastus region has been identified. Our team is actively investigating to determine the root cause.
We will provide a follow-up status update within the next hour or as soon as the root cause is established, whichever occurs first.
Aug 20, 12:48 UTC
Monitoring -
Unfortunately, we can no longer support the E5 Multilingual Large model on the Elastic Inference Service due to continued upstream provider issues. Any customers requiring this model should set up custom inference endpoints using their own API keys.
Aug 13, 18:26 UTC
Update -
We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.
Aug 13, 14:45 UTC
Investigating -
We are seeing elevated error rates from the upstream provider for the microsoft-multilingual-e5-large embedding model. Search embedding requests to this model may fail. We are investigating
Aug 13, 08:32 UTC
Resolved -
We've resolved the issue affecting Serverless project creation and modifications. All systems are now operating normally.
Aug 13, 08:40 UTC
Monitoring -
We've identified and resolved the issue affecting Serverless project creation and modifications. Our fix has been deployed, and all services are operating normally.
Current status: - Creating and modifying Serverless projects is fully operational - All systems are performing as expected
We're continuing to monitor closely for any recurrence.
Aug 13, 06:04 UTC
Update -
We're currently investigating an issue affecting Serverless project creation and modifications. You may experience delays or failures when creating new projects or updating existing project settings.
What's affected: - Creating new Serverless projects - Modifying project settings in the Cloud UI or over the API
What's not affected: - Running Serverless projects continue to operate normally - Existing project workloads are unimpacted
We'll provide an update within 2 hours, or sooner if the situation changes.
Aug 13, 05:28 UTC
Investigating -
We are investigating failures with Serverless project creation.
Aug 13, 03:57 UTC