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% 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.
- Qdrant Cloud monitoring infrastructureNov 19, 2026 · ongoing · scheduled
- Cloud UI and login unavailableNov 2, 2026 → Nov 2, 2026 · resolved
- Cluster metrics unavailable in AWS us-east-1Oct 17, 2026 → Oct 17, 2026 · resolved
- Cluster Availability Issues in Germany West CentralOct 8, 2026 → Oct 8, 2026 · resolved
- Scheduled maintenance: Qdrant Cloud logging infrastructureSep 21, 2026 → Sep 21, 2026 · resolved
- Multiple services degraded in Qdrant Cloud UIAug 17, 2026 → Aug 17, 2026 · resolved
- Scheduled maintenance: Qdrant Cloud monitoring infrastructureAug 15, 2026 → Aug 16, 2026 · resolved
- Configuration issue affecting network access controlsAug 14, 2026 · ongoing · resolved
- Configuration issue affecting network access controlsAug 14, 2026 → Sep 21, 2026 · maintenance
- Configuration issue affecting network access controlsAug 14, 2026 → Aug 14, 2026 · resolved
- Cloud API FailsJul 16, 2026 → Aug 16, 2026 · maintenance
- Cloud API FailsJul 16, 2026 · ongoing · resolved
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.
| Component | Outage | Degraded | Maint. | Days | Last |
|---|---|---|---|---|---|
| Cloud UI | 12 | 53 | 48 | 4 | Nov 2, 2026 |
| Azure germanywestcentral | 38 | 7 | — | 3 | Oct 8, 2026 |
| AWS us-east-1 | — | 31 | — | 1 | Oct 17, 2026 |
| Cloud API (extern) | — | 19 | — | 2 | Aug 14, 2026 |
| Hybrid Cloud | 4 | 7 | — | 4 | Oct 18, 2026 |
| Azure southeastasia | 2 | 7 | — | 1 | Aug 14, 2026 |
| AWS us-west-1 | — | 7 | — | 1 | Aug 14, 2026 |
| Azure eastus | — | 7 | — | 1 | Aug 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
- Nov 19, 2026Qdrant Cloud monitoring infrastructuremaintenancescheduled1 update
- Nov 2, 2026Cloud UI and login unavailableresolved—1 update
October 2026 · 2
- Oct 17, 2026Cluster metrics unavailable in AWS us-east-1resolved—1 update
- Oct 8, 2026Cluster Availability Issues in Germany West Centralresolved—1 update
September 2026 · 1
- Sep 21, 2026Scheduled maintenance: Qdrant Cloud logging infrastructureresolved2 h2 updates
August 2026 · 5
- Aug 17, 2026Multiple services degraded in Qdrant Cloud UIresolved1 h 31 min2 updates
- Aug 15, 2026Scheduled maintenance: Qdrant Cloud monitoring infrastructureresolved2 h2 updates
- Aug 14, 2026Configuration issue affecting network access controlsdegraded923 h 15 min
- Aug 14, 2026Configuration issue affecting network access controlsresolved—1 update
- Aug 14, 2026Configuration issue affecting network access controlsresolvedend not published
July 2026 · 2
- Jul 16, 2026Cloud API Failsresolved735 h 59 min
- Jul 16, 2026Cloud API Failsresolvedend not published
April 2026 · 1
- Apr 28, 2026Cluster Configuration Update Issue on Cloud UIresolvedend not published
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.