t
Outage recap · turbopuffer

turbopuffer outage — January 28, 2026

On January 28, 2026, turbopuffer had 3 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.

aws-us-west-2: Increased 429's on a subset of nodes

minor
Started
Jan 28, 5:10 AM EST
Resolved
Jan 28, 5:15 AM EST
Duration
4 min

turbopuffer's updates (2)

  1. monitoring · Jan 28, 5:02 AM EST

    We identified an issue causing high CPU utilization on a subset of query nodes in us-west-2. Some customers experienced 429 errors and increased query latency during this time. We have identified the root cause and are deploying a fix. We are actively monitoring the situation and implementing additional safeguards to prevent this from recurring.

  2. resolved · Jan 28, 5:15 AM EST

    The issue has been resolved. We deployed a fix and confirmed that affected nodes have returned to normal operation.

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

Elevated 500s in region gcp-us-east4 due to transient unavailability of turbopuffer query nodes

minor
Started
Jan 28, 8:50 AM EST
Resolved
Jan 28, 11:41 AM EST
Duration
2h 51m

turbopuffer's updates (3)

  1. investigating · Jan 28, 8:50 AM EST

    Customers may notice a small number of their requests receiving a 500 response due to transient unavailability of turbopuffer query nodes. We have identified a probable cause and are moving to confirming and addressing it.

  2. monitoring · Jan 28, 9:36 AM EST

    We've identified the problem and taken action to stop customer impact.

  3. resolved · Jan 28, 11:41 AM EST

    Service has returned to normal. The cause has been identified and is being addressed.

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

Outage in aws-us-west-2

critical
Started
Jan 28, 10:30 PM EST
Resolved
Jan 28, 11:47 PM EST
Duration
1h 17m

turbopuffer's updates (3)

  1. investigating · Jan 28, 10:30 PM EST

    We are investigating reports of an outage in aws-us-west-2.

  2. monitoring · Jan 28, 10:36 PM EST

    We've identified the problem and rolled out a fix. We're closely monitoring the situation.

  3. resolved · Jan 28, 11:47 PM EST

    Service has been fully restored. We'll be sharing a full RCA with affected customers as soon as possible.

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.