Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Elastic Cloud

403 error when trying to access Autoops in newly created serverless projects

Resolved Major
October 22, 2026 - Started 26 days ago - Lasted about 10 hours
Official incident page

Incident Report

Summary AI Generated

New Elastic Cloud accounts created in AWS us-east-1 after approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps, receiving HTTP 403 errors on both Hosted and Serverless platforms. Existing deployments and all other Elastic Cloud functionality remained unaffected throughout the incident. The root cause was identified and a fix was deployed, fully resolving the issue by 12:30 UTC after approximately 9.6 hours.

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

Trusted by 1,000+ teams

The Status Page Aggregator with Early Outage Detection

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED 25 days ago - at 10/22/2026 08:50PM

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 26 days ago - at 10/22/2026 12:00PM

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 26 days ago - at 10/22/2026 11:19AM

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

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook