Qdrant logo

Is Qdrant Down?

DatabaseLive status, outages, and incident history

No. Qdrant is up right now.

Every monitored Qdrant system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s1 active incident

Know the moment Qdrant breaks

Qdrant is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Qdrant status page
How we know: the official Qdrant status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Qdrant Status Summary

As of 19:21 UTC on 14 November 2026, Qdrant is operational. PulsAPI checked Qdrant's official status page and found 28 of 28 components operational, with 1 active incident. The latest incident, "Qdrant Cloud monitoring infrastructure", was on Nov 19, 2026 and lasted 3h 0m.

Cite as: PulsAPI, “Qdrant status”, checked 14 November 2026, 19:21 UTC. https://www.pulsapi.com/services/qdrant

Qdrant Component Status

The main Qdrant systems on this page. All 28 are operational right now.

28operational
AWS ap-northeast-1
Operational
AWS ap-south-1
Operational
AWS ap-southeast-1
Operational

25 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking AWS ap-southeast-2, AWS ca-central-1, AWS eu-central-1, AWS eu-west-1, AWS eu-west-2, AWS sa-east-1, AWS us-east-1, AWS us-east-2, AWS us-west-1, AWS us-west-2, Azure eastus, Azure germanywestcentral, and 13 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Qdrant Outages & Incidents

Incident history from the official Qdrant status page, including resolution updates.

Qdrant Cloud monitoring infrastructureResolved Nov 19, 2026 · 3h 0mResolved
Cloud UI and login unavailableResolved Nov 2, 2026 · 0 minResolved
Cluster metrics unavailable in AWS us-east-1Resolved Oct 17, 2026 · 0 minResolved

Qdrant Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Qdrant incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Qdrant Outage Reports

Problems reported by engineers using Qdrant. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Qdrant problems reported yet.

Something wrong with Qdrant on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Qdrant

Qdrant posts its status at status.qdrant.io. The page covers 28 components, among them AWS ap-northeast-1, AWS ap-south-1 and AWS ap-southeast-1. Past incidents and uptime for Qdrant stay on this page, which helps when you want to know how often it has trouble.

Qdrant Status FAQ

Is Qdrant down right now?

The verdict at the top of this page comes from the latest poll of the official Qdrant status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Qdrant is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Qdrant recovers.

How do I check Qdrant uptime history?

PulsAPI tracks Qdrant uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Qdrant changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Qdrant outages?

PulsAPI reads the official Qdrant status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Qdrant components?

Yes. PulsAPI monitors 28 individual Qdrant components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Qdrant goes down?

Yes. Create a free account and subscribe to Qdrant: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Qdrant to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Qdrant problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Qdrant?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Qdrant plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Qdrant with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services