OKX Futures API status

Over the 42 days of a 90-day window up24 has measured so far, OKX Futures's REST API answered 99.99% of 2,094,988 checks, with a typical p95 of 359ms and a typical p50 of 269ms. Its worst day was 08 SEP 2026, at 99.98%. up24 opened 8 incidents against it in that window — uptime counts REST checks only, and an incident is as often a WebSocket feed that stalled or a socket that dropped. Is OKX Futures down right now? →

Latency is measured from each region separately and never averaged between them — the distance is the measurement. Uptime, incidents and the 90-day bars above are the opposite: they combine every region by quorum, so one probe box losing its route to an exchange is not recorded as that exchange going down. Quorum is a counting rule and it only holds while a majority can still see the venue; where a vantage point cannot measure this venue at all, its refusals are named below and left out of every number on the page rather than being left to a vote.

8 incidents over 42 measured days, grouped into 5 distinct faults. A component that fails the same way twice a week has one fault many times, not many faults, and a list that prints it once per firing hides the difference behind its own length.

WORST · 90D

BY FAULTranked by how often each fired · every occurrence links to its own page

Incidents are opened by up24's own state machine over its own measurements, not by OKX Futures's status page. One WebSocket carries every stream a venue publishes, so a dropped socket is recorded once, against the connection, rather than once per stream.

The USDT-margined perpetual swap (BTC-USDT-SWAP), which OKX serves from the same REST hosts and the same public socket as spot — so a network fault common to both will show on both. Measured on public market data only: top of book, the REST depth snapshot and the trades and books channels. Order placement, margin, the liquidation engine and funding are not measured. OKX Futures's own note on this