New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages, May 2026
Services Pricing Dashboard

Elastic Cloud Outage History

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

Checking current status...
0% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Apr 11Jul 9

Monthly Uptime

Month Uptime Days Tracked Days with Issues
July 2026 0% 9 9
June 2026 0% 30 30
May 2026 0% 31 31
April 2026 0% 21 21

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)

Apr 10 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

July 2026
Regional outage - Elastic Inference Service (EIS)
minor

Started: Jul 2, 12:54 AM

monitoring
The issue affecting a subset of customers with EIS in EMEA regions has been mitigated and the service have been restored.
Jul 2, 2:24 AM
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.
Jul 2, 12:54 AM
Partial outage - Elastic Inference Service (EIS)
major

Started: Jul 1, 10:43 PM

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.
Jul 1, 10:45 PM
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.
Jul 1, 10:44 PM
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.
Jul 1, 10:43 PM
Internal Monitoring Data Delay
minor

Started: Jul 1, 3:39 PM

monitoring
The system has recovered and we are continuing to monitor the situation.
Jul 1, 7:50 PM
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.
Jul 1, 4:50 PM
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...
Jul 1, 3:39 PM
June 2026
Issues delivering static assets to products
minor

Started: Jun 29, 4:32 PM

identified
We are continuing to work on a fix for this issue.
Jun 29, 4:33 PM
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.
Jun 29, 4:32 PM
Issues with creating/updating Deployments in several regions
major

Started: Jun 17, 3:52 PM

monitoring
We have identified and deployed a fix for this issue and are continuing to closely monitor the situation.
Jun 17, 4:53 PM
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.
Jun 17, 3:52 PM
Ingestion issues for Managed OTLP and Managed Intake Service endpoints in the Azure Australia East region
major

Started: Jun 16, 10:54 PM

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.
Jun 17, 12:02 AM
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.
Jun 16, 10:54 PM
Failure to authenticate to Kibana with SSO
major

Started: Jun 16, 10:57 AM

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.
Jun 16, 10:57 AM
Issue with Kibana authentication flow
major

Started: Jun 16, 10:57 AM

investigating
We are continuing to investigate this issue.
Jun 16, 11:21 AM
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.
Jun 16, 10:57 AM
Intermittent Elastic Cloud Serverless Availability Issues in AWS us-east-1
major

Started: Jun 15, 5:31 PM

monitoring
This issue has been mitigated, and we are continuing to monitor the situation.
Jun 15, 6:00 PM
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.
Jun 15, 5:31 PM
Customers may see delays with creating Azure serverless projects
major

Started: Jun 4, 1:51 AM

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.
Jun 4, 6:21 AM
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.
Jun 4, 3:44 AM
investigating
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are currently investigating the issue.
Jun 4, 1:51 AM
Missing Metrics in Cloud Console - Azure North Europe
minor

Started: Jun 2, 1:25 PM

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
Jun 2, 3:02 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
Jun 2, 1:25 PM
May 2026
Issue creating new projects in AWS ap-southeast-2
major

Started: May 29, 6:00 PM

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.
May 29, 6:00 PM
Upstream Azure Outage Causing Service Degradation
major

Started: May 29, 6:32 AM

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.
May 30, 6:36 AM
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.
May 29, 6:50 PM
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...
May 29, 2:26 PM
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 ...
May 29, 11:46 AM
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...
May 29, 10:43 AM
investigating
We are continuing to investigate this issue.
May 29, 6:50 AM
investigating
We are continuing to investigate this issue.
May 29, 6:35 AM
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...
May 29, 6:32 AM
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 — 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.
Jun 29, 5:14 PM
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.
Jun 15, 7:27 PM
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.
Jun 1, 5:13 PM
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
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 16, 7:46 PM
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 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