Turbopuffer incident

Elevated 408 and 429s

Minor Resolved View vendor source →

Turbopuffer experienced a minor incident on March 24, 2026 affecting gcp-us-east4, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 24, 2026, 10:18 AM UTC
Resolved
Mar 24, 2026, 10:18 AM UTC
Duration
Detected by Pingoru
Mar 24, 2026, 10:18 AM UTC

Affected components

gcp-us-east4

Update timeline

  1. investigating Mar 24, 2026, 09:50 AM UTC

    Status: Investigating The gcp-us-east4 cluster is experiencing elevated rates of 408 and 429s affecting both reads and writes affecting approximately 4% of traffic. Our team is investigating. Affected components gcp-us-east4 (Degraded performance)

  2. monitoring Mar 24, 2026, 10:11 AM UTC

    Status: Monitoring Our team has taken remedial action and is observing recovery, we will continue to monitor. Affected components gcp-us-east4 (Degraded performance)

  3. resolved Mar 24, 2026, 10:18 AM UTC

    Status: Resolved We've observed a complete recovery of traffic. Affected components gcp-us-east4 (Operational)