Upbit WS · connection degradation, 3 min on 25 AUG 2026
Upbit WS — 10% of windows failing over the last five minutes (conn) — from every region. up24 opened this incident from its own measurements of Upbit's public API on 25 AUG 2026 06:17 UTC. It lasted 3 min and ended 25 AUG 2026 06:20 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, conn.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.
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 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.