- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-1
- Down Index
- 35of 100
What to do
Check whether you use Turso in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 48m it lasted.
Anything that failed between 2026-08-04 22:18 UTC and 2026-08-04 23:06 UTC may need a replay.Subscribe to Turso's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=turso works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Turso 2
- update
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
provider
- 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
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e4c820689a
Is Turso still down?
No, this incident was resolved 2026-08-04 23:06 UTC. For Turso's live state, see https://down.guide/turso.
How long did it last?
48m, from 2026-08-04 22:18 UTC to 2026-08-04 23:06 UTC, by the times Turso posted.
What was affected?
Turso named in us, us-east-1.
What caused it?
Turso hasn't published a root cause. If it does, it shows here.
Where does this come from?
Turso's official status page, https://status.turso.tech, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.