Vendor record
Qdrant
Checked
Front door check counts and Qdrant’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Qdrant endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- cloud.qdrant.io
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Qdrant product, region or your app worked.
How we count front door checksQdrant says
Incident posts from Qdrant’s status page, with its titles, impact levels and times. They say what Qdrant chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents Qdrant posted, last 7 days
Most recent records · all dates
Cluster Availability Issues in Germany West Central
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(0m)
Multiple services degraded in Qdrant Cloud UI
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(1h 31m)
Configuration issue affecting network access controls
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(0m)
Cloud API Fails
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(6m)
Cluster Configuration Update Issue on Cloud UI
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(14m)
3 older records
Dashboard Degradation – Cluster Management Impacted
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(0m)
Cluster dashboards broken returning Forbidden (403)
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(0m)
Autoscaling Impacting AWS Clusters with Performance Disk Speed
Not specifiedQdrant’s postStarted, per Qdrant
Closed in our record(0m)
Your code, your dependencies
See which of your code paths call Qdrant
Connect GitHub or GitLab to find where your public or private repository uses Qdrant. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Qdrant status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Qdrant currently down?
Qdrant's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Qdrant last have an outage?
The most recent closed incident record began 8 days ago and spans 0 minutes. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Qdrant?
No. CheckUpstream checks Qdrant’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Qdrant in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Qdrant?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.