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.
June 2026
Missing Metrics in Cloud Console - Azure North Europe
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are seeing some signs of recovery, and have taken action to mitigate the impact and speed up recovery.
Some users will still see seeing missing metrics visualizations in the Cloud console, for deployments in the Azure North Europe region.
We are actively investigating and will provide another update within 1 hour
investigating
Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 1 hour
May 2026
Issue creating new projects in AWS ap-southeast-2
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We're aware of an issue with creating Serverless projects in the AWS ap-southeast-2 region. The engineering team is investigating the problem. We will post the next update in 2 hours.
Upstream Azure Outage Causing Service Degradation
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We continue to monitor the situation which has mostly recovered. A small number of deployments are still not healthy.
Our support team is working on resolving these on a case-by-case basis.
monitoring
Remediation is underway and systems are recovering. We continue to monitor the situation and will post an update in the next 2 hours or earlier.
identified
We continue to remediate the impact of an upstream Azure outage in Azure West US 2 (azure-westus2), limited to availability zone westus2-2.
Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations.
Deployments configured for high availability across multiple availability zones are not expected to be affected.
Our teams remain actively enga...
identified
We continue to respond to an upstream Microsoft Azure outage in Azure West US 2 (azure-westus2), caused by a datacenter power event reported by Azure. Elastic impact remains limited to availability zone westus2-2.
Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations (including create, edit, restart, and delete).
Deployments configured ...
identified
We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region.
We have confirmed that impact to our service is limited to a single availability zone (westus2-2). Customers whose deployments are not configured for high availability may experience intermittent errors, delays, or inability to access certain features.
Deployments configured for high avail...
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region.
We have confirmed that impact to our service is limited to a single availability zone (westus2-2). Customers whose deployments are not configured for high availability may experience intermittent errors, delays, or inability to access certain features.
Deployments configured for high avail...
Missing Metrics in Cloud Console - Azure North Europe
majorSource not attested
Last archived state: resolved
View archived record details
identified
The problem has been identified and is being stabilized, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.
investigating
Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 1 hour.
AutoOps Login Issues for New Customers
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We continue to actively monitor the implemented mitigation actions. All new user logins are functioning as expected. A permanent resolution is scheduled to be implemented early next week. Our next update will be once the resolution actions are complete, or sooner if the situation changes.
monitoring
We have mitigated the issue preventing new Elastic Cloud customers and trial users from accessing AutoOps by restarting a backend service. We are actively monitoring to confirm the fix remains stable and that all new user logins are functioning as expected. We will provide a final update once we have confirmed full resolution.
investigating
We are investigating an issue that prevents new Elastic Cloud customers, including trial users, from accessing AutoOps across all regions.
Impact: New customers and trial accounts are currently unable to access the AutoOps dashboard.
Existing Customers: Service is unaffected. AutoOps continues to function normally for all existing deployments.
Our team is actively working to identify the root cause. We will provide our next update within the next hour or as soon as more information becomes...
Temporarily unavailability of Serverless Projects Functionality
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are aware of issues resulting in temporary unavailability across multiple Serverless projects. From 08:00 UTC to 09:40 UTC on May 11, Search, Ingest and EIS functionality may have been unavailable.
The root cause of this issue has been identified and resolved - we are currently monitoring, and expect no further impact.
Issues with Email Alerts
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A solution has been implemented, and email delivery has resumed. We are continuing to track the situation closely and will provide another update once considered resolved.
investigating
We are currently investigating reports that some customers may be facing issues with email alerts.
April 2026
Delayed AutoOps Metrics in AWS us-east-1
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
This issue has now been resolved and we are continuing to monitor the system.
identified
We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.
Missing Metrics in Cloud Console — US East (us-east-1)
majorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to see signs of stabilization and monitoring as the system recovers, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.
investigating
Our investigation is ongoing. We continue to see early signs of stabilization, but metrics visualizations in the Cloud console remain impacted. We will provide a further update in 1 hour, or when there is a change in status.
investigating
Our investigation is ongoing. Some early signs of stabilisation have been observed, but metrics visualizations in the Cloud console remain impacted. We will provide a further update within 30 minutes.
investigating
Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the us-east-1 (US East) region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 30 minutes.
Elevated Error Rates and Latency — EU West Region
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our monitoring system reports that AWS EU West 3 (Paris) region ingress layer traffic has recovered to normal levels as of 11:36 UTC and our SLO alerts have resolved. We are continuing to monitor and will update once we are confident the issue is fully resolved.
identified
We are continuing to work on a fix for this issue.
identified
We are currently investigating connectivity issues affecting a subset of customers in our AWS EU West 3 (Paris) region. Some requests may be experiencing elevated latency or failures. Our team is actively investigating, and we are working with our cloud infrastructure provider on the underlying issue. Other regions are not affected at this time. We will provide updates as the situation develops.
