← OKX status page

OKX REST · depth outage, 4 min on 25 AUG 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 25 AUG 2026 07:09 UTC. It lasted 4 min and ended 25 AUG 2026 07:14 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
25 AUG 2026 07:09 UTC
ENDED
25 AUG 2026 07:14 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 25 AUG 2026 07:09 UTC
    up24 opened the incident at outage, bad_body.
  2. 25 AUG 2026 07:14 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, 8 of 1,558 checks failed: bad_body ×8.

— p50‑ ‑ p95
axis 0 – 1000ms
06:40 · 25 AUG07:12 · 25 AUG07:44 · 25 AUG

REST latency for the failing endpoint, per minute, from 25 AUG 2026 06:39 UTC to 25 AUG 2026 07:44 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.