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 |
|---|---|---|---|
| April 2026 | 0% | 10 | 10 |
| March 2026 | 3.2% | 31 | 30 |
| February 2026 | 87% | 23 | 3 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 64 Days)
Feb 6
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
Privatelink hostnames reported by API are incorrect
Started: Apr 9, 8:46 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
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)
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
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
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
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)
Started: Mar 2, 6:23 AM
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