- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
- Down Index
- 23of 100
What to do
Check whether you use Elastic Cloud in eu. 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 6m it lasted.
Anything that failed between 2026-07-02 00:54 UTC and 2026-07-02 03:00 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 have identified continued impact for a subset of affected customers using EIS. Our team is investigating an issue with the previous remediation and is working to ensure all affected environments are fully restored.
provider
- monitoring
The issue affecting a subset of customers with EIS in EMEA regions has been mitigated and the service have been restored.
provider
- resolved
The incident impacting a subset of customers with EIS in EMEA regions has been resolved. Services have been fully restored and the team has confirmed stability.
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-117d85391e
Is Elastic Cloud still down?
No, this incident was resolved 2026-07-02 03:00 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
2h 6m, from 2026-07-02 00:54 UTC to 2026-07-02 03:00 UTC, by the times Elastic Cloud posted.
What was affected?
Elastic Cloud named in eu.
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.