rewindex

ChangesElastic Cloud403 error when trying to access Autoops in newly created serverless projects

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

Major incidentoutage (model (Jev), 100%)Changed Detected status.elastic.co (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Elastic Cloud removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: 403 error when trying to access Autoops in newly created serverless projects
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: investigating
AddedStart time#4
Before: not present
After: 2026-10-22 11:19 UTC
AddedUpdateinvestigating#5
Before: not present
After: 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

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

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 this record existed by then and has not been changed since, by anyone, Rewindex included.

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

History of this incident

Thursday, October 22

3 incident changes

Cite this

Major incident: 403 error when trying to access Autoops in newly created serverless projects on Elastic Cloud’s status page, changed 2026-10-22 11:19 UTC (change 1 of 3).

Title
Major incident: 403 error when trying to access Autoops in newly created serverless projects
Vendor
Elastic Cloud
Date
URL
https://rewindex.com/change/i948c848300dd5b

All Elastic Cloud changesElastic Cloud profileMarkdownJSON