โ† Outage Reports
Elastic logo
Elastic
elastic.co
๐Ÿ”ด Outages Resolved

Elastic investigating 403 errors blocking AutoOps access for new serverless projects

New accounts created after October 22 in AWS us-east-1 unable to access AutoOps feature.

By The Downtime ยท Oct 22, 2026 ยท 11:30 AM ยทUpdated 2 weeks ago

Elastic is investigating a major incident affecting AutoOps functionality for newly created serverless projects in the AWS us-east-1 region. Accounts created after 00:00 UTC on October 22, 2026 are unable to access AutoOps and receive HTTP 403 errors when attempting to open the feature. Existing deployments, projects, and all other Elastic Cloud functionality remain unaffected.

Elastic provides search, observability, and analytics infrastructure widely used by enterprises and developers for log management, security monitoring, and application performance tracking.

The company's engineering teams are actively investigating the root cause. Elastic said it will provide its next status update within 60 minutes, or sooner if conditions change significantly.

This is a developing story. Check back for updates.

๐Ÿ•’ Live updates (3)

resolved Oct 22, 8:50 PM

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.

identified Oct 22, 12:00 PM

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.

investigating Oct 22, 11:19 AM

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

๐Ÿ“Ž Sources

Outage details are aggregated from official provider status pages. The Downtime reports them as a public service and is not affiliated with the providers named.

๐Ÿ’ฌ Comments (0)

No comments yet โ€” be the first to weigh in.

Join the conversation.