← Upbit status page

Upbit REST · ping outage, ongoing since 18 OCT 2026

Upbit REST · ping — 100% of checks 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:03 UTC. It is still open, 1h 13m in.

OUTAGEREST · ping · https://api.upbit.com/v1/candles/minutes/1?market=KRW-BTC&count=1
DURATION
1h 13m
STARTED
18 OCT 2026 17:03 UTC
ENDED
ONGOING
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 18 OCT 2026 17:03 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,315 of 3,902 checks failed: timeout ×1,315.

— p50‑ ‑ p95
axis 0 – 5000ms
15:51 · 18 OCT17:01 · 18 OCT18:15 · 18 OCT

REST latency for the failing endpoint, per minute, from 18 OCT 2026 15:50 UTC to 18 OCT 2026 18:17 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 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.