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

> Incident updated: 403 error when trying to access Autoops in newly created serverless projects. Detected 2026-10-22 by Rewindex: what changed on Elastic Cloud’s status page, with the before/after diff.

Canonical: https://rewindex.com/change/r53a2fb31e67354
Last updated: 2026-10-22T12:04:02Z

**Summary:** _summary pending_
- Kind: Incident update · Label: Normal progress (rule)
- Changed: 2026-10-22 12:04 UTC · Detected: 2026-10-22 12:04 UTC
- [Source: https://status.elastic.co/incidents/x522yx02qbft](https://status.elastic.co/incidents/x522yx02qbft)
- [Company: Elastic Cloud](https://rewindex.com/company/elastic-cloud.md)
- Versions: before incident\_version:276/x522yx02qbft@f4e5798168ab → after incident\_version:276/x522yx02qbft@4708f1690392
- Change 2 of 3 for this incident

Incident page (full timeline): [403 error when trying to access Autoops in newly created serverless projects](https://rewindex.com/company/elastic-cloud/incidents/x522yx02qbft.md)
## What changed

**1. Changed: Status**

```diff
- investigating
+ identified
```

**2. Added: Update** (identified) · 2026-10-22 12:00 UTC

```diff
+ 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.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 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) | outage |
| 2026-10-22 12:04 UTC | Incident updated: 403 error when trying to access Autoops in newly created serverless projects (this change) | Normal progress |
| 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) | Normal progress |

Previous: [change](https://rewindex.com/change/i948c848300dd5b.md) · Next: [change](https://rewindex.com/change/rb7f5029e26a0da.md) · All Elastic Cloud changes: [timeline](https://rewindex.com/company/elastic-cloud/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._

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

- Canonical URL: https://rewindex.com/change/r53a2fb31e67354
- Citation: Elastic Cloud, “Incident updated: 403 error when trying to access Autoops in newly created serverless projects” (2026-10-22 12:04 UTC). Archived by Rewindex: https://rewindex.com/change/r53a2fb31e67354 (CC BY 4.0).
- Markdown link: `[Elastic Cloud: Incident updated: 403 error when trying to access Autoops in newly created serverless projects (2026-10-22)](https://rewindex.com/change/r53a2fb31e67354)`


---
Canonical: https://rewindex.com/change/r53a2fb31e67354 · Markdown: https://rewindex.com/change/r53a2fb31e67354.md · JSON: https://rewindex.com/api/v1/changes/r53a2fb31e67354 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T17:15:32.790Z