Is Turbopuffer down?

Last checked 7m ago
Current status
Turbopuffer is up

No incidents right now.

Official status page: https://status.turbopuffer.com · Polled every 5 minutes · 16 components tracked

Turbopuffer is operational right now. Last checked 7m 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 12 incidents in the last 90 days (98.99% uptime). Get email, Slack, Discord, or webhook alerts the moment Turbopuffer reports a new incident — free for 5 monitors, no credit card.

Users who monitor Turbopuffer also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Turbopuffer uptime 98.99% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 28, 2026, 06:30 PM UTC · Resolved May 28, 2026, 06:30 PM UTC
    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. …

  2. Resolved
    Started May 20, 2026, 04:19 PM UTC · Resolved May 20, 2026, 04:19 PM UTC
    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)

  3. Resolved
    Started Apr 20, 2026, 05:32 PM UTC · Resolved Apr 20, 2026, 05:32 PM UTC
    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)

    Latest: 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 regio…

  4. Resolved 5h 9m
    Started Apr 20, 2026, 12:22 PM UTC · Resolved Apr 20, 2026, 05:32 PM UTC
  5. Resolved
    Started Apr 02, 2026, 01:10 PM UTC · Resolved Apr 02, 2026, 01:10 PM UTC
    Dashboard
    Timeline · 2 updates
    • investigating · Apr 02, 2026, 12:14 PM UTC

      Status: Investigating We've confirmed reports of dashboard errors and our team is investigating. Affected components Dashboard (Full outage)

    • resolved · Apr 02, 2026, 01:10 PM UTC

      Status: Resolved We were impacted by an issue with one of our providers: https://www.vercel-status.com/incidents/5r9bp5y8rql2, which we were able to resolve. We will continue to monitor for regressions. Affected components Dashboard (Operational)

    Latest: Status: Resolved We were impacted by an issue with one of our providers: https://www.vercel-status.com/incidents/5r9bp5y8rql2, which we were able to resolve. We will continue to mo…

See the full Turbopuffer outage history

7 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Turbopuffer outage history →

Or sign up free to get alerts when Turbopuffer breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 12 incidents View full outage history →