Turbopuffer

turbopuffer.com (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 4 incidents, 4 major or critical
Rewrites caught: None so far
Next deprecation: None announced

Turbopuffer incidents per day, last 90 days

Our copy of Turbopuffer’s status page starts Aug 27; hatched days are before that. Select a day to jump to its incidents.

How Turbopuffer reports incidents

Not enough incidents to compare Turbopuffer with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Turbopuffer has 4 and 4).

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

Dependencies

What Turbopuffer relies on and who relies on Turbopuffer, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Turbopuffer depends on

Provider	Evidence	Signal
Google Cloud (us-central1, us-southeast1)	blamed in 1 incident; named as hosting in 2 “…Elevated rate of 5xx in gcp-us-central1 The issue upstream in Google Cloud Storage is resolved and us-central1 operations have returned to normal. Error rates have recovered as Google rolls out a fix…” incident	Likely

Who depends on Turbopuffer

Vendor	Evidence	Signal
Writer	listed as a subprocessor	Weak

Runs in (named in its incidents): Google Cloud us-central1 (2), Google Cloud us-southeast1 (1).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.