Turbopuffer incident
Elevated 500 rate on delete_by_filter writes, filtered queries
Turbopuffer experienced a minor incident on May 28, 2026 affecting aws-us-east-1 and aws-us-east-2 and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring May 28, 2026, 05:55 PM UTC
Status: Monitoring Investigating elevated 500 error rate on filtered queries, delete_by_filter operations. Affected components gcp-us-central1 (Degraded performance) aws-us-east-2 (Degraded performance) aws-us-east-1 (Degraded performance) gcp-asia-southeast1 (Degraded performance) gcp-us-east4 (Degraded performance)
- resolved May 28, 2026, 06:30 PM UTC
Status: Resolved Starting at ~17:55 UTC, we experienced an elevated 500 rate affecting delete_by_filter, and filtered queries as a result of a recent change deployed to filtering. This change was reverted, and errors fully subsided by ~18:30 UTC. This incident affected approximately 38.2% of delete_by_filter requests in aws-us-east-1, and a small percentage of filtered queries in other regions. Affected components gcp-us-central1 (Operational) aws-us-east-2 (Operational) aws-us-east-1 (Operational) gcp-asia-southeast1 (Operational) gcp-us-east4 (Operational)