Turbopuffer incident
Elevated 500s in region gcp-us-east4 due to transient unavailability of turbopuffer query nodes
Minor Vendor's status page →
Resolved after 2 hours 50 minutes, affecting gcp-us-east4, on January 28, 2026.
Service has returned to normal. The cause has been identified and is being addressed.
Affected components
gcp-us-east4
Update timeline
- investigating Jan 28, 2026, 01:50 PM UTC
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.
- monitoring Jan 28, 2026, 02:36 PM UTC
We've identified the problem and taken action to stop customer impact.
- resolved Jan 28, 2026, 04:41 PM UTC
Service has returned to normal. The cause has been identified and is being addressed.
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.
Amazon Web Services