Reliability
Reliability
CheckUpstream has measured Turso at 39.854% uptime over the last 90 days and 62.442% over the last 12 months. 14 incidents were recorded in the past 12 months; the most recent resolved 344 days ago after 318 days. Status signals are polled from Turso's official Better Stack status page, alongside independent probes and community reports.
180 days uptime
69.927%
25 of 180 days clean · 54d 3h total downtime
Fewer incidents in the last 30 days than 48% of 234 tracked services.
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 →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
Feb 19, 16:47 UTC · resolved in 133d 4h · Resolved
157signals across 2 sources
Synthetic probes 156 · active_probe 1
Worst window: 53.57% of 280 requests failing at 2026-07-27 04:14 UTC.
| Day | Requests | Failed | Error rate | Reporting orgs |
|---|---|---|---|---|
| 2026-07-28 | 782,499 | 83 | 0.01% | 1 |
| 2026-07-27 | 1,746,952 | 4,213 | 0.24% | 1 |
| 2026-07-26 | 1,600,032 | 1,150 | 0.07% | 1 |
| 2026-07-25 | 1,398,553 | 0 | 0.00% | 1 |
Live status pill for Turso. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=turso"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/turso" style="border:0;width:260px;height:44px" loading="lazy" title="Turso status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/turso)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/turso/badge.svgTurso 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 344 days ago and lasted 318d 5h (a partial outage).
Looking for the live "is Turso down" view? See the Turso Live status page.
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
| 2026-07-24 | 1,558,319 | 15 | 0.00% | 1 |
| 2026-07-23 | 1,355,127 | 0 | 0.00% | 1 |
| 2026-07-22 | 1,216,164 | 0 | 0.00% | 1 |
| 2026-07-21 | 383,876 | 0 | 0.00% | 1 |
Turso's 30-day customer-perceived uptime is 69.927%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
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.