← OKX status page

OKX REST · depth outage, 4 min on 08 SEP 2026

OKX REST · depth — 33% of checks failing over the last minute (bad_body) — from every region. up24 opened this incident from its own measurements of OKX's public API on 08 SEP 2026 09:55 UTC. It lasted 4 min and ended 08 SEP 2026 10:00 UTC, when the component started answering again.

OUTAGEREST · depth · https://www.okx.com/api/v5/market/books?instId=BTC-USDT&sz=20
DURATION
4 min
STARTED
08 SEP 2026 09:55 UTC
ENDED
08 SEP 2026 10:00 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 08 SEP 2026 09:55 UTC
    up24 opened the incident at outage, bad_body.
  2. 08 SEP 2026 10:00 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, 11 of 2,340 checks failed: bad_body ×11.

— p50‑ ‑ p95
axis 0 – 2000ms
09:26 · 08 SEP09:58 · 08 SEP10:30 · 08 SEP

REST latency for the failing endpoint, per minute, from 08 SEP 2026 09:25 UTC to 08 SEP 2026 10:30 UTC. The gap in the line is where nothing answered.

DID OKX SAY SO?

OKX 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 13 incidents for OKX in the last 90 days. Nothing OKX published lines up with any of them.

OKX — OTHER INCIDENTS

Measured by up24's own probe against OKX's public API, BTC-USDT against USDT, every 5s. This page is generated from the incident's own rows — 2 recorded transitions — and nothing on it is reported by OKX.