- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Elastic Cloud Serverless
- Regions
- us, us-east-1
- Down Index
- 37of 100
What to do
Check whether you use Elastic Cloud Elastic Cloud Serverless 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 1h 42m it lasted.
Anything that failed between 2026-06-15 17:31 UTC and 2026-06-15 19:13 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 currently investigating an intermittent issue which may cause unavailability of Elastic Cloud Serverless projects or the inability to create new Serverless projects in AWS us-east-1. We will continue to update status as we learn more.
provider
- monitoring
This issue has been mitigated, and we are continuing to monitor the situation.
provider
- resolved
This issue 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-b301259b90
Is Elastic Cloud still down?
No, this incident was resolved 2026-06-15 19:13 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
1h 42m, from 2026-06-15 17:31 UTC to 2026-06-15 19:13 UTC, by the times Elastic Cloud posted.
What was affected?
Elastic Cloud named Elastic Cloud Serverless 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.