OKX Futures REST · depth degradation, 4 min on 22 SEP 2026
OKX Futures REST · depth — 27% of checks failing over the last minute (bad_body) — from Singapore, SG and Carlstadt, US — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of OKX Futures's public API on 22 SEP 2026 06:44 UTC. It lasted 4 min and ended 22 SEP 2026 06:48 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, bad_body.
- 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 2,301 checks failed: bad_body ×8.
REST latency for the failing endpoint, per minute, from 22 SEP 2026 06:14 UTC to 22 SEP 2026 07:18 UTC. The gap in the line is where nothing answered.
DID OKX FUTURES SAY SO?
OKX Futures 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 8 incidents for OKX Futures in the last 90 days. Nothing OKX Futures published lines up with any of them.
OKX FUTURES — OTHER INCIDENTS
Measured by up24's own probe against OKX Futures's public API, BTC-USDT-SWAP 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 Futures.