← Hyperliquid status page

Hyperliquid WS · book degradation, 5 min on 18 NOV 2026

Hyperliquid WS · book — 33% of windows stalled over the last minute (stalled) — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Hyperliquid's public API on 18 NOV 2026 04:30 UTC. It lasted 5 min and ended 18 NOV 2026 04:35 UTC, when the component started answering again.

DEGRADEDWS · book · l2Book
DURATION
5 min
STARTED
18 NOV 2026 04:30 UTC
ENDED
18 NOV 2026 04:35 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 18 NOV 2026 04:30 UTC
    up24 opened the incident at degraded, stalled.
  2. 18 NOV 2026 04:35 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, 9 of 1,170 ten-second windows failed: conn ×5, stalled ×4.

— p50‑ ‑ p95
axis 0 – 1000ms
04:01 · 18 NOV04:33 · 18 NOV05:05 · 18 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 — 2 recorded transitions — and nothing on it is reported by Hyperliquid.