Upbit REST · depth outage, 8 min on 15 AUG 2026
Upbit REST · depth — 33% of checks failing over the last minute (timeout). up24 opened this incident from its own measurements of Upbit's public API on 15 AUG 2026 15:46 UTC. It lasted 8 min and ended 15 AUG 2026 15:54 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, timeout.
- up24 raised it to outage — the same incident, not a second one.
- 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, 6 of 812 checks failed: timeout ×6.
REST latency for the failing endpoint, per minute, from 15 AUG 2026 15:16 UTC to 15 AUG 2026 16:24 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 — 3 recorded transitions — and nothing on it is reported by Upbit.