- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-1
- Down Index
- 37of 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 2h it lasted.
Anything that failed between 2026-05-08 04:30 UTC and 2026-05-08 06:30 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
Some databases were affected by the incident with US-EAST-1 "thermal event". More details at: https://health.aws.amazon.com/health/status
provider
- resolved
AWS reports that service is restored. Affected databases had already been moved to new machines.
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-02b5d55551
Is Turso still down?
No, this incident was resolved 2026-05-08 06:30 UTC. For Turso's live state, see https://down.guide/turso.
How long did it last?
2h, from 2026-05-08 04:30 UTC to 2026-05-08 06:30 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.