Hyperliquid WS · connection outage, 7 min on 25 OCT 2026
Hyperliquid WS — 100% of windows failing over the last minute (http_5xx) — from Singapore, SG and Carlstadt, US; Lauterbourg, FR read outage by another measure. up24 opened this incident from its own measurements of Hyperliquid's public API on 25 OCT 2026 09:33 UTC. It lasted 7 min and ended 25 OCT 2026 09:40 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, http_5xx.
- up24 raised it to outage — the same incident, not a second one.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Over the window, 102 of 2,418 ten-second windows failed: http_5xx ×68, timeout ×32, conn ×2.
A stream has no latency of its own — a feed either delivers or it does not — so this is Hyperliquid's REST endpoints over the same window, per minute, as the median across them, measured from Lauterbourg, FR. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.
DID HYPERLIQUID SAY SO?
Hyperliquid publishes a status feed and nothing in it lines up with this incident. That is not proof they stayed silent; it is what their feed says.
up24 opened 41 incidents for Hyperliquid in the last 90 days. Nothing Hyperliquid published lines up with any of them.
HYPERLIQUID — OTHER INCIDENTS
Measured by up24's own probe against Hyperliquid's public API, BTC against USD, every 5s. This page is generated from the incident's own rows — 3 recorded transitions — and nothing on it is reported by Hyperliquid.