Turbopuffer Outage History

Turbopuffer is up right now

Pingoru has recorded 36 incidents for Turbopuffer: 31 in the last 12 months and 4 in the last 90 days.

Source: status.turbopuffer.com

36incidents recorded

31last 12 months

4last 90 days

81 minutestypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Turbopuffer in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Month	Incidents	Hours with an open incident
April 2026	4	6 of 720 (1%)
May 2026	2	1 of 744 (0%)
June 2026	0	0 of 720 (0%)
July 2026	1	1 of 744 (0%)
August 2026	1	2 of 744 (0%)
September 2026	2	1 of 720 (0%)
October 2026	1	7 of 523 (1%)

Incidents, newest first

Minor October 8, 2026 Elevated rate of 5xx in gcp-us-central1 7h 26m gcp-us-central1

Started Oct 08, 2026, 05:45 PM UTC· resolved Oct 09, 2026, 01:11 AM UTC

investigating Oct 08, 2026, 05:45 PM UTC

Some namespaces are experiencing an elevated rate of 5xx errors. We have identified the issue and are working to restore full service.
identified Oct 08, 2026, 06:27 PM UTC

Some write operations are intermittently failing due to an ongoing incident with Google Cloud Storage: https://status.cloud.google.com/incidents/mSFVt6PiP557bjRyYsut.
monitoring Oct 08, 2026, 06:50 PM UTC

Error rates have recovered as Google rolls out a fix to Google Cloud Storage. We will continue monitoring until the upstream incident is resolved.
resolved Oct 09, 2026, 01:11 AM UTC

The issue upstream in Google Cloud Storage is resolved and us-central1 operations have returned to normal.

Read the full incident report →

Minor September 5, 2026 Dashboard outage 12m Dashboard

Started Sep 05, 2026, 06:40 PM UTC· resolved Sep 05, 2026, 06:52 PM UTC

investigating Sep 05, 2026, 06:40 PM UTC

The turbopuffer dashboard is currently experiencing an outage. turbopuffer regions are fully available. Writes and queries are not affected.
resolved Sep 05, 2026, 06:52 PM UTC

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.

Read the full incident report →

Minor August 27, 2026 Outage in gcp-us-southeast1 1h 37m gcp-asia-southeast1

Started Aug 27, 2026, 08:37 PM UTC· resolved Aug 27, 2026, 10:15 PM UTC

investigating Aug 27, 2026, 08:37 PM UTC

Full outage identified in gcp-southeast1
monitoring Aug 27, 2026, 09:08 PM UTC

We’ve identified the problem and rolled out a fix. We’re closely monitoring the situation.
resolved Aug 27, 2026, 10:15 PM UTC

Service has been fully restored.

Read the full incident report →

Minor July 16, 2026 Errors when accessing dashboard 1h 6m Dashboard

Started Jul 16, 2026, 09:42 AM UTC· resolved Jul 16, 2026, 10:49 AM UTC

investigating Jul 16, 2026, 09:42 AM UTC

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.
identified Jul 16, 2026, 10:05 AM UTC

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.
monitoring Jul 16, 2026, 10:14 AM UTC

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.
resolved Jul 16, 2026, 10:49 AM UTC

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.

Read the full incident report →

Minor May 28, 2026 Elevated 500 rate on delete_by_filter writes, filtered queries 35m aws-us-east-1, aws-us-east-2, gcp-us-central1, gcp-us-east4 and 1 more

Started May 28, 2026, 05:55 PM UTC· resolved May 28, 2026, 06:30 PM UTC

monitoring May 28, 2026, 05:55 PM UTC

Investigating elevated 500 error rate on filtered queries, delete_by_filter operations.
resolved May 28, 2026, 06:30 PM UTC

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.

Read the full incident report →

Minor May 20, 2026 partial outage in aws-us-west-2 37m aws-us-west-2

Started May 20, 2026, 03:42 PM UTC· resolved May 20, 2026, 04:19 PM UTC

identified May 20, 2026, 03:42 PM UTC

Our team has identified an issue with a deploy in aws-us-west-2, we are deploying a fix.
resolved May 20, 2026, 04:19 PM UTC

Our deploy has rolled out and affected namespaces have recovered.

Read the full incident report →

Minor March 24, 2026 Elevated 408 and 429s 28m gcp-us-east4

Started Mar 24, 2026, 09:50 AM UTC· resolved Mar 24, 2026, 10:18 AM UTC

investigating Mar 24, 2026, 09:50 AM UTC

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.
monitoring Mar 24, 2026, 10:11 AM UTC

Our team has taken remedial action and is observing recovery, we will continue to monitor.
resolved Mar 24, 2026, 10:18 AM UTC

We've observed a complete recovery of traffic.

Read the full incident report →

Major March 17, 2026 Increased Request Latency and 429s in GCP us-east4 50m

Started Mar 17, 2026, 09:58 AM UTC· resolved Mar 17, 2026, 10:48 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 16, 2026 Elevated 500s in region gcp-us-west1 44m gcp-us-west1

Started Mar 16, 2026, 08:55 AM UTC· resolved Mar 16, 2026, 09:39 AM UTC

investigating Mar 16, 2026, 08:55 AM UTC

We are investigating an increase 500's in the region!
monitoring Mar 16, 2026, 09:12 AM UTC

A fix has been rolled out and 5xx errors in the region have reduced. We are continuing to monitor the situation!
resolved Mar 16, 2026, 09:39 AM UTC

The region has stabilized and returned to normal operation. We are continuing to monitor!

Read the full incident report →

Minor January 29, 2026 Outage in aws-us-west-2 1h 17m aws-us-west-2

Started Jan 29, 2026, 03:30 AM UTC· resolved Jan 29, 2026, 04:47 AM UTC

investigating Jan 29, 2026, 03:30 AM UTC

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

We've identified the problem and rolled out a fix. We're closely monitoring the situation.
resolved Jan 29, 2026, 04:47 AM UTC

Service has been fully restored. We'll be sharing a full RCA with affected customers as soon as possible.

Read the full incident report →

Minor January 28, 2026 Elevated 500s in region gcp-us-east4 due to transient unavailability of turbopuffer query nodes 2h 50m gcp-us-east4

Started Jan 28, 2026, 01:50 PM UTC· resolved Jan 28, 2026, 04:41 PM UTC

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.