turbopuffer outage history

We hold 25 turbopuffer incidents from turbopuffer's status page, the newest from Oct 8, 2026. 25 of the 25 listed carry turbopuffer'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 41d 11h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
100%
0 incidents · no downtime
2015 checks
Operational · 30d
100%
0 incidents · no downtime
8638 checks
Operational · since Jun 22, 2026
99.71%
5 incidents · ≈10h 10m degraded
41620 checks

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

Since Jul 16, 2026, turbopuffer's status page has marked 2 turbopuffer components as impaired, across 112 of our five-minute readings. gcp-us-central1 accounts for the most: 101 readings (about 8.4 hours) on 2 days, most recently on Oct 8, 2026. Next is Dashboard, with 11 readings on 1 day. We hold 25 turbopuffer incidents from turbopuffer's status page, the earliest from Oct 20, 2025. Of the 22 that turbopuffer closed with an end time, the median lasted 54 minutes.

ComponentOutageDegradedMaint.DaysLast
gcp-us-central1—101—2Oct 8, 2026
Dashboard—11—1Jul 16, 2026

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

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

October 2026 · 1

September 2026 · 2

August 2026 · 1

July 2026 · 1

May 2026 · 2

April 2026 · 2

March 2026 · 3

January 2026 · 5

December 2025 · 4

November 2025 · 1

October 2025 · 3

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