- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2025-11-18 14:52 UTC and 2025-11-18 14: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 1
- resolved
We are currently recovering from the sign-in and UI issues affecting the product. The root cause has been identified as ongoing incidents with our third-party providers, Cloudflare and Auth0. Although our systems are stabilizing, both Cloudflare and Auth0 have not yet marked their incidents as fully resolved: • Cloudflare status: https://www.cloudflarestatus.com/?t=1 • Auth0 status: https://status.auth0.com/incidents/hdwf387t3nx7 We continue to monitor the situation closely and will provide further updates as the upstream services progress toward full recovery.
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-26ea55ebcf
Is Qdrant Cloud still down?
No, this incident was resolved 2025-11-18 14:52 UTC. For Qdrant Cloud's live state, see https://down.guide/qdrant.
How long did it last?
0m, from 2025-11-18 14:52 UTC to 2025-11-18 14: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.