Skip to main content
Elastic Cloud

AutoOps deployments marked as Inactive in AWS us-east-1 region

Partial outage Lasted 2h 50m · started · Elastic Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
AutoOps
Regions
us, us-east-1
Down Index
38of 100

What to do

  • Check whether you use Elastic Cloud AutoOps in us, us-east-1. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 50m it lasted.

    Anything that failed between 2026-03-27 04:33 UTC and 2026-03-27 07:23 UTC may need a replay.
  • Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Elastic Cloud 4

  1. investigating

    We are currently investigating an outage of AutoOps in AWS us-east-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

    provider

  2. monitoring

    We have identified the issue and applied mitigations to bring AutoOps in the AWS us-east-1 region back to functionality. Customer deployments may still be marked as inactive, and recent metrics may still not be available. We expect AutoOps to return to full functionality within the next hour. We will provide an update when one is available or within the hour, whichever comes first.

    provider

  3. monitoring

    We have mitigated the issue, and AutoOps is back to full functionality in the AWS us-east-1 region. We will continue monitoring the signals from the region to ensure AutoOps remains fully functional, and will share another update once the issue is fully resolved.

    provider

  4. resolved

    AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7ad052f0b7

Is Elastic Cloud still down?

No, this incident was resolved 2026-03-27 07:23 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.

How long did it last?

2h 50m, from 2026-03-27 04:33 UTC to 2026-03-27 07:23 UTC, by the times Elastic Cloud posted.

What was affected?

Elastic Cloud named AutoOps in us, us-east-1.

What caused it?

Elastic Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Elastic Cloud's official status page, https://status.elastic.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.