OKX REST · ticker degradation, 1 min on 22 AUG 2026
OKX REST · ticker — p95 1196ms over five minutes, 4.1× the 7-day baseline of 289ms. up24 opened this incident from its own measurements of OKX's public API on 22 AUG 2026 14:16 UTC. It lasted 1 min and ended 22 AUG 2026 14:17 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- 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, 0 of 738 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 22 AUG 2026 13:46 UTC to 22 AUG 2026 14:47 UTC. The gap in the line is where nothing answered.
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 13 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.