">
sevanalysis

Turso

Infrastructure. Source: Turso status page.

History starts 2026-08-04 22:18 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.

Incidents, last 90 days
2+
Median duration
7h 57m
p95 duration
15h 7m
Naming an upstream provider
50%
With a postmortem on the status page
0%

What failed, last 90 days

A provider or third-party service this vendor depends on failed1
Orchestration, control plane, service discovery or load balancing failed1

Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.

Incidents per month

Hatched months are before the recorded history starts.

All recorded incidents

Degraded for Fly regions minor 2026-10-16 18:24 UTC 15h 7m

Affected: Global

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    Fly is rolling out host reboots platform wide and databases will become unavailable during the reboot. http://status.flyio.net/incidents/01M52RAWMVC0NKEBRDKC3VXT3K

  2. resolved

    The issue is resolved and databases on Fly are back to healthy status.

Excerpts are shortened. Read the full incident on Turso's status page.

Elevated errors of 502 on database queries minor 2026-08-04 22:18 UTC 48m

Affected: Turso API, AWS us-east-1 (N. Virginia)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. degraded

    The router component is experiencing a high number of 502. At the moment, we only see databases in us-east-1 affected but are monitoring the situation and working on a mitigation

  2. resolved

    We had identified and resolved the issue. The issue was a software issue that brought a particular multitenant server down, which then cascaded due to retries to a load issue in the routing layer increasing the blast radius of the incident. We estimate that around 30 customers...

Excerpts are shortened. Read the full incident on Turso's status page.