Elastic favicon

Elastic Cloud outage on 2026-10-22

elastic.co
October 2026 22 Major incident

If you created a new Elastic Cloud or Elastic Cloud Serverless account in AWS us-east-1 on 22 October 2026, AutoOps may have returned an HTTP 403 error for most of the day. The fault sat with Elastic and lasted 9h 32m by their own clock, though they say the underlying issue was fixed well before the incident was formally closed.

Started

11:19 UTC

Duration

Lasted 9h 32m

Source

IsDown

Next time

Elastic is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

Elastic opened this incident at 11:19 UTC, reporting that AutoOps was returning HTTP 403 errors for accounts newly created in the AWS us-east-1 region. The affected window, per Elastic, was accounts created since roughly 00:00 to 00:30 UTC that same day, a detail that shifted slightly between their first two updates. Both Elastic Cloud Hosted and Elastic Cloud Serverless were named as affected, but only for AutoOps access on new accounts. Elastic was explicit that existing deployments and projects, and all other Elastic Cloud functionality, were untouched. At 12:00 UTC they identified a cause internally, said a fix was rolling out, and projected full resolution by 13:00 UTC. That projection did not hold. The next update did not arrive until 20:50 UTC, over eight hours later, when Elastic marked the incident resolved and stated the actual fix had landed at 12:30 UTC, close to their original estimate. That leaves a long gap between when Elastic says the problem was actually fixed and when they got around to saying so publicly. No components list was published alongside this incident, and no user reports were filed during the window on record. There is nothing in Elastic's updates explaining the root cause beyond "identified the cause", so the technical reason behind the 403 errors is not on the record.

Learning

This incident only touched AutoOps for brand-new accounts in one AWS region, a narrow enough slice that monitoring aimed at your own deployments or projects would have stayed green the entire time, exactly as Elastic said existing deployments and projects were unaffected. That is not a contradiction: your endpoints and Elastic's new-account provisioning path are different layers, and a fault in one does not have to show up in the other. The real gap here was not in the fix but in communication, Elastic says the problem was resolved at 12:30 UTC yet did not publish that until 20:50 UTC, which means anyone watching only the status page had no way to know the outage was actually over for hours. Elastic's own history shows 22 incidents in the last 90 days with a median duration of 5 hours 55 minutes, so a multi-hour event is not unusual for this provider, and UptimeRobot's own 30-day figures for Elastic Cloud show a similar pattern, 8 incidents with a median duration of 8h 14m. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.