← Hyperliquid status page

Hyperliquid REST · ping outage, 6 min on 14 NOV 2026

Hyperliquid REST · ping — 73% of checks 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:35 UTC. It lasted 6 min and ended 14 NOV 2026 08:42 UTC, when the component started answering again.

OUTAGEREST · ping · https://api.hyperliquid.xyz/info
DURATION
6 min
STARTED
14 NOV 2026 08:35 UTC
ENDED
14 NOV 2026 08:42 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 14 NOV 2026 08:35 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:42 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, 73 of 2,412 checks failed: http_5xx ×46, timeout ×27.

— p50‑ ‑ p95
axis 0 – 1000ms
08:06 · 14 NOV08:39 · 14 NOV09:12 · 14 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 14 NOV 2026 08:05 UTC to 14 NOV 2026 09:12 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.