Hyperliquid REST · depth outage, 6 min on 12 NOV 2026
Hyperliquid REST · depth — 75% of checks failing over the last minute (timeout) — from every region. up24 opened this incident from its own measurements of Hyperliquid's public API on 12 NOV 2026 10:44 UTC. It lasted 6 min and ended 12 NOV 2026 10:50 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, 76 of 2,376 checks failed: http_5xx ×47, timeout ×29.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 12 NOV 2026 10:14 UTC to 12 NOV 2026 11:20 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 54 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.