CheckUpstream measured Turso at 100.000% availability across 2829 independent checks (global · api). 15 incidents were recorded in the past 12 months; the most recent resolved 27 days ago after 22 minutes. Status signals are polled from Turso's official Better Stack status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2829 · p95 493ms (30d)
Share of our own checks against Turso endpoints that returned Turso's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 1 incident · 29 of 30 days with none posted · 30m of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Turso
7d
100.000%
30d
99.930%
90d
99.977%
180d
69.915%
1y
67.588%
Downtime like this can be refundable
If you're a paying Turso customer, outages in these windows may count against Turso's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Turso entitlement →Does Turso actually matter to you?
A Turso outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 4, 22:18 UTC · resolved in 22m · Resolved
May 22, 06:09 UTC · resolved in 41d 14h · Resolved
May 22, 06:00 UTC · resolved in 41d 15h · Resolved
May 8, 04:30 UTC · resolved in 0m · Resolved
1signal across 1 source
Synthetic probes 1
All of these are CheckUpstream's own probes. Nobody else has reported Turso in this window, so nothing here is corroboration.
Live Turso status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/turso)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Turso is currently Operational. CheckUpstream tracks Turso in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Turso's last resolved incident started 27 days ago and lasted 22 minutes (a partial outage).
Looking for the live "is Turso down" view? See the Turso Live status page.
Feb 19, 16:47 UTC · resolved in 133d 4h · Resolved
Jan 6, 15:22 UTC · resolved in 4h 47m · Resolved
Jan 6, 05:25 UTC · resolved in 177d 15h · Resolved
Nov 11, 15:12 UTC · resolved in 233d 5h · Resolved
Oct 20, 15:08 UTC · resolved in 255d 5h · Resolved
Oct 20, 07:52 UTC · resolved in 255d 13h · Resolved
Aug 18, 15:34 UTC · resolved in 318d 5h · Resolved
Jul 11, 19:03 UTC · resolved in 356d 1h · Resolved
Turso's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Turso endpoints. It is the share of checks that returned the expected response, not a figure taken from Turso's status page.
Sign up to CheckUpstream and add Turso to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Turso's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.