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 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.
Jul 21, 2026 - 23:15 UTC
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.
Jul 21, 2026 - 14:24 UTC
Monitoring - Delivery delays have been mitigated. We will continue to monitor to ensure delivery remains stable.
Jul 21, 2026 - 23:10 UTC
Update - Update: This incident is still ongoing and we are continuing to investigate.
Jul 21, 2026 - 14:25 UTC
Update - 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 Key access to your projects and deployments remains fully operational. We are actively collaborating with our partners to resolve this issue and will provide an update as soon as we can.
Jul 21, 2026 - 10:56 UTC
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 actively collaborating with our partners to resolve this issue and will provide an update as soon as we can.
Jul 21, 2026 - 09:36 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 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
On Tuesday, July 28, between 22:00 and 23:30 UTC, we will be performing planned infrastructure maintenance on the Elastic Inference Service (EIS). EIS is the default managed inference provider for features such as semantic search, reranking, embeddings, Elastic AI Agent, and Attack Discovery. Customers using alternative inference providers will not be affected by this maintenance.
The maintenance will be applied progressively across regions. During the window, customers may experience intermittent interruptions to EIS-powered features, as the changes take effect in each region. Some inference requests may fail during this time.
If you continue to see issues after the maintenance window has ended, please open a case through our Support portal (https://support.elastic.co) or email support@elastic.co for assistance. Posted on
Jul 14, 2026 - 12:37 UTC
Resolved -
This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Jul 21, 14:21 UTC
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.
Jul 21, 13:45 UTC
Resolved -
Resolved – This incident is 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.
Jul 18, 02:45 UTC
Resolved -
This incident has been resolved
Jul 15, 01:12 UTC
Monitoring -
The ability to manage Elastic Cloud Hosted deployments via the Cloud Console has been restored
Jul 15, 00:31 UTC
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.
Jul 15, 00:15 UTC
Resolved -
This incident has been resolved.
Jul 13, 12:19 UTC
Investigating -
We are investigating a problem that prevents customers from authenticating against Elastic Cloud using their Microsoft login credentials
Jul 13, 12:15 UTC