Turbopuffer incident

Increased Request Latency and 429s in GCP us-east4

Minor Resolved View vendor source →
Started
Mar 17, 2026, 10:48 AM UTC
Resolved
Mar 17, 2026, 10:48 AM UTC
Duration
Detected by Pingoru
Mar 17, 2026, 10:48 AM UTC

Affected components

gcp-us-east4

Update timeline

  1. investigating Mar 17, 2026, 09:53 AM UTC

    Status: Investigating We are looking into an issue causing increased latency and 429s in us-east4. Affected components gcp-us-east4 (Degraded performance)

  2. monitoring Mar 17, 2026, 10:28 AM UTC

    Status: Monitoring Latencies have returned to normal and 429s have fully recovered. The issue was related to transient failures in the underlying infrastructure. Our engineers have applied mitigations, and we are continuing to monitor. Affected components gcp-us-east4 (Partial outage)

  3. resolved Mar 17, 2026, 10:48 AM UTC

    Status: Resolved The region is stable and has fully recovered. We will continue to monitor. Affected components gcp-us-east4 (Operational)

Looking to track Turbopuffer downtime and outages?

Pingoru polls Turbopuffer's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Turbopuffer reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Turbopuffer alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Turbopuffer for free

5 free monitors · No credit card required