← Hyperliquid status page

Hyperliquid WS · book outage, 4 min on 14 NOV 2026

Hyperliquid WS · book — 100% of windows failing over the last minute (timeout) — from Lauterbourg, FR and Carlstadt, US; Singapore, SG read outage by another measure. up24 opened this incident from its own measurements of Hyperliquid's public API on 14 NOV 2026 08:32 UTC. It lasted 4 min and ended 14 NOV 2026 08:37 UTC, when the component started answering again.

OUTAGEWS · book · l2Book
DURATION
4 min
STARTED
14 NOV 2026 08:32 UTC
ENDED
14 NOV 2026 08:37 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 14 NOV 2026 08:32 UTC
    up24 opened the incident at degraded, timeout.
  2. 14 NOV 2026 08:37 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 14 NOV 2026 08:37 UTC
    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, 68 of 1,167 ten-second windows failed: http_5xx ×34, stalled ×17, timeout ×15, conn ×2.

— p50‑ ‑ p95
axis 0 – 1000ms
08:03 · 14 NOV08:35 · 14 NOV09:07 · 14 NOV

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 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.