Is Turbopuffer down?
Last checked 5m agoNo incidents right now.
Turbopuffer is operational right now. Last checked 5m ago; the most recent incident resolved 16d ago.
Real-time Turbopuffer status, recent outages, and incident history — pulled directly from Turbopuffer's official status page at https://status.turbopuffer.com every 5 minutes. Pingoru tracks 16 Turbopuffer services and has captured 3 incidents in the last 90 days (99.51% uptime). Get email, Slack, Discord, or webhook alerts the moment Turbopuffer reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Dashboard
Timeline · 4 updates
- 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)
- 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)
- 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)
- 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)
Latest: 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 dat…
-
- 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)
Latest: 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. …
-
- 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)
Latest: Status: Resolved Our deploy has rolled out and affected namespaces have recovered. Affected components aws-us-west-2 (Operational)
-
- Errors when accessing dashboard ResolvedStarted Jul 16, 2026, 10:49 AM UTC · Resolved Jul 16, 2026, 10:49 AM UTC · —
- Started May 28, 2026, 06:30 PM UTC · Resolved May 28, 2026, 06:30 PM UTC · —
- partial outage in aws-us-west-2 ResolvedStarted May 20, 2026, 04:19 PM UTC · Resolved May 20, 2026, 04:19 PM UTC · —