Elastic Cloud Outage History

Uptime record, past incidents, and downtime history for Elastic Cloud.

Checking current status...

90-Day Trend

Monthly Uptime

Month	Uptime	Days Tracked	Days with Issues
May 2026	0%	25	25
April 2026	0%	30	30
March 2026	3.2%	31	30
February 2026	60%	5	2

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Feb 24 Today

Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

May 2026

Missing Metrics in Cloud Console - Azure North Europe

major

Started: May 23, 9:42 PM

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.

May 23, 10:11 PM

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 23, 9:42 PM

AutoOps Login Issues for New Customers

major

Started: May 20, 3:29 PM

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.

May 22, 4:19 PM

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, 3:48 PM

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...

May 20, 3:29 PM

Temporarily unavailability of Serverless Projects Functionality

major

Started: May 11, 8:00 AM

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, 10:07 AM

Issues with Email Alerts

major

Started: May 8, 6:10 PM

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, 11:11 PM

investigating

We are currently investigating reports that some customers may be facing issues with email alerts.

May 8, 6:10 PM

April 2026

Delayed AutoOps Metrics in AWS us-east-1

major

Started: Apr 30, 9:46 PM

monitoring

This issue has now been resolved and we are continuing to monitor the system.

Apr 30, 10:18 PM

identified

We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.

Apr 30, 9:46 PM

Missing Metrics in Cloud Console — US East (us-east-1)

major

Started: Apr 28, 2:46 PM

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.

Apr 28, 5:39 PM

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.

Apr 28, 4:32 PM

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.

Apr 28, 3:57 PM

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.

Apr 28, 2:46 PM

Elevated Error Rates and Latency — EU West Region

major

Started: Apr 27, 11:49 AM

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.

Apr 27, 12:08 PM

identified

We are continuing to work on a fix for this issue.

Apr 27, 11:57 AM

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.

Apr 27, 11:49 AM

EIS elevated 5xx error rates for model google-gemini-embedding-001

major

Started: Apr 20, 6:37 AM

investigating

Errors are coming from the provider API (Google). The incident has been escalated to them, and we are still waiting for a response.

Apr 20, 9:50 AM

investigating

We're seeing elevated 5xx error rates for the Gemini Embedding v1 model in EIS. The following default inference endpoint is affected: - .google-gemini-embedding-001 We're investigating and will update again in 2 hours or if there's a change in status.

Apr 20, 6:37 AM

Privatelink hostnames reported by API are incorrect

major

Started: Apr 9, 8:46 PM

identified

We are still working on moving the fix to production as we experienced some testing issues.

Apr 10, 12:18 PM

identified

We have merged a fix and are working on deploying it to production

Apr 9, 10:44 PM

identified

A recent change to our Privatelink implementation resulted in the URLs reported by the deployment API being incorrect in some cases, causing connectivity issues for customers who relied on those URLs. We have identified the issue and are working on a fix.

Apr 9, 8:46 PM

Connection issue to Kibana via the Cloud UI SSO

major

Started: Apr 9, 3:37 PM

investigating

We have rolled out the fix and there should be no more customer impact

Apr 9, 7:50 PM

investigating

We have identified the issue and are working on a fix. We will update again in 3 hours or earlier.

Apr 9, 4:41 PM

investigating

We have identified that only PrivateLink customers are impacted and no other Hosted Cloud Deployments should see any issues.

Apr 9, 4:21 PM

investigating

We are aware of an issue when connecting to Kibana through the Elastic Cloud UI via SAML SSO, impacting hosted Cloud deployments. Our team is actively investigating. We will post an update to this status within the next hour.

Apr 9, 3:37 PM

Synthetics service may not run on schedule (us-east-4)

major

Started: Apr 6, 5:58 PM

identified

We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours.

Apr 6, 7:16 PM

investigating

We are investigating an issue in our Synthetics service on us-east-4. Some customer monitor jobs may not run on their expected schedule. We will provide an update in an hour or earlier.

Apr 6, 5:58 PM

March 2026

Elevated error rates for Claude Sonnet 4.5 EIS inference endpoints

major

Started: Mar 30, 6:46 PM

investigating

We're seeing elevated 5xx error rates for the Claude Sonnet 4.5 model in EIS. The following default inference endpoints are affected: - .anthropic-claude-4.5-sonnet-chat_completion - .anthropic-claude-4.5-sonnet-completion - .gp-llm-v2-chat_completion - .gp-llm-v2-completion We're investigating and will update again in 2 hours or if there's a change in status.

Mar 30, 6:46 PM

AutoOps deployments marked as Inactive in AWS us-east-1 region

major

Started: Mar 27, 4:33 AM

monitoring

We have mitigated the issue, and AutoOps is back to full functionality in the AWS us-east-1 region. We will continue monitoring the signals from the region to ensure AutoOps remains fully functional, and will share another update once the issue is fully resolved.

Mar 27, 7:13 AM

monitoring

We have identified the issue and applied mitigations to bring AutoOps in the AWS us-east-1 region back to functionality. Customer deployments may still be marked as inactive, and recent metrics may still not be available. We expect AutoOps to return to full functionality within the next hour. We will provide an update when one is available or within the hour, whichever comes first.

Mar 27, 5:37 AM

investigating

We are currently investigating an outage of AutoOps in AWS us-east-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

Mar 27, 4:33 AM

Issue creating new projects in GCP europe-west3

major

Started: Mar 26, 10:51 AM

identified

The engineering team is validating the fix to restore project creation in the GCP europe-west3 region. We will post another update in 2 hours or sooner if needed

Mar 26, 1:06 PM

identified

We are aware of problems creating new Serverless projects in the GCP europe-west3 region. The engineering team has identified the problem and we are working on mitigating it. We will post the next updated in 2 hours.

Mar 26, 10:51 AM

Connectivity disruption for AWS Bahrain (me-south-1)

major

Started: Mar 2, 6:23 AM

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.

May 18, 4:33 PM

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...

Apr 20, 5:46 PM

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 (http...

Apr 2, 12:00 AM

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...

Mar 24, 11:09 AM

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.

Mar 24, 9:29 AM

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 (http...

Mar 23, 4:20 PM

identified

Mar 16, 7:46 PM

identified

Mar 9, 3:01 PM

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 2, 6:23 AM

View live status for Elastic Cloud Browse all services