Coinbase vs Crypto.com: which API is more reliable?
Over the 60 days of a 90-day window up24 has measured so far, Crypto.com was more available — 99.98% against 99.99% of checks answered, and Coinbase was quicker — a typical p95 of 178ms against 327ms.
Both venues are probed by the same probes on the same schedule — 90-day window, one request every 5 seconds, percentiles over successful responses only and measured from Lauterbourg, FR. Neither exchange reports any of this; up24 measures it.
| MEASUREMENT | ||
|---|---|---|
Uptime · 90d | 99.98% | 99.99% |
REST checks behind it | 3,082,890 | 2,980,914 |
Days measured | 62 of 90 | 60 of 90 |
Typical p50 | 116ms (better) | 272ms |
Typical p95 | 178ms (better) | 327ms |
Worst day | 99.92% | 99.96% |
up24 incidents · 90d | 20 | 70 |
WS delivering · 24h | 99.94% (better) | 99.93% |
WS connected · 24h | 99.99% | 99.99% |
Reconnects · 24h | 26 (better) | 30 |
Sequence gaps · 24h | 0 | 0 |
Longest feed silence · 24h | 21s (better) | 3 min 50s |
Own status feed | statuspage | statuspage |
Incidents they acknowledged | 9 of 20 | 0 of 70 |
Median gap to their own notice | 1h 47m later | — |
COINBASE
Over the 62 days of a 90-day window up24 has measured so far, Coinbase's REST API answered 99.98% of 3,082,890 checks, with a typical p95 of 178ms and a typical p50 of 116ms. Its worst day was 25 SEP 2026, at 99.92%. up24 opened 20 incidents against it in that window — uptime counts REST checks only, and an incident is as often a WebSocket feed that stalled or a socket that dropped.
Over the last 24 hours Coinbase's WebSocket feeds were delivering 99.94% of the time on a socket up24 held open 99.99% of it, across 26 reconnects, with 0 sequence gaps and a longest silence of 21s.
CRYPTO.COM
Over the 60 days of a 90-day window up24 has measured so far, Crypto.com's REST API answered 99.99% of 2,980,914 checks, with a typical p95 of 327ms and a typical p50 of 272ms. Its worst day was 15 AUG 2026, at 99.96%. up24 opened 70 incidents against it in that window — uptime counts REST checks only, and an incident is as often a WebSocket feed that stalled or a socket that dropped.
Over the last 24 hours Crypto.com's WebSocket feeds were delivering 99.93% of the time on a socket up24 held open 99.99% of it, across 30 reconnects, with 0 sequence gaps and a longest silence of 3 min 50s.
Uptime is ok checks over total checks, REST only. Both percentiles are medians of daily percentiles over the window rather than the window's own — percentiles do not compose, and the daily rollup is the finest grain that outlives raw retention. Green marks the better column on that row and nothing else: a venue with no measurement never wins one.