rewindex

CompaniesElastic CloudIncidents

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

MajorStatus: resolvededitedStarted Resolved (9.5 h)3 updatesstatus.elastic.co (opens in new tab)

Timeline of updates

  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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.elastic.co (opens in new tab).

Cite this

Status incident (vendor impact label: major) posted by Elastic Cloud, started 2026-10-22 11:19 UTC, resolved after 9.5 h, 3 update(s); edited after publishing.

Title
403 error when trying to access Autoops in newly created serverless projects
Vendor
Elastic Cloud
Date
URL
https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft

Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on October 22, 2026Elastic Cloud in October 2026MarkdownJSON