deepset outage history

We hold 3 deepset incidents from deepset's status page, the newest from Aug 25, 2026. 3 of the 3 listed carry deepset'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 79d 17h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
97.62%
0 incidents · no downtime
2015 checks
Operational · 30d
99.44%
0 incidents · no downtime
8638 checks
Operational · since Jun 22, 2026
99.68%
3 incidents · ≈5m degraded
41552 checks

% of our checks that found deepset 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 deepset fails

Since Jul 23, 2026, the only non-operational component readings we hold are scheduled maintenance, on General Availability, Search Availability. We hold 3 deepset incidents from deepset's status page, the earliest from Jul 3, 2026. Of the 3 that deepset closed with an end time, the median lasted 11 minutes.

ComponentOutageDegradedMaint.DaysLast
General Availability——1306Nov 17, 2026
Search Availability——1175Nov 17, 2026

Incidents by month: Jul 2026: 2 · Aug 2026: 1

Counts are five-minute readings of deepset'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

August 2026 · 1

July 2026 · 2

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