Turbopuffer Outage History

Turbopuffer had 23 outages in the last 2 years totaling 61h 32m of downtime — averaging 0.9 incidents per month.

There were 23 Turbopuffer outages since July 26, 2025 totaling 61h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.turbopuffer.com

Minor May 28, 2026

Elevated 500 rate on delete_by_filter writes, filtered queries

Detected by Pingoru: May 28, 2026, 06:30 PM UTC
Resolved: May 28, 2026, 06:30 PM UTC
Duration: —

Affected: aws-us-east-1aws-us-east-2gcp-us-central1gcp-us-east4gcp-asia-southeast1

Timeline · 2 updates

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)

Read the full incident report →

Minor May 20, 2026

partial outage in aws-us-west-2

Detected by Pingoru: May 20, 2026, 04:19 PM UTC
Resolved: May 20, 2026, 04:19 PM UTC
Duration: —

Affected: aws-us-west-2

Timeline · 2 updates

identified May 20, 2026, 03:42 PM UTC

Status: Identified Our team has identified an issue with a deploy in aws-us-west-2, we are deploying a fix. Affected components aws-us-west-2 (Degraded performance)
resolved May 20, 2026, 04:19 PM UTC

Status: Resolved Our deploy has rolled out and affected namespaces have recovered. Affected components aws-us-west-2 (Operational)

Read the full incident report →

Minor April 20, 2026

Errors when accessing dashboard

Detected by Pingoru: Apr 20, 2026, 05:32 PM UTC
Resolved: Apr 20, 2026, 05:32 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 24, 2026

Elevated 408 and 429s

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

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)

Read the full incident report →

Minor March 17, 2026

Increased Request Latency and 429s in GCP us-east4

Detected by Pingoru: Mar 17, 2026, 10:48 AM UTC
Resolved: Mar 17, 2026, 10:48 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 16, 2026

Elevated 500s in region gcp-us-west1

Detected by Pingoru: Mar 16, 2026, 09:39 AM UTC
Resolved: Mar 16, 2026, 09:39 AM UTC
Duration: —

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)

Read the full incident report →

Minor January 29, 2026

Outage in aws-us-west-2

Detected by Pingoru: Jan 29, 2026, 04:47 AM UTC
Resolved: Jan 29, 2026, 04:47 AM UTC
Duration: —

Affected: aws-us-west-2

Timeline · 3 updates

investigating Jan 29, 2026, 03:30 AM UTC

Status: Investigating We are investigating reports of an outage in aws-us-west-2.
monitoring Jan 29, 2026, 03:36 AM UTC

Status: Monitoring We've identified the problem and rolled out a fix. We're closely monitoring the situation. Affected components aws-us-west-2 (Degraded performance)
resolved Jan 29, 2026, 04:47 AM UTC

Status: Resolved Service has been fully restored. We'll be sharing a full RCA with affected customers as soon as possible. Affected components aws-us-west-2 (Operational)

Read the full incident report →

Minor January 28, 2026

Elevated 500s in region gcp-us-east4 due to transient unavailability of turbopuffer query nodes

Detected by Pingoru: Jan 28, 2026, 04:41 PM UTC
Resolved: Jan 28, 2026, 04:41 PM UTC
Duration: —

Affected: gcp-us-east4

Timeline · 3 updates

investigating Jan 28, 2026, 01:50 PM UTC

Status: Investigating 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. Affected components gcp-us-east4 (Partial outage)
monitoring Jan 28, 2026, 02:36 PM UTC

Status: Monitoring We've identified the problem and taken action to stop customer impact. Affected components gcp-us-east4 (Partial outage)
resolved Jan 28, 2026, 04:41 PM UTC

Status: Resolved Service has returned to normal. The cause has been identified and is being addressed. Affected components gcp-us-east4 (Operational)

Read the full incident report →

Minor January 28, 2026

aws-us-west-2: Increased 429's on a subset of nodes

Detected by Pingoru: Jan 28, 2026, 10:15 AM UTC
Resolved: Jan 28, 2026, 10:15 AM UTC
Duration: —

Affected: aws-us-west-2

Timeline · 2 updates

monitoring Jan 28, 2026, 10:02 AM UTC

Status: Monitoring We identified an issue causing high CPU utilization on a subset of query nodes in us-west-2. Some customers experienced 429 errors and increased query latency during this time. We have identified the root cause and are deploying a fix. We are actively monitoring the situation and implementing additional safeguards to prevent this from recurring. Affected components aws-us-west-2 (Degraded performance)
resolved Jan 28, 2026, 10:15 AM UTC

Status: Resolved The issue has been resolved. We deployed a fix and confirmed that affected nodes have returned to normal operation. Affected components aws-us-west-2 (Operational)

Read the full incident report →

Minor January 28, 2026

Degraded performance in aws-us-west-2

Detected by Pingoru: Jan 28, 2026, 04:12 AM UTC
Resolved: Jan 28, 2026, 04:12 AM UTC
Duration: —

Affected: aws-us-west-2

Timeline · 4 updates

investigating Jan 28, 2026, 02:39 AM UTC

Status: Investigating We're investigating reports of degraded performance in aws-us-west-2. Affected components aws-us-west-2 (Degraded performance)
identified Jan 28, 2026, 03:09 AM UTC

Status: Identified We've identified a pathological performance issue when running on ARM hardware. We've shifted the region to run entirely on Intel hardware. Affected components aws-us-west-2 (Degraded performance)
monitoring Jan 28, 2026, 03:31 AM UTC

Status: Monitoring The region has fully transitioned back to Intel hardware and API response latency has returned to normal. We're monitoring to ensure that latencies remain stable. Affected components aws-us-west-2 (Operational)
resolved Jan 28, 2026, 04:12 AM UTC

Status: Resolved Latencies have remained stable. Affected components aws-us-west-2 (Operational)