← Upbit status page

Upbit REST · ping degradation, 10 min on 22 SEP 2026

Upbit REST · ping — p95 1114ms over the last five minutes, 4.1× the 7-day baseline of 275ms — from every region. up24 opened this incident from its own measurements of Upbit's public API on 22 SEP 2026 13:57 UTC. It lasted 10 min and ended 22 SEP 2026 14:07 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api.upbit.com/v1/candles/minutes/1?market=KRW-BTC&count=1
DURATION
10 min
STARTED
22 SEP 2026 13:57 UTC
ENDED
22 SEP 2026 14:07 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 22 SEP 2026 13:57 UTC
    up24 opened the incident at degraded.
  2. 22 SEP 2026 14:07 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, 7 of 1,969 checks failed: timeout ×7.

— p50‑ ‑ p95
axis 0 – 5000ms
13:28 · 22 SEP13:56 · 22 SEP14:37 · 22 SEP

REST latency for the failing endpoint, per minute, from 22 SEP 2026 13:27 UTC to 22 SEP 2026 14:37 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 — 2 recorded transitions — and nothing on it is reported by Upbit.