403 error when trying to access Autoops in newly created serverless projects
View the provider incident record →Current answer
Elastic Cloud experienced a major incident: 403 error when trying to access Autoops in newly created serverless projects. ServiceAlert observed recovery on Oct 22, 2026.
Official Elastic Cloud status page Current Elastic Cloud status
ServiceAlert observed status change:
Looking for an update now? Check the current status, or follow Elastic Cloud for future changes.
Incident Lifecycle
Incident Timeline
Identified
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.
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.
Oct 22, 2026 at 12:00 PM UTC
Investigating
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
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
Oct 22, 2026 at 11:19 AM UTC
Was your business affected by this Elastic Cloud outage?
Follow Elastic Cloud and route available status alerts to email or a team channel.