← Upbit status page

Upbit REST · ping outage, 17 min on 02 SEP 2026

Upbit REST · ping — 33% of checks failing over the last minute (timeout) — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Upbit's public API on 02 SEP 2026 13:44 UTC. It lasted 17 min and ended 02 SEP 2026 14:01 UTC, when the component started answering again.

OUTAGEREST · ping · https://api.upbit.com/v1/candles/minutes/1?market=KRW-BTC&count=1
DURATION
17 min
STARTED
02 SEP 2026 13:44 UTC
ENDED
02 SEP 2026 14:01 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 02 SEP 2026 13:44 UTC
    up24 opened the incident at outage, timeout.
  2. 02 SEP 2026 14:01 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, 287 of 2,380 checks failed: timeout ×286, conn ×1.

— p50‑ ‑ p95
axis 0 – 5000ms
13:15 · 02 SEP13:53 · 02 SEP14:31 · 02 SEP

REST latency for the failing endpoint, per minute, from 02 SEP 2026 13:14 UTC to 02 SEP 2026 14:31 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.