Turbopuffer incident

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

Resolved after 13 minutes, affecting aws-us-west-2, on January 28, 2026.

resolved Jan 28, 2026, 10:15 AM UTC

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

Started
Jan 28, 2026, 10:02 AM UTC
Resolved
Jan 28, 2026, 10:15 AM UTC
Duration
13m
Detected by Pingoru
Jan 28, 2026, 10:02 AM UTC

Affected components

aws-us-west-2

Update timeline

  1. monitoring Jan 28, 2026, 10:02 AM UTC

    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, 2026, 10:15 AM UTC

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

Your product runs on more than Turbopuffer

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →