Upbit REST · depth degradation, 19 min on 21 SEP 2026
Upbit REST · depth — p95 1342ms over the last five minutes, 5.3× the 7-day baseline of 253ms — from every region. up24 opened this incident from its own measurements of Upbit's public API on 21 SEP 2026 15:52 UTC. It lasted 19 min and ended 21 SEP 2026 16:11 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, 4 of 1,890 checks failed: timeout ×4.
REST latency for the failing endpoint, per minute, from 21 SEP 2026 15:22 UTC to 21 SEP 2026 16:41 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 35 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.