How do I know if Qdrant is down?

Verify Qdrant status by: 1) Hitting the /healthz and /readyz endpoints on your cluster, 2) Checking the Qdrant Cloud status page and console, 3) Searching "Qdrant down" on X/Twitter, or 4) Using API Status Check to monitor your cluster endpoint.

Is Qdrant down or is my collection just indexing?

After a large upsert, a collection can be in an "indexing" or "yellow" state where queries are slower but the service is up. Check /readyz and the collection status before assuming a full outage.

What should I do when Qdrant is down?

Check /healthz and /readyz, verify your API key and cluster URL, inspect memory and disk usage for self-hosted nodes, and check the Qdrant Cloud status page before assuming a platform-wide outage.

Can I monitor my Qdrant cluster automatically?

Yes. API Status Check can poll your Qdrant /healthz endpoint continuously and send instant alerts when the cluster stops responding.

Is Qdrant Down? How to Check Qdrant Status in 2026

Q: Why does Qdrant go down?

Qdrant outages are typically caused by memory pressure from large HNSW indexes, disk I/O saturation during heavy upserts, resource limits on your cluster tier, or Qdrant Cloud platform incidents.

Your semantic search starts timing out and your retrieval-augmented generation pipeline goes quiet. Before you blame your own code, ask the right question: is Qdrant down, or is it just me?

Qdrant is a high-performance open-source vector database used for semantic search, recommendations, and RAG. Whether you run it self-hosted or on Qdrant Cloud, failures can come from memory pressure on large indexes, disk saturation during upserts, or a managed-platform incident.

This guide gives you the fastest ways to confirm a Qdrant outage and a checklist to bring search back.

How to Check if Qdrant is Down (Fastest Methods)

Use these proven methods to verify a Qdrant outage instead of guessing:

1. Hit the Health Endpoints

The fastest signal is /healthz and /readyz on your cluster URL. A 200 means the node is alive and ready; a non-200 or timeout means the cluster is unhealthy.

2. Check the Cloud Console and Status Page

For Qdrant Cloud, open the console and status page. A flagged cluster or posted incident confirms the problem is on their side.

3. Inspect Collection Status

A collection in a "yellow" indexing state after a big upsert returns slower queries but is not down. Check the collection status before assuming an outage.

4. Use API Status Check

For continuous tracking, API Status Check polls your Qdrant endpoint around the clock and alerts you the moment it stops responding.

📡

Recommended

Monitor Your Vector Database

Don't let a vector database outage silently break your RAG pipeline. Get professional monitoring and instant alerts for Qdrant and other AI infrastructure with Better Stack.

Try Better Stack Free →

Why Does Qdrant Go Down?

Vector databases have failure modes that traditional databases don't:

Memory Pressure: HNSW indexes live largely in RAM; a collection that outgrows available memory can OOM the node.
Disk I/O Saturation: Heavy upserts or snapshots can saturate disk throughput and make the cluster unresponsive.
Resource Limits: Smaller Qdrant Cloud tiers have CPU and memory caps; exceeding them during traffic spikes causes failures.
Platform Incidents: Qdrant Cloud, like any managed service, can have control-plane or regional incidents.

🔐

Recommended

Secure Your API Keys

Stop storing your Qdrant and embedding provider keys in plain text. Use 1Password to keep your developer secrets secure and synchronized.

Try 1Password Free →

Qdrant Troubleshooting Checklist

Step 1: Confirm the Failure

Does /readyz return 200? If not, the node is not ready to serve.
Is the collection green, or yellow/indexing? Yellow means slow, not down.
Are you authenticated? A 401/403 means an API key issue, not an outage.

Step 2: Check Resources

For self-hosted clusters, inspect memory and disk. OOM-killed nodes and full disks are the most common causes of sudden Qdrant outages.

Step 3: Degrade Gracefully

Add retries and cache recent results so a brief Qdrant blip doesn't take your entire search experience offline.

Conclusion: Stay Ahead of Vector Database Outages

Vector databases are critical infrastructure for AI search and RAG. When Qdrant goes down, your retrieval layer goes dark. The best defense is monitoring that flags a failing cluster before your users notice missing results.

Automate Your Status Alerts

Get notified the second your Qdrant cluster or any other API fails. Stop guessing and start monitoring.

Start Your Free Trial →