Skip to main content
Qdrant Cloud

Cloud API Fails

Degraded Lasted 6m · started · Qdrant Cloud's page

Level
confirmed
Worst impact
Degraded
Down Index
12of 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 6m it lasted.

    Anything that failed between 2026-07-16 12:02 UTC and 2026-07-16 12:08 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

  1. update

    We have an issue with our latest Cloud API release. We are working on it to fix it as soon as possible.

    provider

  2. resolved

    Our engineering team has resolved the issue and deployed the fix. The Cloud API is now up and running as expected.

    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-aafdeda4fe

Is Qdrant Cloud still down?

No, this incident was resolved 2026-07-16 12:08 UTC. For Qdrant Cloud's live state, see https://down.guide/qdrant.

How long did it last?

6m, from 2026-07-16 12:02 UTC to 2026-07-16 12:08 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.