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 - 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.
May 22, 2026 - 16:19 UTC
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.
May 20, 2026 - 15:48 UTC
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 available.
May 20, 2026 - 15:29 UTC
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 -
Synthetics browser monitors running in Europe-Germany region (GCP europe-west3) for some of the users were experiencing delayed executions results and some of them being stopped. The issue affected both Elastic Cloud Hosted and Elastic Cloud Serverless in that region and other regions were not impacted.
May 22, 04:54 UTC
May 21, 2026
No incidents reported.
May 20, 2026
May 19, 2026
No incidents reported.
May 18, 2026
Unresolved incident: Connectivity disruption for AWS Bahrain (me-south-1).
Resolved -
We have confirmed no further impact from this incident, and are now considering this issue resolved. Thank you for your patience.
May 11, 11:11 UTC
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.
May 11, 08:00 UTC
Resolved -
This issue is now resolved. Email delivery has been successful with no monitored issues.
May 9, 01:01 UTC
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.
May 8, 23:11 UTC
Investigating -
We are currently investigating reports that some customers may be facing issues with email alerts.
May 8, 18:10 UTC