Turbopuffer Outage History

Turbopuffer is up right now

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

There were 23 Turbopuffer outages since October 9, 2025 totaling 79h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.turbopuffer.com

Minor October 8, 2026

Elevated rate of 5xx in gcp-us-central1

Detected by Pingoru
Oct 08, 2026, 05:45 PM UTC
Resolved
Oct 09, 2026, 01:11 AM UTC
Duration
7h 26m
Affected: gcp-us-central1
Timeline · 4 updates
  1. investigating Oct 08, 2026, 05:45 PM UTC

    Status: Investigating Some namespaces are experiencing an elevated rate of 5xx errors. We have identified the issue and are working to restore full service. Affected components gcp-us-central1 (Partial outage)

  2. identified Oct 08, 2026, 06:27 PM UTC

    Status: Identified Some write operations are intermittently failing due to an ongoing incident with Google Cloud Storage: https://status.cloud.google.com/incidents/mSFVt6PiP557bjRyYsut. Affected components gcp-us-central1 (Partial outage)

  3. monitoring Oct 08, 2026, 06:50 PM UTC

    Status: Monitoring Error rates have recovered as Google rolls out a fix to Google Cloud Storage. We will continue monitoring until the upstream incident is resolved. Affected components gcp-us-central1 (Partial outage)

  4. resolved Oct 09, 2026, 01:11 AM UTC

    Status: Resolved The issue upstream in Google Cloud Storage is resolved and us-central1 operations have returned to normal. Affected components gcp-us-central1 (Operational)

Read the full incident report →

Minor September 5, 2026

Dashboard outage

Detected by Pingoru
Sep 05, 2026, 06:40 PM UTC
Resolved
Sep 05, 2026, 06:52 PM UTC
Duration
12m
Affected: Dashboard
Timeline · 2 updates
  1. investigating Sep 05, 2026, 06:40 PM UTC

    Status: Investigating The turbopuffer dashboard is currently experiencing an outage. turbopuffer regions are fully available. Writes and queries are not affected. Affected components Dashboard (Full outage)

  2. resolved Sep 05, 2026, 06:52 PM UTC

    Status: Resolved From 7:21-7:41 UTC, the turbopuffer dashboard was unavailable due to an issue with our backing datastore. This issue has been resolved and dashboard access has been restored. Affected components Dashboard (Operational)

Read the full incident report →

Minor August 27, 2026

Outage in gcp-us-southeast1

Detected by Pingoru
Aug 27, 2026, 08:37 PM UTC
Resolved
Aug 27, 2026, 10:15 PM UTC
Duration
1h 37m
Affected: gcp-asia-southeast1
Timeline · 3 updates
  1. investigating Aug 27, 2026, 08:37 PM UTC

    Status: Investigating Full outage identified in gcp-southeast1 Affected components gcp-asia-southeast1 (Full outage)

  2. monitoring Aug 27, 2026, 09:08 PM UTC

    Status: Monitoring We’ve identified the problem and rolled out a fix. We’re closely monitoring the situation. Affected components gcp-asia-southeast1 (Operational)

  3. resolved Aug 27, 2026, 10:15 PM UTC

    Status: Resolved Service has been fully restored. Affected components gcp-asia-southeast1 (Operational)

Read the full incident report →

Minor July 16, 2026

Errors when accessing dashboard

Detected by Pingoru
Jul 16, 2026, 09:42 AM UTC
Resolved
Jul 16, 2026, 10:49 AM UTC
Duration
1h 6m
Affected: Dashboard
Timeline · 4 updates
  1. investigating Jul 16, 2026, 09:42 AM UTC

    Status: Investigating We're aware of issues affecting some customers who are logging into the dashboard. We're investigating and will provide an update shortly. Note that the database is not affected - this issue is limited to the dashboard. Affected components Dashboard (Partial outage)

  2. identified Jul 16, 2026, 10:05 AM UTC

    Status: Identified Dashboard logins (Google, SSO, and email) are intermittently failing due to an ongoing incident at our authentication provider: https://status.workos.com/incidents/b52fkqjzcl20. We're monitoring and will update here. Affected components Dashboard (Partial outage)

  3. monitoring Jul 16, 2026, 10:14 AM UTC

    Status: Monitoring Logins are succeeding again as of 10:08 UTC. Our authentication provider is still working through their incident, so some logins may be slower than usual. We'll continue monitoring until it's fully resolved. Affected components Dashboard (Partial outage)

  4. resolved Jul 16, 2026, 10:49 AM UTC

    Status: Resolved Our authentication provider has resolved the incident on their end, and dashboard logins have been fully operational since 10:08 UTC. Existing sessions and the database were unaffected throughout. Affected components Dashboard (Operational)

Read the full incident report →

Minor May 28, 2026

Elevated 500 rate on delete_by_filter writes, filtered queries

Detected by Pingoru
May 28, 2026, 05:55 PM UTC
Resolved
May 28, 2026, 06:30 PM UTC
Duration
35m
Affected: aws-us-east-1aws-us-east-2gcp-us-central1gcp-us-east4gcp-asia-southeast1
Timeline · 2 updates
  1. 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)

  2. 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, 03:42 PM UTC
Resolved
May 20, 2026, 04:19 PM UTC
Duration
37m
Affected: aws-us-west-2
Timeline · 2 updates
  1. 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)

  2. 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 March 24, 2026

Elevated 408 and 429s

Detected by Pingoru
Mar 24, 2026, 09:50 AM UTC
Resolved
Mar 24, 2026, 10:18 AM UTC
Duration
28m
Affected: gcp-us-east4
Timeline · 3 updates
  1. 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)

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

  3. 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 16, 2026

Elevated 500s in region gcp-us-west1

Detected by Pingoru
Mar 16, 2026, 08:55 AM UTC
Resolved
Mar 16, 2026, 09:39 AM UTC
Duration
44m
Affected: gcp-us-west1
Timeline · 3 updates
  1. 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)

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

  3. 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, 03:30 AM UTC
Resolved
Jan 29, 2026, 04:47 AM UTC
Duration
1h 17m
Affected: aws-us-west-2
Timeline · 3 updates
  1. investigating Jan 29, 2026, 03:30 AM UTC

    Status: Investigating We are investigating reports of an outage in aws-us-west-2.

  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)

  3. 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, 01:50 PM UTC
Resolved
Jan 28, 2026, 04:41 PM UTC
Duration
2h 50m
Affected: gcp-us-east4
Timeline · 3 updates
  1. 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)

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

  3. 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 →