Coinbase vs Kraken: which API is more reliable?
Over the 62 days of a 90-day window up24 has measured so far, Kraken was more available — 99.98% against 99.99% of checks answered, and Kraken was quicker — a typical p95 of 178ms against 65ms.
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% (better) |
REST checks behind it | 3,082,854 | 3,083,455 |
Days measured | 62 of 90 | 62 of 90 |
Typical p50 | 116ms | 27ms (better) |
Typical p95 | 178ms | 65ms (better) |
Worst day | 99.92% | 99.95% (better) |
up24 incidents · 90d | 20 (better) | 77 |
WS delivering · 24h | 99.94% (better) | 99.86% |
WS connected · 24h | 99.99% (better) | 99.97% |
Reconnects · 24h | 26 (better) | 58 |
Sequence gaps · 24h | 0 | not published |
Longest feed silence · 24h | 21s (better) | 1 min 1s |
Own status feed | statuspage | statuspage |
Incidents they acknowledged | 9 of 20 | 39 of 77 |
Median gap to their own notice | 1h 47m later | 1h 58m 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,854 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.
KRAKEN
Over the 62 days of a 90-day window up24 has measured so far, Kraken's REST API answered 99.99% of 3,083,455 checks, with a typical p95 of 65ms and a typical p50 of 27ms. Its worst day was 14 SEP 2026, at 99.95%. up24 opened 77 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 Kraken's WebSocket feeds were delivering 99.86% of the time on a socket up24 held open 99.97% of it, across 58 reconnects, (sequence numbers are not checked for this feed), with a longest silence of 1 min 1s.
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.