Elastic Cloud outage, 22 October 2026

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

Started
Resolved
22 Oct 2026, 20:50 UTC (after 9 h 30 min)
Impact
Major

Is this still happening?

No. Elastic Cloud marked this incident resolved on 22 Oct 2026, 20:50 UTC, 9 h 30 min after it began.

Right now: Elastic Cloud reports all systems operational. (as of 26 Oct, 03:45 UTC) Live Elastic Cloud status

Last update from Elastic Cloud

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.

22 Oct 2026, 20:50 UTC

Read the full incident on the official Elastic Cloud status page

Similar Elastic Cloud incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 3 h 34 min

    Issue when creating Serverless projects in Azure eastus region

  2. , resolved after 1 h 22 min

    [RESOLVED - 2026-08-26] APM endpoints for serverless projects not available

  3. , resolved after 4 h 42 min

    Serverless project creation delayed or failing

Other recent Elastic Cloud incidents

  1. Elastic Support Portal is unavailable

  2. Elastic Cloud scaling issues in Azure

  3. Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)

  4. Delayed or Unavailable project operation in GCP us-central1

  5. Delayed Serverless Metrics in Azure UAE North region

  6. Degraded Performance: Cloud Provisioning Delays

  7. AutoOps node metrics temporarily unavailable in some regions

  8. Elastic Support Portal unavailable

All recorded Elastic Cloud incidents