- Level
- confirmed
- Worst impact
- Degraded
- Components
- AWS us-west-2 (Oregon)
- Regions
- us, us-west-2
What to do
Check whether you use Turso AWS us-west-2 (Oregon) in us, us-west-2. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-11-11 07:12 UTC and 2026-11-11 07:12 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 1
- resolved
In us-west-2, there was a 24-minute period of elevated latencies and error rates for database, group and token creations as well as some control plane read operations. The issue has been resolved.
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-02961b2483
Is Turso still down?
No, this incident was resolved 2026-11-11 07:12 UTC. For Turso's live state, see https://down.guide/providers/turso.
How long did it last?
0m, from 2026-11-11 07:12 UTC to 2026-11-11 07:12 UTC, by the times Turso posted.
What was affected?
Turso named AWS us-west-2 (Oregon) in us, us-west-2.
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.