ChangesElastic Cloud403 error when trying to access Autoops in newly created serverless projects
Elastic Cloud: Incident updated: 403 error when trying to access Autoops in newly created serverless projects
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.
Compared with the previous archived version of this incident (10 to 30-minute polling). 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 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.
Before captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
df6815c3a9e6ce40…After captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
45f8b7481215c7ec…
History of this incident
Thursday, October 22
3 incident changes
- Normal progressIncident
- Normal progressIncident
Incident update403 error when trying to access Autoops in newly created serverless projectsthis change
- OutageMajor incident
Cite this
Incident updated: 403 error when trying to access Autoops in newly created serverless projects on Elastic Cloud’s status page, changed 2026-10-22 12:04 UTC (change 2 of 3).
- Title
- Incident updated: 403 error when trying to access Autoops in newly created serverless projects
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/change/r53a2fb31e67354