Looking for an update now? Check the current status, or follow Elastic Cloud for future changes.
0%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. We are seeing slight signs of recovery, both from our cloud provider and from our own mitigation work.
Elastic Cloud Hosted: Some of the affected deployments are recovering. Customers whose plan changes or other operations failed during the incident are advised to retry them from the Elastic Cloud console. Operations that depend on the affected zone may take longer than usual, or fail again, until recovery progresses further. Some deployments may remain unavailable or degraded.
Elastic Serverless: Some projects may remain unavailable or degraded.
identified
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. Elastic Cloud Hosted deployments and Elastic Serverless projects with resources in the affected zone may remain unavailable or degraded.
Our teams are continuing to work on mitigation and recovery, and we are working closely with our cloud provider. We do not yet have an estimated time for full recovery.
We will provide the next update by 12:00 UTC, or sooner if there is a significant change.
identified
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing.
Elastic Cloud Hosted: Most deployments with resources in the affected zone remain unavailable or degraded. We are seeing early, limited signs of recovery, and a small number of the initially affected deployments are recovering. We are continuing our mitigation work and will share more as recovery progresses.
Elastic Serverless: We have taken steps to avoid placing new projects in the affected zone, and we are now rebalancing existing projects to other availability zones. We are seeing signs of recovery - some projects remain unavailable or degraded in the meantime.
Reduced capacity in the region may delay scaling and the creation of new resources. We do not yet have an estimated time for full recovery from our cloud provider. We are working closely with them and will provide the next update by 10:15am UTC.
identified
Our cloud provider has confirmed an infrastructure incident affecting a single availability zone (europe-west2-b) in the GCP europe-west2 (London) region, causing network connectivity loss and resource unavailability in that zone. Elastic Cloud Hosted deployments and Elastic Serverless projects with resources in the affected zone may be unavailable or experience degraded performance.
We have taken steps to avoid placing new Serverless projects in the affected zone, and we are working to restore services that depend on it. Reduced capacity in the region may delay scaling and the creation of new resources.
We do not yet have an estimated time for recovery from our cloud provider. We are working closely with them and will provide the next update within an hour.
investigating
We are investigating an issue affecting one availability zone in the GCP europe-west2 (London) region. Starting at approximately 06:15 UTC, some Elastic Cloud Hosted and Serverless deployments with capacity in this zone may experience degraded availability or connectivity. Monitoring and logging for deployments in the region may also be delayed.
Deployments in other zones and regions are not affected. Our engineers are actively working on the issue, and we are in contact with our cloud provider.
Delayed or Unavailable project operation in GCP us-central1
We have observed improvements after mitigations were applied by our upstream cloud storage provider. Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations while recovery continues. We are monitoring the situation and will provide another update when more information is available.
identified
Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations. The provider is continuing to investigate the issue. We are monitoring the situation and will provide another update when more information is available.
identified
We have identified an issue with cloud storage affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operations. The provider is investigating the issue, and we are monitoring recovery. We will provide another update when more information is available.
investigating
We are investigating an issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operation.
Delayed Serverless Metrics in Azure UAE North region
Customers with Serverless projects in the Azure UAE North region may see delays in metrics displayed in Cloud UI. The team is investigating the issue and we will post an update in 2 hours or sooner if necessary
We are currently experiencing delays in provisioning new cloud resources due to slowness with an external container image provider. This may result in delays when creating new deployments, scaling existing ones, or relocating instances affected by infrastructure maintenance. As mitigation, you can try re-running failed plan changes.
Existing running deployments are not impacted. Our team is actively monitoring the situation and working to mitigate the issue.
We will provide an update in the next 12 hours.
AutoOps node metrics temporarily unavailable in some regions
We've identified the cause of the missing node-level metrics (CPU, memory, disk, thread pools) in affected regions. Cluster health, shard, and deployment data were never affected, and no data loss has occurred.
A fix has been validated in one region and is now being rolled out to the remaining affected regions. We'll provide a further update once the rollout is complete.
investigating
We are investigating reports of missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions. This may appear as a "No data" message on the Nodes view. Cluster health, shard, and deployment data are unaffected, and no data loss has occurred.
We will provide an update within the next 2 hours or earlier.
We are seeing signs of recovery on the Elastic Support Portal, and customers should now be able to access as normal. We will continue monitoring for 30 minutes before marking this incident as resolved.
investigating
We are currently aware that some customers may be unable to access the Elastic Support Portal at this time. We are working with our provider to investigate.
If you need to contact support in the meantime, please contact support@elastic.co.
Update: The fix has been deployed to production and we have applied a data correction to affected accounts, restoring Kibana access for impacted users. We are monitoring to confirm full resolution.
identified
Update: This incident is still ongoing and we are continuing to investigate.
identified
We have identified and are in the process of fixing+mitigating a bug in our permissions management UI that is prevents users with the Organisation Owner role and Cloud Console, Elasticsearch, and Kibana access from accessing Kibana in Hosted Deployments.
Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output
We have patched Fleet Server versions 9.5.3 and 9.4.6 with corrected releases deployed as of September 10, 2026 at 21:20 UTC.
- Upgrading to the current 9.4.6 or 9.5.3 releases will not be affected by this bug as the updated release contains the fix.
- If you upgraded to 9.4.6 or 9.5.3 before 21:20 UTC on 10 September 2026, perform the following mitigation:
1. Force restart the Integration Server component of you affected deployment
2. Run cleanup procedures on affected Elastic Agents (see https://support.elastic.co/knowledge/bee1c75c) — required if agents failed to check in or remained offline after the Integration Server restart
IMPORTANT: The patched Fleet Server is not available outside Elastic Cloud Enterprise (ECE) Stack Packs and Elastic Cloud Hosted (ECH).
identified
We have patched Fleet Server versions 9.5.3 and 9.4.6 with corrected releases deployed as of September 10, 2026 at 21:20 UTC.
- Upgrading to the current 9.4.6 or 9.5.3 releases will not be affected by this bug as the updated release contains the fix.
- If you upgraded to 9.4.6 or 9.5.3 before 21:20 UTC on 10 September 2026, perform the following mitigation:
1. Force restart the Integration Server component of you affected deployment
2. Run cleanup procedures on affected Elastic Agents (see https://support.elastic.co/knowledge/bee1c75c) — required if agents failed to check in or remained offline after the Integration Server restart
identified
We've identified a bug in Fleet Server 9.5.3 (also present in 9.4.6) that can cause Elastic Agents to crash-loop and go offline when Fleet pushes a configuration update, including enrollment, a policy change, or a routine revision bump. This only affects policies that use Fleet's remote Elasticsearch output feature.
Recommendation: If you use Fleet's remote Elasticsearch output, do not upgrade to 9.5.3 or 9.4.6 until a fixed version is available. If you're already on an affected version and experiencing agent check-in failures, contact Support for remediation steps.
A fix has been merged and will ship in the next 9.5.x and 9.4.x releases. Known Issue documentation: fleet-server#7791, elastic-agent#16542.
Issue impacting services running in GCP us-central1
We are seeing signs of recovery for services in GCP us-central1 impacted by an <a href='https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev'>upstream CSP issue</a>. We are continuing to monitor the situation and will provide updates as they become available.
identified
An ongoing <a href="https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev">upstream CSP issue</a> is impacting services running in GCP us-central1. This includes, but is not limited to Elastic Cloud Hosted and Serverless projects in the region and our Docker Registry service. We are continuing to monitor the situation and will provide updates when they are available.
identified
An ongoing issue is impacting services running in GCP us-central1. This includes, but is not limited to Elastic Cloud Hosted and Serverless projects in the region and our Docker Registry service. We are continuing to monitor the situation and will provide updates when they are available.
investigating
We are currently investigating an issue impacting services running in GCP us-central1. We will provide additional updates as we learn more about the scope of impact.
Legacy Incident Archive
37 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Missing Metrics in Cloud Console - Azure North Europe
minorSource not attested
Last archived state: resolved
View archived record details
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
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 2026
Issue creating new projects in AWS ap-southeast-2
majorSource not attested
Last archived state: resolved
View archived record details
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.
Upstream Azure Outage Causing Service Degradation
majorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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...
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 ...
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...
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
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...
Missing Metrics in Cloud Console - Azure North Europe
majorSource not attested
Last archived state: resolved
View archived record details
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.
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.
AutoOps Login Issues for New Customers
majorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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...
Temporarily unavailability of Serverless Projects Functionality
majorSource not attested
Last archived state: resolved
View archived record details
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.
Issues with Email Alerts
majorSource not attested
Last archived state: resolved
View archived record details
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.
investigating
We are currently investigating reports that some customers may be facing issues with email alerts.
April 2026
Delayed AutoOps Metrics in AWS us-east-1
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
This issue has now been resolved and we are continuing to monitor the system.
identified
We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.
Missing Metrics in Cloud Console — US East (us-east-1)
majorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
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.
Elevated Error Rates and Latency — EU West Region
majorSource not attested
Last archived state: resolved
View archived record details
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.
identified
We are continuing to work on a fix for this issue.
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.
