Is Turso Down?

No — Turso is up

Turso's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 146 ms

Right now

We could not read Turso's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

turso.tech from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 146 ms
Checked: 3 hours ago

By region

Amsterdam reachable, 131 ms
Dallas reachable, 200 ms
Frankfurt reachable, 85 ms
Newark reachable, 120 ms
Paris reachable, 131 ms
Stockholm reachable, 102 ms
São Paulo reachable, 169 ms
Toronto reachable, 231 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	31 ms	5 ms	17 ms	114 ms
Dallas	57 ms	1 ms	53 ms	174 ms
Frankfurt	29 ms	3 ms	7 ms	77 ms
Newark	20 ms	9 ms	13 ms	93 ms
Paris	16 ms	9 ms	16 ms	101 ms
Stockholm	36 ms	1 ms	9 ms	96 ms
São Paulo	112 ms	2 ms	5 ms	165 ms
Toronto	50 ms	18 ms	28 ms	193 ms

We check that turso.tech loads, not every feature behind it. Test it yourself

History

Turso website availability

Measured by FlareWarden · turso.tech

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 155ms

Last 30 days

68-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of turso.tech from multiple regions every 6 hours. Turso's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 68 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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.

Test it yourself

Related services

Turso outage FAQ

My app still reads data but writes are failing. Is Turso down?

Quite possibly, for your region. Applications using embedded replicas keep serving reads from the local copy when the remote primary is unreachable, so the app appears healthy while writes fail. That is the dangerous shape of a Turso incident, because monitoring built on read queries stays green. Check writes explicitly and find your region's row on the status page.

Turso says operational but my database is unreachable. Why?

Look at the specific region rather than the summary. Turso reports AWS us-east-1, us-east-2, us-west-2, eu-west-1, ap-northeast-1 and ap-south-1 separately, plus individual Fly locations, so a database in one region can be affected while everything else is fine. Confirm which region hosts the database before concluding the status page is wrong.

Does a Turso outage affect the dashboard as well as my databases?

Not necessarily. The status page tracks Turso Website and Turso API as components distinct from the regional data plane, so the dashboard can be unavailable while databases serve normally, or the reverse. If you cannot reach the dashboard, test a query against the database directly before assuming your data is affected.

Turso runs on Fly infrastructure. Does a Fly outage take it down?

It can affect the locations that depend on it, and Turso makes this visible by listing its Fly locations as their own components alongside the AWS regions. If your database sits in one of those locations and it is the affected row, the underlying cause may be upstream of Turso, which usually means waiting rather than reconfiguring.

How do I get notified about Turso incidents?

status.turso.tech offers status updates by email, RSS, JSON, webhook and Slack, and lets you subscribe to specific components rather than everything. Subscribing to just the region your databases run in is the practical choice, since most incidents are regional and a global subscription produces alerts that do not apply to you.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Turso itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Turso goes down

We check Turso every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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

Free plan available No credit card required