← Upbit status page

Upbit WS · connection degradation, 3 min on 18 NOV 2026

Upbit WS — 10% of windows failing over the last five minutes (conn) — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Upbit's public API on 18 NOV 2026 02:37 UTC. It lasted 3 min and ended 18 NOV 2026 02:40 UTC, when the component started answering again.

DEGRADEDWS · connection · the shared socket
DURATION
3 min
STARTED
18 NOV 2026 02:37 UTC
ENDED
18 NOV 2026 02:40 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 18 NOV 2026 02:37 UTC
    up24 opened the incident at degraded, conn.
  2. 18 NOV 2026 02:40 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, 18 of 2,298 ten-second windows failed: conn ×18.

— p50‑ ‑ p95
axis 0 – 2000ms
02:08 · 18 NOV02:39 · 18 NOV03:10 · 18 NOV

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, measured from Lauterbourg, FR. 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 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 — 2 recorded transitions — and nothing on it is reported by Upbit.