30 days uptime
99.903%
29 of 30 days clean · 41m total downtime
All windows
Last resolved incident
4 days ago · lasted 19m · None
5/22/2026, 6:00:00 AM · resolved 5/22/2026, 6:19:00 AM · Resolved
5/8/2026, 4:30:00 AM · resolved 5/8/2026, 6:30:00 AM · Resolved
2/19/2026, 4:47:00 PM · resolved 2/19/2026, 4:47:00 PM · Resolved
1/6/2026, 5:25:00 AM · resolved 1/6/2026, 8:09:00 PM · Resolved
65signals across 1 source
synthetic_probe 65
Official status page: https://status.turso.tech (opens in new tab)
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 4 days ago and lasted 19 minutes (an incident).
Looking for the live "is Turso down" view? See the Turso Status page.
Turso's 30-day customer-perceived uptime is 99.903%. 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.