Bybit vs Hyperliquid: which API is more reliable?
Over the 60 days of a 90-day window up24 has measured so far, Bybit was more available — 99.99% against 99.98% of checks answered, and Bybit was quicker — a typical p95 of 288ms against 375ms.
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.99% | 99.98% |
REST checks behind it | 3,076,902 | 3,001,388 |
Days measured | 62 of 90 | 60 of 90 |
Typical p50 | 180ms (better) | 242ms |
Typical p95 | 288ms (better) | 375ms |
Worst day | 99.88% | 99.88% |
up24 incidents · 90d | 19 | 37 |
WS delivering · 24h | 99.96% (better) | 99.88% |
WS connected · 24h | 99.99% (better) | 99.98% |
Reconnects · 24h | 12 (better) | 54 |
Sequence gaps · 24h | 0 | not published |
Longest feed silence · 24h | 47s | 24s (better) |
Own status feed | none published | statuspage |
Incidents they acknowledged | 0 of 19 | 0 of 37 |
Median gap to their own notice | — | — |
BYBIT
Over the 62 days of a 90-day window up24 has measured so far, Bybit's REST API answered 99.99% of 3,076,902 checks, with a typical p95 of 288ms and a typical p50 of 180ms. Its worst day was 10 SEP 2026, at 99.88%. up24 opened 19 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 Bybit's WebSocket feeds were delivering 99.96% of the time on a socket up24 held open 99.99% of it, across 12 reconnects, with 0 sequence gaps and a longest silence of 47s.
HYPERLIQUID
Over the 60 days of a 90-day window up24 has measured so far, Hyperliquid's REST API answered 99.98% of 3,001,388 checks, with a typical p95 of 375ms and a typical p50 of 242ms. Its worst day was 15 AUG 2026, at 99.88%. up24 opened 37 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 Hyperliquid's WebSocket feeds were delivering 99.88% of the time on a socket up24 held open 99.98% of it, across 54 reconnects, (sequence numbers are not checked for this feed), with a longest silence of 24s.
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.