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

> Elastic Cloud status incident “403 error when trying to access Autoops in newly created serverless projects” on 2026-10-22: impact major (vendor’s label), 9.5 h, 3 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft
Last updated: 2026-10-22T20:53:52Z

- Impact (vendor’s label): major
- Status: resolved · edited after publishing
- Started: 2026-10-22 11:19 UTC · Resolved: 2026-10-22 20:50 UTC · Duration: 9.5 h
- Updates: 3
- [Vendor status page: https://status.elastic.co/incidents/x522yx02qbft](https://status.elastic.co/incidents/x522yx02qbft)
- [Company: Elastic Cloud](https://rewindex.com/company/elastic-cloud.md)

## Timeline of updates

- **investigating** 2026-10-22 11:19 UTC: 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
- **identified** 2026-10-22 12:00 UTC: 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.
- **resolved** 2026-10-22 20:50 UTC: 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.

## Rewindex changes for this incident

- 2026-10-22 11:19 UTC: [Major incident: 403 error when trying to access Autoops in newly created serverless projects](https://rewindex.com/change/i948c848300dd5b.md)
- 2026-10-22 12:04 UTC: [Incident updated: 403 error when trying to access Autoops in newly created serverless projects](https://rewindex.com/change/r53a2fb31e67354.md)
- 2026-10-22 20:53 UTC: [Incident updated: 403 error when trying to access Autoops in newly created serverless projects](https://rewindex.com/change/rb7f5029e26a0da.md)

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

- Canonical URL: https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft
- Citation: Elastic Cloud, “403 error when trying to access Autoops in newly created serverless projects” (2026-10-22 11:19 UTC). Archived by Rewindex: https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft (CC BY 4.0).
- Markdown link: `[Elastic Cloud: 403 error when trying to access Autoops in newly created serverless projects (2026-10-22)](https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft)`


---
Canonical: https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft · Markdown: https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft.md · JSON: https://rewindex.com/api/v1/companies/elastic-cloud/incidents/x522yx02qbft · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:18:30.241Z