Upbit REST · depth degradation, 40s on 18 NOV 2026
Upbit REST · depth — p95 1093ms over the last five minutes, 4.8× the 7-day baseline of 230ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Upbit's public API on 18 NOV 2026 00:24 UTC. It lasted 40s and ended 18 NOV 2026 00:25 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 2,196 checks failed.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 17 NOV 2026 23:54 UTC to 18 NOV 2026 00:55 UTC. The gap in the line is where nothing answered.
DID UPBIT SAY SO?
Upbit publishes no machine-readable status feed, so there is nothing to compare this against — everything on this page is up24's own measurement.
up24 opened 62 incidents for Upbit in the last 90 days. Nothing Upbit published lines up with any of them.
UPBIT — OTHER INCIDENTS
Measured by up24's own probe against Upbit's public API, KRW-BTC against KRW, every 5s. This page is generated from the incident's own rows — 2 recorded transitions — and nothing on it is reported by Upbit.