- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 45of 100
What to do
Check whether your product depends on Turso. 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 14h 44m it lasted.
Anything that failed between 2026-01-06 05:25 UTC and 2026-01-06 20:09 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 3
- update
Fly.io is having major downtime with their control plane (https://status.flyio.net/). This is affecting CRUD operations on all fly.io databases until their situation is resolved.
provider
- update
Fly.io seems to have mostly recovered, but it has not fully stabilized.
provider
- resolved
Fly.io incident has been resolved: https://status.flyio.net/incidents/mcspt3m8w89t
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-740a936752
Is Turso still down?
No, this incident was resolved 2026-01-06 20:09 UTC. For Turso's live state, see https://down.guide/turso.
How long did it last?
14h 44m, from 2026-01-06 05:25 UTC to 2026-01-06 20:09 UTC, by the times Turso posted.
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.