OKX Futures WS · connection degradation, 2 min on 22 SEP 2026
OKX Futures WS — 6.7% of windows failing over the last five minutes (conn) — from Lauterbourg, FR and Singapore, SG. up24 opened this incident from its own measurements of OKX Futures's public API on 22 SEP 2026 06:19 UTC. It lasted 2 min and ended 22 SEP 2026 06:21 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, conn.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.
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.