OKX Futures WS · book degradation, 4 min on 09 OCT 2026
OKX Futures WS · book — 13.3% of windows stalled over the last five minutes (stalled) — from Carlstadt, US and Singapore, SG. up24 opened this incident from its own measurements of OKX Futures's public API on 09 OCT 2026 16:33 UTC. It lasted 4 min and ended 09 OCT 2026 16:38 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, stalled.
- 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, 16 of 1,167 ten-second windows failed: stalled ×14, conn ×2.
A stream has no latency of its own — a feed either delivers or it does not — so this is OKX Futures's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.
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.