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

> Major incident: 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/i948c848300dd5b
Last updated: 2026-10-22T11:23:56Z

**Summary:** _summary pending_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-10-22 11:19 UTC · Detected: 2026-10-22 11:23 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 (none: first archived) → after incident\_version:276/x522yx02qbft@f4e5798168ab
- Change 1 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. Added: Title**

```diff
+ 403 error when trying to access Autoops in newly created serverless projects
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ investigating
```

**4. Added: Start time**

```diff
+ 2026-10-22 11:19 UTC
```

**5. Added: Update** (investigating) · 2026-10-22 11:19 UTC

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

## 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 (this change) | outage |
| 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) | 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 |

Next: [change](https://rewindex.com/change/r53a2fb31e67354.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

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

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


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