Hyperliquid WS · book degradation, 5 min on 21 AUG 2026
Hyperliquid WS · book — 33% of windows stalled over the last minute (stalled). up24 opened this incident from its own measurements of Hyperliquid's public API on 21 AUG 2026 06:08 UTC. It lasted 5 min and ended 21 AUG 2026 06:13 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, stalled.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.
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. 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 37 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 — 2 recorded transitions — and nothing on it is reported by Hyperliquid.