Looking for an update now? Check the current status, or follow Elastic Cloud for future changes.
0%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Elasticsearch 9.5.3 has been released and all customers currently running 9.5.0, 9.5.1 or 9.5.2 are advised to update to this new version as soon as possible.
Impacted customers are advised to follow the workaround steps from https://github.com/elastic/elasticsearch/issues/158212 after the upgrade.
monitoring
Elasticsearch 9.5.3 has been released and all customers currently running 9.5.0, 9.5.1 or 9.5.2 are advised to update to this new version as soon as possible.
identified
The fix has been identified and backported to the Elasticsearch 9.5 patch branch. The teams are performing the needed validations before scheduling and rolling out the 9.5.3 release.
identified
We have identified the root cause and the team is working on a fix scheduled to be released in Elasticsearch version 9.5.3
What you can do:
- If you have not yet upgraded to 9.5.*, you are not affected as upgrades to 9.5 have been disabled until 9.5.3 is released
- If you are already running 9.5 and experience the symptoms of this issue, please contact Elastic Support.
More information can be found on https://www.elastic.co/docs/release-notes/elasticsearch/known-issues#elasticsearch-9.5.2-known-issues
investigating
We are aware of a bug affecting customers on Elasticsearch versions 9.5.0, 9.5.1 and 9.5.2 where bulk index operations processed on the primary shard can result in divergence on the replicas resulting in high disk usage and long-running recoveries. The team is working on a fix. More information can be found on https://www.elastic.co/docs/release-notes/elasticsearch/known-issues#elasticsearch-9.5.2-known-issues
The next update will be in the next 2 hours or sooner if needed.
August 2026
[RESOLVED - 2026-08-26] APM endpoints for serverless projects not available
On August 26, at around 00:00 UTC we deployed a change in Managed Inputs that affected some rules in our internal DNS provider, removing the .apm endpoints some of our Serverless customers. The service was restored around 9AM UTC on the same day. During this time, some customers would have experienced unavailability of the .apm endpoint, for a period in the 9 hour window. We are putting some checks and alerts in place to ensure this does not happen again.
March 2026
Connectivity disruption for AWS Bahrain (me-south-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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
Legacy Incident Archive
37 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Elevated Error Rates Affecting Managed OTLP
majorSource not attested
Last archived state: resolved
View archived record details
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.
investigating
We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless.
We will provide an update within 1 hour.
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.
Issue when creating Serverless projects in Azure eastus region
majorSource not attested
Last archived state: resolved
View archived record details
Elastic Cloud Serverless
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.
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.
Elasticsearch 9.5.1: false-positive matches in certain boolean queries
majorSource not attested
Last archived state: resolved
View archived record details
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 Ser...
Increased error rates for microsoft-multilingual-e5-large
majorSource not attested
Last archived state: resolved
View archived record details
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.
investigating
We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.
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
Serverless project creation delayed or failing
majorSource not attested
Last archived state: resolved
View archived record details
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.
investigating
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 ...
investigating
We are investigating failures with Serverless project creation.
Elasticsearch 9.5.0 contains a query-correctness defect
majorSource not attested
Last archived state: resolved
View archived record details
identified
A patch release containing the fix is in progress and it is expected to be available within the next week. Our recommendation to defer upgrading to 9.5.0 until 9.5.1 is available remains unchanged.
identified
Further investigation confirmed the impact of this issue was limited to boolean queries containing a must, filter, or should clause, along with a must_not clause on unindexed fields. Such queries can return false-positives returning documents that should have been excluded and report higher document counts than expected.
We have identified the root cause, a fix is in progress, and we are preparing a patch release. We will provide a further update by 10:00 UTC August 6.
identified
Elasticsearch 9.5.0 contains a defect that can cause searches to return incorrect results for any index or data stream that disables indexing on a queried field . A query that excludes values using a must_not clause may fail to exclude them when the targeted field has doc values enabled but is not indexed for search. Affected searches can return documents that should have been excluded and report higher document counts than expected, and results may vary between runs of the same query.
No er...
July 2026
Metering issue with Elastic Cloud Hosted Deployments
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are still investigating the metering issue impacting a small number of customers.
We'll provide a further update when new information is available.
investigating
We are still investigating the metering issue impacting a small number of customers. We will proactively issue billing corrections where necessary.
We'll provide another update when new information is available.
investigating
We have identified an issue with our metering of Instance Capacity for Hosted Deployments that affects a subset of customers.
We currently believe the impact to be limited to a small number of customers but are still working to identify and correct all occurrences of this issue. We will proactively issue billing corrections where necessary.
AutoOps monitoring data not ingested for subset of deployments
majorSource not attested
Last archived state: resolved
View archived record details
identified
RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe.
Note this incident has already been resolved, and is being posted retroactively.
Elastic Cloud - Email MFA Delivery Delays (Gmail)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Delivery delays have been mitigated. We will continue to monitor to ensure delivery remains stable.
investigating
Update: This incident is still ongoing and we are continuing to investigate.
investigating
Update: This incident is still ongoing and we are continuing to investigate.
We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code.
Available Workarounds:
- Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn).
- Authenticate using the "Log in with Google" social login button.
Note: API K...
investigating
We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code.
Available Workarounds:
- Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn).
- Authenticate using the "Log in with Google" social login button.
Note: API Key access to your projects and deployments remains fully operational.
We are a...
Cloud Console Deployment Errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The ability to manage Elastic Cloud Hosted deployments via the Cloud Console has been restored
investigating
We are investigating errors with our cloud console affecting access to create, update, delete and view Elastic Cloud Hosted deployments. Our team is actively investigating the cause so that they can mitigate and restore the service.
