← Upbit status page

Upbit REST · depth degradation, 30s on 15 AUG 2026

Upbit REST · depth — p95 1237ms over five minutes, 4.6× the 7-day baseline of 270ms. up24 opened this incident from its own measurements of Upbit's public API on 15 AUG 2026 16:13 UTC. It lasted 30s and ended 15 AUG 2026 16:13 UTC, when the component started answering again.

DEGRADEDREST · depth · https://api.upbit.com/v1/orderbook?markets=KRW-BTC
DURATION
30s
STARTED
15 AUG 2026 16:13 UTC
ENDED
15 AUG 2026 16:13 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 15 AUG 2026 16:13 UTC
    up24 opened the incident at degraded.
  2. 15 AUG 2026 16:13 UTC
    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 716 checks failed: timeout ×6.

— p50‑ ‑ p95
axis 0 – 2000ms
15:44 · 15 AUG16:13 · 15 AUG16:43 · 15 AUG

REST latency for the failing endpoint, per minute, from 15 AUG 2026 15:43 UTC to 15 AUG 2026 16:43 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.