Turbopuffer Outage History

There were 4 Turbopuffer outages since March 16, 2026. Each is summarised below — incident details, duration, and resolution information.

Minor April 20, 2026

Errors when accessing dashboard

Affected: Dashboard

Timeline · 5 updates

investigating Apr 20, 2026, 12:22 PM UTC

Status: Investigating We've confirmed reports of dashboard errors and are actively investigating. Note that the database is not affected - this issue is limited to the dashboard. Affected components Dashboard (Full outage)
identified Apr 20, 2026, 01:39 PM UTC

Status: Identified This issue is currently affecting the dashboard and API key management. turbopuffer regions and namespaces are all operating normally, and existing API keys continue to authenticate as expected. The root cause is a dependency service that we use for metadata. We'll share an update as we make progress. Affected components Dashboard (Full outage)
monitoring Apr 20, 2026, 02:11 PM UTC

Status: Monitoring We're seeing recovery with traffic returning to normal. We're monitoring closely and will share another update shortly. Affected components Dashboard (Full outage)
monitoring Apr 20, 2026, 03:00 PM UTC

Status: Monitoring Traffic has returned to normal. We're monitoring closely! Affected components Dashboard (Operational)
resolved Apr 20, 2026, 05:32 PM UTC

Status: Resolved This incident is resolved. Dashboard access is working as usual. As noted earlier, this incident only affected the dashboard and had no impact on turbopuffer regions or namespaces! Affected components Dashboard (Operational)

Minor March 24, 2026

Affected: gcp-us-east4

Timeline · 3 updates

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)
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)
resolved Mar 24, 2026, 10:18 AM UTC

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

Minor March 17, 2026

Affected: gcp-us-east4

Timeline · 3 updates

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)
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)
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)

Minor March 16, 2026

Affected: gcp-us-west1

Timeline · 3 updates

investigating Mar 16, 2026, 08:55 AM UTC

Status: Investigating We are investigating an increase 500's in the region! Affected components gcp-us-west1 (Partial outage)
monitoring Mar 16, 2026, 09:12 AM UTC

Status: Monitoring A fix has been rolled out and 5xx errors in the region have reduced. We are continuing to monitor the situation! Affected components gcp-us-west1 (Partial outage)
resolved Mar 16, 2026, 09:39 AM UTC

Status: Resolved The region has stabilized and returned to normal operation. We are continuing to monitor! Affected components gcp-us-west1 (Operational)

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

5 free monitors · No credit card required