Turso: Elevated errors of 502 on database queries
Affected components: Turso APIAWS us-east-1 (N. Virginia)
Timeline of updates
- 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
- 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 were affected and we deeply apologize for the disruption to those affected
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a9cd2c14283de281…
Impact, status and times are the vendor’s own, as last archived.
Cite this
Status incident (vendor impact label: minor) posted by Turso, started 2026-08-04 22:18 UTC, resolved after 48 min, 2 update(s).
- Title
- Elevated errors of 502 on database queries
- Vendor
- Turso
- Date
- URL
- https://rewindex.com/company/turso/incidents/996229
Turso profileRecent Turso incidentsAll outages on August 4, 2026Turso in August 2026MarkdownJSON