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.
July 2026
Regional outage - Elastic Inference Service (EIS)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue affecting a subset of customers with EIS in EMEA regions has been mitigated and the service have been restored.
investigating
We have identified continued impact for a subset of affected customers using EIS. Our team is investigating an issue with the previous remediation and is working to ensure all affected environments are fully restored.
Partial outage - Elastic Inference Service (EIS)
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
investigating
We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
investigating
We are currently investigating a partial outage affecting the Elastic Integration Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
Internal Monitoring Data Delay
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The system has recovered and we are continuing to monitor the situation.
identified
We have identified the issue and implemented a fix. We are seeing signs of system recovery and are continuing to monitor the situation closely.
investigating
We're experiencing a monitoring data delay affecting a limited number of Azure regions. Elastic Cloud's internal metrics for these regions are being ingested more slowly than usual.
What you may notice: Deployment metrics and instance utilization data may not appear in the Elastic Cloud UI for Hosted Deployments and Serverless Projects in affected regions.
What's not affected: Your deployments and projects are running normally. Data ingestion and all functionality remain unimpacted besides la...
June 2026
Issues delivering static assets to products
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
We have identified an issue with our ability to deliver certain static assets to our products. We have identified and are working to implement a fix.
Issues with creating/updating Deployments in several regions
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified and deployed a fix for this issue and are continuing to closely monitor the situation.
identified
We are currently investigating an issue when creating/updating Deployments in several regions.
We've identified the issue and working on applying a fix.
We will provide an update when one is available or within the hour, whichever comes first.
Ingestion issues for Managed OTLP and Managed Intake Service endpoints in the Azure Australia East region
majorSource not attested
Last archived state: resolved
View archived record details
identified
This incident is ongoing. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.
identified
We are currently experiencing an issue impacting the ability to ingest data into mOTLP and .amp endpoints in the Azure Australia East region. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.
Failure to authenticate to Kibana with SSO
majorSource not attested
Last archived state: resolved
View archived record details
identified
We have detected an issue with the Kibana authentication flow. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure. A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution. We will post an update in 30 minutes, or sooner if there is a change in status.
Issue with Kibana authentication flow
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
We have detected an issue with the Kibana authentication flow for both Deployments and Projects. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure.
A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution.
Our team is currently identifying the root cause to resolve the issue.
We will share another update in the next hour.
Intermittent Elastic Cloud Serverless Availability Issues in AWS us-east-1
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
This issue has been mitigated, and we are continuing to monitor the situation.
investigating
We are currently investigating an intermittent issue which may cause unavailability of Elastic Cloud Serverless projects or the inability to create new Serverless projects in AWS us-east-1. We will continue to update status as we learn more.
Customers may see delays with creating Azure serverless projects
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable.
We are seeing increased recovery across as we monitor the situation. Services are being restored.
Monitoring is continuing, and we will provide further updates as we progress.
monitoring
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable.
Recovery has started and we will provide further updates as we progress.
investigating
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable.
We are currently investigating the issue.
