GlobalOutageMap
← Live dashboard
Elastic Cloud

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

ActivemajorOfficial source confirmedSingle region affectedSource start Oct 22, 2026, 11:19 AM

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 live status →

Are you affected by this incident?

One tap, no account. Your report helps others see if the problem is just them.

Choose your status. You can add a comment next.

No visitor reports in the last 24 hours yet.

Updates (2)

  1. Oct 22, 2026, 12:00 PM
    403 error when trying to access Autoops in newly created serverless projects

    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 ↗
  2. Oct 22, 2026, 11:19 AM
    403 error when trying to access Autoops in newly created serverless projects

    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 ↗

What to do right now

  • Check the provider's own status page. Open Elastic Cloud's official status page ↗
  • Don't restart everything. If the outage is upstream (cloud provider, CDN, auth provider), redeploying your own service usually won't help and may make recovery slower.
  • Communicate early. Even a one-line update to your users referencing the upstream incident reduces support load dramatically.
  • Watch this page. We post each new vendor update and source as it lands. Bookmark or share the URL with your team.

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.