- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AutoOps
- Down Index
- 26of 100
What to do
Check whether you use Elastic Cloud AutoOps. 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 35m it lasted.
Anything that failed between 2026-07-21 13:45 UTC and 2026-07-21 14:21 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 2
- identified
RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe. Note this incident has already been resolved, and is being posted retroactively.
provider
- resolved
This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
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-47a7b6d24f
Is Elastic Cloud still down?
No, this incident was resolved 2026-07-21 14:21 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
35m, from 2026-07-21 13:45 UTC to 2026-07-21 14:21 UTC, by the times Elastic Cloud posted.
What was affected?
Elastic Cloud named AutoOps.
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.