Elastic Cloud

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.

All private link traffic for AWS and Azure going to the Serverless intake-v2 endpoint (`.apm`) is not being accepted at the moment. Non private link traffic is flowing normally. We're working on a solution and we'll update this status page once the service has been restored.

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