← Upbit status page

Upbit WS · book outage, ongoing since 18 OCT 2026

Upbit WS · book — 100% of windows failing over the last minute (timeout) — from every region. up24 opened this incident from its own measurements of Upbit's public API on 18 OCT 2026 17:00 UTC. It is still open, 1h 19m in.

OUTAGEWS · book · orderbook
DURATION
1h 19m
STARTED
18 OCT 2026 17:00 UTC
ENDED
ONGOING
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 18 OCT 2026 17:00 UTC
    up24 opened the incident at degraded, timeout.
  2. 18 OCT 2026 17:05 UTC
    up24 raised it to outage — the same incident, not a second one.

HOW IT FAILED

Over the window, 1,369 of 2,794 ten-second windows failed: timeout ×1,315, stalled ×54.

— p50‑ ‑ p95
axis 0 – 1000ms
15:42 · 18 OCT17:00 · 18 OCT18:18 · 18 OCT

A stream has no latency of its own — a feed either delivers or it does not — so this is Upbit's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.

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 41 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.