- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AutoOps
- Regions
- us, us-east-1
- Down Index
- 35of 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 51m it lasted.
Anything that failed between 2026-04-30 21:46 UTC and 2026-04-30 22:36 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 3
- identified
We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.
provider
- monitoring
This issue has now been resolved and we are continuing to monitor the system.
provider
- resolved
This issue has now 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-4551ed1fe2
Is Elastic Cloud still down?
No, this incident was resolved 2026-04-30 22:36 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
51m, from 2026-04-30 21:46 UTC to 2026-04-30 22:36 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.