t
Outage recap · turbopuffer

turbopuffer outage — October 20, 2025

On October 20, 2025, turbopuffer had 3 reported incidents on turbopuffer's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Outage in aws us-east-1

major
Started
Oct 20, 3:58 AM EDT
Resolved
Oct 20, 7:18 PM EDT
Duration
15h 19m

turbopuffer's updates (5)

  1. investigating · Oct 20, 3:58 AM EDT

    [AWS us-east-1 is experiencing a major outage and many services are affected. ](https://health.aws.amazon.com/health/status) turbopuffer clients in aws-us-east-1 will see elevated error rate and latencies during this outage. We're looking at mitigating the impact.

  2. monitoring · Oct 20, 4:38 AM EDT

    We have deployed mitigations and are monitoring the situation.

  3. monitoring · Oct 20, 10:32 AM EDT

    AWS is experiencing a major disruption in region us-east-1 impacting multiple services (<https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A>). This caused turbopuffer to become unavailable in that region starting at 7:50 UTC. We've rolled out mitigations which resulted in a full recovery of turbopuffer at 8:20 UTC (despite the ongoing AWS outage). An existing mitigation to guard against EC2 instance launch issues has prevented the long-running EC2 degradation from further affecting turbopuffer availability. The AWS incident is ongoing. We will continue monitoring the cluster's health.

  4. monitoring · Oct 20, 5:39 PM EDT

    The turbopuffer service remains healthy in the aws-us-east-1 region. We continue to closely monitor the situation while AWS continues to report service disruption in the region.

  5. resolved · Oct 20, 7:18 PM EDT

    AWS has reported that the upstream incident is resolved.

Updates are turbopuffer's own words from its status page (status: resolved); we never add an inferred cause.

Degraded performance in gcp-us-east4

minor
Started
Oct 20, 5:55 AM EDT
Resolved
Oct 20, 1:22 PM EDT
Duration
7h 27m

turbopuffer's updates (3)

  1. investigating · Oct 20, 5:55 AM EDT

    we're currently observing degraded performance in gcp-us-east4 leading to elevated rates of 408s and 429s. Our team is currently investigating.

  2. monitoring · Oct 20, 6:12 AM EDT

    We have observed an increase in timeouts and a slow down in indexing starting at 9:38 UTC. The service has returned to normal at 10:00 UTC. We are monitoring and investigating the root cause.

  3. resolved · Oct 20, 1:22 PM EDT

    Service is stable. We are continuing to investigate the root cause with high priority.

Updates are turbopuffer's own words from its status page (status: resolved); we never add an inferred cause.

Partial dashboard outage

major
Started
Oct 20, 3:42 PM EDT
Resolved
Oct 20, 10:31 PM EDT
Duration
6h 49m

turbopuffer's updates (3)

  1. identified · Oct 20, 2:32 PM EDT

    Some users are reporting issues accessing the turbopuffer dashboard due to a partial outage with our authentication provider: <https://status.workos.com/incidents/rdz189wnjhyn> turbopuffer APIs are unaffected.

  2. monitoring · Oct 20, 3:52 PM EDT

    Dashboard error rates have subsided. We continue to monitor the situation while we wait for confirmation from our authentication provider that the incident has resolved.

  3. resolved · Oct 20, 10:31 PM EDT

    The upstream incident is resolved.

Updates are turbopuffer's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with turbopuffer. This recap summarizes incidents published on turbopuffer's official status page.