- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 100
What to do
Check whether your product depends on Qdrant Cloud. 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 14m it lasted.
Anything that failed between 2026-04-28 11:38 UTC and 2026-04-28 11:52 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 2
- update
We're investigating an issue affecting cluster configuration changes on the Cloud UI. The cluster itself is not affected, your data and search operations continue to run normally. We're working on a fix and will provide updates here as soon as we have more information.
provider
- resolved
We've deployed a fix to production and this issue is now resolved. Cluster configuration changes through the Cloud UI are working as expected. We apologize for any inconvenience this may have caused.
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-f843256dd9
Is Qdrant Cloud still down?
No, this incident was resolved 2026-04-28 11:52 UTC. For Qdrant Cloud's live state, see https://down.guide/qdrant.
How long did it last?
14m, from 2026-04-28 11:38 UTC to 2026-04-28 11:52 UTC, by the times Qdrant Cloud posted.
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.