Live / Elastic Cloud (Public) / Incident
Elastic Cloud (Public): 403 error when trying to access Autoops in newly created serverless projects
Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-10-22 20:50 UTC
Public — what happened
Summary
Elastic Cloud reported that people who created new accounts in the AWS us-east-1 region on October 22, 2026 could not open AutoOps and saw an access error (HTTP 403). It said this affected both the Hosted and Serverless offerings, while existing deployments and projects and other Elastic Cloud features were not affected. The company opened its investigation at 11:19 UTC, and by 12:00 UTC it said it had identified the cause and was rolling out a fix, which it expected to finish by 13:00 UTC. The incident is now marked resolved, with a final time of 20:50.
Timeline
- Started — 2026-10-22 11:19 UTC
- Investigating — 2026-10-22 11:19 UTC
- Identified — 2026-10-22 12:00 UTC
- Resolved — 2026-10-22 20:50 UTC · 9h 31m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Elastic Cloud (Public) against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Elastic Cloud (Public): its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Elastic Cloud (Public) report →
More from Elastic Cloud (Public)
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.