Skip to content
OutageDeck

Incident detail

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

Resolved incidentMajor

Timeline window

to

Get alerted the next time Elastic Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Elastic Cloud alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

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

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

  3. Resolved

    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.

Keep exploring

More from Elastic Cloud

Neighboring incidents on Elastic Cloud's timeline and the rest of their record on OutageDeck.

← Older incident

Elastic Cloud scaling issues in Azure

Newer incident →

Elastic Support Portal is unavailable

All Elastic Cloud incidentsElastic Cloud live status