Turbopuffer incident

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

Minor Resolved View vendor source →

Turbopuffer experienced a minor incident on January 28, 2026 affecting aws-us-west-2, lasting —. The incident has been resolved; the full update timeline is below.

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

Affected components

aws-us-west-2

Update timeline

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

    Status: Monitoring 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. Affected components aws-us-west-2 (Degraded performance)

  2. resolved Jan 28, 2026, 10:15 AM UTC

    Status: Resolved The issue has been resolved. We deployed a fix and confirmed that affected nodes have returned to normal operation. Affected components aws-us-west-2 (Operational)