Is Elastic Cloud down?

We are currently investigating an issue preventing access to the Elastic Support portal. At this time, customers may experience issues authenticating to the support portal.

We have identified an issue preventing access to the Elastic Support portal caused by an upstream provider. The provider has confirmed a fix that has restored access for some of its affected environments and is now rolling it out to the rest. At this time, customers may experience issues authenticating to the support portal.

The upstream provider has completed its fix, and access to the Elastic Support portal has been restored. Customers can authenticate to the support portal again. We are considering this issue resolved and will be providing no further updates. If you continue to have issues, please contact us.

We are investigating an issue affecting AutoOps for newly created accounts in the AWS us-east-1 region. Accounts created after 00:00 UTC on October 22, 2026 may be unable to access AutoOps and may see an error (HTTP 403) when opening it. Elastic Cloud Hosted: AutoOps is not available for affected new accounts. Elastic Cloud Serverless: AutoOps is not available for affected new accounts. Existing deployments and projects, and all other Elastic Cloud functionality, are not affected. Our engineering teams are working to identify the cause and restore access. We will provide the next update within 60 minutes, or sooner if there is a significant change

We have identified the cause of the issue affecting AutoOps and are deploying a fix. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it. The fix is rolling out now, and we expect the situation to be fully resolved by 13:00 UTC. Existing deployments and projects, and all other Elastic Cloud functionality, are not affected.

We resolved the issue affecting AutoOps at 12:30 UTC. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it.

We are investigating an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. New project and deployment creation in Azure may be delayed.

We have identified an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. New project and deployment creation in Azure may be delayed. Engineers are actively working to mitigate the issue.

Engineers have identified and mitigated an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. We are monitoring the issue to ensure operations continue normally.

Engineers have mitigated an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. Scaling is working as expected.

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.

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.

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.

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.

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.

The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is recovering. Our cloud provider reports recovery of services for most workloads in the region, and we are seeing progress on our side as the affected zone comes back. Elastic Cloud Hosted: An increasing number of 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. Some deployments may still be unavailable or degraded, and some may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support. Operations may take longer than usual while capacity is restored.

The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. We are continuing to work towards full recovery of our services. Elastic Cloud Hosted: An increasing number of 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. Some deployments may still be unavailable or degraded, and some may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support. Operations may take longer than usual while capacity is restored.

The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. Engineering has completed recovery of infrastructure running in the affected availability zone. Elastic Cloud Hosted: Customers whose plan changes or other operations failed during the incident are advised to retry them from the Elastic Cloud console. Some deployments may still be unavailable or degraded, and may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support.

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.

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.

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.

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.

The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.