Hyperliquid REST · depth outage, 6 min on 25 OCT 2026
Hyperliquid REST · depth — 43% of checks failing over the last minute (timeout) — 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 6 min and ended 25 OCT 2026 09:39 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, timeout.
- 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, 58 of 2,355 checks failed: http_5xx ×43, timeout ×15.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 25 OCT 2026 09:03 UTC to 25 OCT 2026 10:09 UTC. The gap in the line is where nothing answered.
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.