← Upbit status page

Upbit REST · ticker outage, 26 min on 15 AUG 2026

Upbit REST · ticker — intermittently failing: 2 episodes. up24 opened this incident from its own measurements of Upbit's public API on 15 AUG 2026 15:46 UTC. It lasted 26 min and ended 15 AUG 2026 16:12 UTC, when the component started answering again.

OUTAGEREST · ticker · https://api.upbit.com/v1/ticker?markets=KRW-BTC
DURATION
26 min
STARTED
15 AUG 2026 15:46 UTC
ENDED
15 AUG 2026 16:12 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 15 AUG 2026 15:46 UTC
    up24 opened the incident at degraded, timeout.
  2. 15 AUG 2026 15:47 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 15 AUG 2026 16:12 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, 5 of 1,028 checks failed: timeout ×5.

— p50‑ ‑ p95
axis 0 – 5000ms
15:17 · 15 AUG15:59 · 15 AUG16:42 · 15 AUG

REST latency for the failing endpoint, per minute, from 15 AUG 2026 15:16 UTC to 15 AUG 2026 16:42 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 — 3 recorded transitions — and nothing on it is reported by Upbit.