WS · connection · conn
HYP
Hyperliquid API status
OPERATIONALBTC · api.hyperliquid.xyz · 3 REST endpoints · 2 streams · every 5s
UPTIME · 60 OF 90 DAYS MEASURED
99.98%
TYPICAL P50 · 24H
242ms
TYPICAL P95 · 24H
330ms
INCIDENTS · 90D
37
UPTIME · LAST 90 DAYS · ALL REST ENDPOINTS
■ operational■ degraded■ outage■ not measured
14 JUL27 AUG11 OCT
Over the 60 days of a 90-day window up24 has measured so far, Hyperliquid's REST API answered 99.98% of 2,995,880 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. Is Hyperliquid down right now? →
— p50‑ ‑ p95
axis 0 – 1000ms06:20 · 10 OCT18:20 · 10 OCT06:20 · 11 OCT
| REGION | P50 | P95 | UPTIME | CHECKS |
|---|---|---|---|---|
Asia Singapore, SG | 84ms | 159ms | 99.88% | 51,798 |
Europe Lauterbourg, FR · shown above | 242ms | 339ms | 99.88% | 51,812 |
US East Carlstadt, US | 166ms | 292ms | 99.88% | 51,782 |
Latency is measured from each region separately and never averaged between them — the distance is the measurement. Uptime, incidents and the 90-day bars above are the opposite: they combine every region by quorum, so one probe box losing its route to an exchange is not recorded as that exchange going down. Quorum is a counting rule and it only holds while a majority can still see the venue; where a vantage point cannot measure this venue at all, its refusals are named below and left out of every number on the page rather than being left to a vote.
REST ENDPOINTS · LAST 24H · LAUTERBOURG
| ENDPOINT | P50 | P95 | UPTIME | STATUS |
|---|---|---|---|---|
REST · ping 17,273 checks · every 5s · api.hyperliquid.xyz | 248ms | 352ms | 99.87% | OPERATIONAL |
REST · ticker 17,271 checks · every 5s · api.hyperliquid.xyz | 236ms | 336ms | 99.88% | OPERATIONAL |
REST · depth 17,268 checks · every 5s · api.hyperliquid.xyz | 237ms | 333ms | 99.88% | OPERATIONAL |
WEBSOCKET STREAMS · LAST 24H · LAUTERBOURG
| STREAM | CONNECTED | DELIVERING | MESSAGES | MAX GAP | SEQ GAPS | RECONNECTS | RTT | STATUS |
|---|---|---|---|---|---|---|---|---|
WS · trade trades | 99.86% | 99.75% | 49,031 | 2 min 15s | — | 9 | 230ms | OPERATIONAL |
WS · book l2Book | 99.86% | 99.74% | 16,067 | 2 min 16s | — | 9 | 230ms | OPERATIONAL |
HYPERLIQUID SAID · 90D
up24 opened 37 incidents for Hyperliquid in the last 90 days. Nothing Hyperliquid published lines up with any of them.
Hyperliquid has published nothing in the last 90 days. That is not the same as ninety quiet days — compare it with the incident timeline.
Read from hyperliquid.statuspage.io every 5 minutes. Times are the venue’s own.
INCIDENT HISTORY · 90D
■ operational■ degraded■ outage■ not measured
37 incidents over 60 measured days, grouped into 10 distinct faults. A component that fails the same way twice a week has one fault many times, not many faults, and a list that prints it once per firing hides the difference behind its own length.
14 JULincidents opened per day · tallest bar is 411 OCT
WORST · 90D
WS · connection · http_5xx
WS · connection · http_5xx
WS · connection · http_5xx
BY FAULTranked by how often each fired · every occurrence links to its own page
WS · connection · http_5xxHyperliquid WS — 83% of windows failing over the last minute (http_5xx) — from every region6×7 minMEDIAN10 OCTLAST SEEN
Every occurrence, newest first. 29 AUG 2026 → 10 OCT 2026.
REST · depth · timeoutHyperliquid REST · depth — 60% of checks failing over the last minute (timeout) — from every region5×6 minMEDIAN10 OCTLAST SEEN
Every occurrence, newest first. 13 SEP 2026 → 10 OCT 2026.
REST · ticker · http_5xxHyperliquid REST · ticker — 22% of checks failing over the last minute (http_5xx) — from every region5×6 minMEDIAN26 SEPLAST SEEN
Every occurrence, newest first. 15 AUG 2026 → 26 SEP 2026.
REST · ping · http_5xxHyperliquid REST · ping — 44% of checks failing over the last minute (http_5xx) — from every region5×6 minMEDIAN26 SEPLAST SEEN
Every occurrence, newest first. 15 AUG 2026 → 26 SEP 2026.
REST · ticker · timeoutHyperliquid REST · ticker — 67% of checks failing over the last minute (timeout) — from every region4×6 minMEDIAN10 OCTLAST SEEN
Every occurrence, newest first. 13 SEP 2026 → 10 OCT 2026.
REST · ping · timeoutHyperliquid REST · ping — 56% of checks failing over the last minute (timeout) — from every region4×6 minMEDIAN10 OCTLAST SEEN
Every occurrence, newest first. 13 SEP 2026 → 10 OCT 2026.
REST · depth · http_5xxHyperliquid REST · depth — 25% of checks failing over the last minute (http_5xx) — from every region4×6 minMEDIAN05 SEPLAST SEEN
Every occurrence, newest first. 15 AUG 2026 → 05 SEP 2026.
WS · connection · connHyperliquid WS — 33% of windows failing over the last minute (conn) — from Singapore, SG and Carlstadt, US2×4 minMEDIAN05 SEPLAST SEEN
Every occurrence, newest first. 14 AUG 2026 → 05 SEP 2026.
REST · pingHyperliquid REST · ping — p95 1227ms over five minutes, 4× the 7-day baseline of 306ms — from Lauterbourg, FR and Carlstadt, US1×30sMEDIAN01 SEPLAST SEEN
Every occurrence, newest first. 01 SEP 2026 → 01 SEP 2026.
WS · book · stalledHyperliquid WS · book — 33% of windows stalled over the last minute (stalled)1×5 minMEDIAN21 AUGLAST SEEN
Every occurrence, newest first. 21 AUG 2026 → 21 AUG 2026.
Incidents are opened by up24's own state machine over its own measurements, not by Hyperliquid's status page. One WebSocket carries every stream a venue publishes, so a dropped socket is recorded once, against the connection, rather than once per stream.