OKX WS · connection degradation, 4 min on 20 OCT 2026
OKX WS — 33% of windows failing over the last minute (conn) — from Singapore, SG and Lauterbourg, FR — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of OKX's public API on 20 OCT 2026 02:52 UTC. It lasted 4 min and ended 20 OCT 2026 02:56 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
Over the window, 10 of 2,310 ten-second windows failed: conn ×10.
A stream has no latency of its own — a feed either delivers or it does not — so this is OKX'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 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 16 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.