Is Turso Down?
Reachable from all 8 checked regions
Average response time: 157ms
Last checked · checks run every 6 hours
Official status page: https://status.turso.tech
Turso uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 43 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
43-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Turso does
Turso is a managed database platform built on libSQL, a fork of SQLite. It hosts databases close to the application, supports embedded replicas that sync against a remote primary, and exposes each database over its own HTTP and websocket endpoint. Teams use it for multi-tenant and edge workloads where every tenant or region gets a database of its own.
What an outage looks like
Applications see connection failures or timeouts against one database host rather than a total outage, because Turso reports each AWS region and each Fly location as its own component. Where embedded replicas are in use, reads keep being served from the local copy while writes to the remote primary fail, so an application can look healthy while quietly no longer persisting anything.
What to do about it
Check status.turso.tech and find the row for the region your database actually lives in rather than reading the global headline. Turso lists AWS us-east-1, us-east-2, us-west-2, eu-west-1, ap-northeast-1 and ap-south-1 individually, alongside its Fly locations and separate rows for the Turso Website and the Turso API. If you run embedded replicas, verify writes are landing instead of trusting local reads.
Is it down for everyone, or just you?
If this page says Turso is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Turso outage FAQ
My app still reads data but writes are failing. Is Turso down?
Turso says operational but my database is unreachable. Why?
Does a Turso outage affect the dashboard as well as my databases?
Turso runs on Fly infrastructure. Does a Fly outage take it down?
How do I get notified about Turso incidents?
How we measure this
- We request Turso's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Turso publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Turso goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring