← Upbit status page

Upbit REST · ping outage, 29 min on 15 AUG 2026

Upbit REST · ping — 27% of checks failing over the last minute (timeout). up24 opened this incident from its own measurements of Upbit's public API on 15 AUG 2026 15:45 UTC. It lasted 29 min and ended 15 AUG 2026 16:15 UTC, when the component started answering again.

OUTAGEREST · ping · https://api.upbit.com/v1/candles/minutes/1?market=KRW-BTC&count=1
DURATION
29 min
STARTED
15 AUG 2026 15:45 UTC
ENDED
15 AUG 2026 16:15 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 15 AUG 2026 15:45 UTC
    up24 opened the incident at outage, timeout.
  2. 15 AUG 2026 16:15 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,076 checks failed: timeout ×7.

— p50‑ ‑ p95
axis 0 – 5000ms
15:16 · 15 AUG16:00 · 15 AUG16:45 · 15 AUG

REST latency for the failing endpoint, per minute, from 15 AUG 2026 15:15 UTC to 15 AUG 2026 16:45 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.