- Level
- confirmed
- Worst impact
- Degraded
- Components
- Azure germanywestcentral
- Down Index
- 9of 100
What to do
Check whether you use Qdrant Cloud Azure germanywestcentral. 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 0m it lasted.
Anything that failed between 2026-10-08 10:07 UTC and 2026-10-08 10:07 UTC may need a replay.Subscribe to Qdrant Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=qdrant works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Qdrant Cloud 1
- resolved
We're investigating an issue affecting Qdrant Cloud clusters in the Azure Germany West Central region. Some clusters are currently unavailable, and others are running with fewer replicas than usual. Our engineers are investigating the issue. You don't need to take any action. Please avoid deleting or recreating your cluster while we work on this. We'll post the next update asap.
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-eefb324fc6
Is Qdrant Cloud still down?
No, this incident was resolved 2026-10-08 10:07 UTC. For Qdrant Cloud's live state, see https://down.guide/qdrant.
How long did it last?
0m, from 2026-10-08 10:07 UTC to 2026-10-08 10:07 UTC, by the times Qdrant Cloud posted.
What was affected?
Qdrant Cloud named Azure germanywestcentral.
What caused it?
Qdrant Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Qdrant Cloud's official status page, https://status.qdrant.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.