- Level
- confirmed
- Worst impact
- Degraded
- Components
- Cloud UI, AWS us-east-1
- Regions
- us, us-east-1
- Down Index
- 16of 100
What to do
Check whether you use Qdrant Cloud Cloud UI, AWS us-east-1 in us, us-east-1. 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-17 20:22 UTC and 2026-10-17 20:22 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
Monitoring metrics, including the /sys_metrics endpoint, are currently unavailable for clusters in AWS us-east-1. Clusters keep running, and reads and writes are not affected. We have found the cause in our internal metrics collection and are working on a fix. Metrics will be available again once it 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-39afdd540f
Is Qdrant Cloud still down?
No, this incident was resolved 2026-10-17 20:22 UTC. For Qdrant Cloud's live state, see https://down.guide/qdrant.
How long did it last?
0m, from 2026-10-17 20:22 UTC to 2026-10-17 20:22 UTC, by the times Qdrant Cloud posted.
What was affected?
Qdrant Cloud named Cloud UI, AWS us-east-1 in us, us-east-1.
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.