- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-4
- Down Index
- 38of 100
What to do
Check whether you use Elastic Cloud in us, us-east-4. 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 46m it lasted.
Anything that failed between 2026-04-06 17:58 UTC and 2026-04-06 20:43 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
- investigating
We are investigating an issue in our Synthetics service on us-east-4. Some customer monitor jobs may not run on their expected schedule. We will provide an update in an hour or earlier.
provider
- identified
We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours.
provider
- resolved
Issue has been fixed and there should be no more customer impact
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-10150ef51e
Is Elastic Cloud still down?
No, this incident was resolved 2026-04-06 20:43 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
2h 46m, from 2026-04-06 17:58 UTC to 2026-04-06 20:43 UTC, by the times Elastic Cloud posted.
What was affected?
Elastic Cloud named in us, us-east-4.
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.