t
Outage recap · turbopuffer

turbopuffer outage — December 15, 2025

On December 15, 2025, turbopuffer had 2 reported incidents on turbopuffer's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded service (500 responses)

minor
Started
Dec 15, 5:25 AM EST
Resolved
Dec 15, 5:30 AM EST
Duration
5 min

turbopuffer's updates (2)

  1. monitoring · Dec 15, 5:25 AM EST

    Some of our query nodes restarted repeatedly due to OOMs caused by a code path that was producing very large allocations. We have deployed a fix, and the service has recovered. We are monitoring.

  2. resolved · Dec 15, 5:30 AM EST

    Service is stable.

Updates are turbopuffer's own words from its status page (status: resolved); we never add an inferred cause.

Degraded performance in aws-us-west-2

minor
Started
Dec 15, 12:14 PM EST
Resolved
Dec 15, 1:03 PM EST
Duration
49 min

turbopuffer's updates (2)

  1. identified · Dec 15, 12:14 PM EST

    Some query nodes are currently experiencing excessive load, leading to 429s for certain namespaces. We have identified the problem and have a fix in preparation.

  2. resolved · Dec 15, 1:03 PM EST

    The problematic queries have been isolated and traffic has been restored to normal.

Updates are turbopuffer's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with turbopuffer. This recap summarizes incidents published on turbopuffer's official status page.