Upbit REST · depth outage, 3h 51m on 08 NOV 2026
Upbit REST · depth — 100% of checks failing over the last minute (timeout) — from every region. up24 opened this incident from its own measurements of Upbit's public API on 08 NOV 2026 17:02 UTC. It lasted 3h 51m and ended 08 NOV 2026 20:53 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, 8,077 of 24,947 checks failed: timeout ×8,077.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 08 NOV 2026 13:11 UTC to 09 NOV 2026 00:44 UTC. The gap in the line is where nothing answered.
DID UPBIT SAY SO?
Announced maintenance. Upbit had announced a maintenance from 08 NOV 2026 17:00 UTC to 08 NOV 2026 22:00 UTC, and this incident began inside it: 서버 점검 안내. What is measured here is that closure as a client saw it. The grade and the uptime figure count it like any other time the API did not answer.
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 — 3 recorded transitions — and nothing on it is reported by Upbit.