← Hyperliquid status page

Hyperliquid REST · depth outage, 6 min on 05 SEP 2026

Hyperliquid REST · depth — 25% of checks failing over the last minute (http_5xx) — from every region. up24 opened this incident from its own measurements of Hyperliquid's public API on 05 SEP 2026 09:29 UTC. It lasted 6 min and ended 05 SEP 2026 09:36 UTC, when the component started answering again.

OUTAGEREST · depth · https://api.hyperliquid.xyz/info
DURATION
6 min
STARTED
05 SEP 2026 09:29 UTC
ENDED
05 SEP 2026 09:36 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 05 SEP 2026 09:29 UTC
    up24 opened the incident at outage, http_5xx.
  2. 05 SEP 2026 09:36 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, 58 of 2,391 checks failed: http_5xx ×42, timeout ×16.

— p50‑ ‑ p95
axis 0 – 1000ms
09:00 · 05 SEP09:33 · 05 SEP10:06 · 05 SEP

REST latency for the failing endpoint, per minute, from 05 SEP 2026 08:59 UTC to 05 SEP 2026 10:06 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 37 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.