- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- au
What to do
Check whether you use Elastic Cloud in au. 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 5m it lasted.
Anything that failed between 2026-06-16 22:54 UTC and 2026-06-17 00:59 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 are currently experiencing an issue impacting the ability to ingest data into mOTLP and .amp endpoints in the Azure Australia East region. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.
provider
- identified
This incident is ongoing. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.
provider
- resolved
This issue is 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-7a752c7d72
Is Elastic Cloud still down?
No, this incident was resolved 2026-06-17 00:59 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
2h 5m, from 2026-06-16 22:54 UTC to 2026-06-17 00:59 UTC, by the times Elastic Cloud posted.
What was affected?
Elastic Cloud named in au.
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.