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

1. resolvedOct 22, 2026, 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.

2. identifiedOct 22, 2026, 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.

3. investigatingOct 22, 2026, 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

What APIStatus.watch saw

• Oct 22, 2026, 13:31 UTCoperational → unknown
• Oct 22, 2026, 13:36 UTCunknown → operational
• Oct 22, 2026, 13:41 UTCoperational → unknown
• Oct 22, 2026, 13:46 UTCunknown → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Supabase: Project lifecycle operation errors in the EU regionMajor · Oct 22, 2026, 03:53 UTC
• Supabase: Elevated Mgmt API Error Rates in Multiple RegionsMajor · Oct 22, 2026, 11:29 UTC
• Cloudflare: Network Error Log Processing UnavailableMajor · Oct 22, 2026, 16:30 UTC
• HashiCorp Vault: GitHub and Other VCS workloads experiencing intermittent issuesMajor · Oct 22, 2026, 17:15 UTC
• Cloudflare: Delayed audit log delivery for WARP and Zero Trust servicesMajor · Oct 22, 2026, 17:32 UTC
• Shopify: Some merchants encountering error messages when trying to login to their adminsMinor · Oct 8, 2026, 14:49 UTC
• Twilio: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• Twilio: SMS Delivery Delays and Failures Between a Subset of Twilio Long Codes and Multiple Networks in ItalyMinor · Oct 19, 2026, 16:53 UTC
• Twilio: Voice Call Post Dial Delay From a Subset of Twilio Phone Numbers to IsraelMinor · Oct 21, 2026, 03:10 UTC

How often does Elasticsearch have incidents?

Elasticsearch reported 23 incidents in the last 90 days, 22 of them major or critical. A typical incident lasted 5h 53m. See Elasticsearch's uptime and incident history