Service comparison
CockroachDB vs. Turso
CockroachDB vs. Turso — reliability, API availability, and incident frequency head-to-head.
Last 90 days · 3 incidents total · Data via Pulsetic monitoring
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Service comparison
CockroachDB vs. Turso — reliability, API availability, and incident frequency head-to-head.
Last 90 days · 3 incidents total · Data via Pulsetic monitoring
Head-to-head
90-day uptime
99.03%
Incidents (90d)
3
2 major · 1 minor
Median resolution
39m
Longest outage
19h 40m
Turso
turso.tech
90-day uptime
100.00%
Incidents (90d)
0
0 major · 0 minor
Median resolution
—
Longest outage
—
Uptime over time
| Window | CockroachDB | Turso | Δ |
|---|---|---|---|
| Last 24 hours |
|
|
-2.50 pp |
| Last 7 days |
|
|
-0.36 pp |
| Last 30 days |
|
|
-0.08 pp |
| Last 90 days |
|
|
-0.97 pp |
Δ is percentage-point difference (CockroachDB minus Turso). Higher is better.
Incidents 90-day
CockroachDB
3 total
Median resolution
39m
Longest outage
19h 40m
Turso
0 total
Median resolution
—
Longest outage
—
Recent activity
CockroachDB
Unable to accept invites
36m
Degraded performance in one AWS us-east-1 availability zone
19h 40m
Cloud Console Social Login Auth Unavailable
39m
Cluster unavailability and degraded cluster operations in AWS me-central...
10d 4h 39m
Connectivity issues to Standard and Basic clusters on AWS
12h 16m
Turso
No incidents recorded in the last 90 days.
Bottom line
Turso winsCockroachDB posted 99.03% vs. 100.00% for Turso (Δ -0.97 pp). Incidents: 3 vs. 0 (+3).
Also compare
Pulsetic watches endpoints from 15+ global regions and alerts you before users notice.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT