Qdrant outage history

We hold 13 Qdrant incidents from Qdrant's status page, the newest from Nov 19, 2026. 8 of the 13 listed carry Qdrant's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 16d 17h since the last recorded problem.
Operational · 24h
100%
1 incident · no downtime
288 checks
Operational · 7d
100%
1 incident · no downtime
2015 checks
Operational · 30d
99.84%
2 incidents · ≈1h 10m degraded
8638 checks
Operational · since Jun 22, 2026
99.58%
12 incidents · ≈10h 25m degraded
41625 checks

% of our checks that found Qdrant fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Qdrant fails

Since Jul 16, 2026, Qdrant's status page has marked 13 Qdrant components as impaired, across 213 of our five-minute readings. Cloud UI accounts for the most: 65 readings (about 5.4 hours) on 4 days, 12 of them marked as an outage rather than degraded, most recently on Nov 2, 2026. Next is Azure germanywestcentral, with 45 readings on 3 days. We hold 13 Qdrant incidents from Qdrant's status page, the earliest from Apr 28, 2026. Of the 5 that Qdrant closed with an end time, the median lasted 2 h.

ComponentOutageDegradedMaint.DaysLast
Cloud UI1253484Nov 2, 2026
Azure germanywestcentral387—3Oct 8, 2026
AWS us-east-1—31—1Oct 17, 2026
Cloud API (extern)—19—2Aug 14, 2026
Hybrid Cloud47—4Oct 18, 2026
Azure southeastasia27—1Aug 14, 2026
AWS us-west-1—7—1Aug 14, 2026
Azure eastus—7—1Aug 14, 2026

Incidents by month: Apr 2026: 1 · Jul 2026: 2 · Aug 2026: 5 · Sep 2026: 1 · Oct 2026: 2 · Nov 2026: 2

Counts are five-minute readings of Qdrant's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 2

October 2026 · 2

September 2026 · 1

August 2026 · 5

July 2026 · 2

April 2026 · 1

Incidents and their updates are Qdrant's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Qdrant.