← all exchanges
UPB

Upbit API status

OPERATIONAL
KRW-BTC · api.upbit.com · 3 REST endpoints · 2 streams
UPTIME · 90D
100.00%
TYPICAL P50 · 24H
263ms
TYPICAL P95 · 24H
270ms
INCIDENTS · 90D
0

UPTIME · LAST 90 DAYS · ALL REST ENDPOINTS

■ operational■ degraded■ outage■ not measured
16 MAY29 JUN13 AUG

API LATENCY · 24H · MEASURED FROM RAW SAMPLES

— p50‑ ‑ p95
axis 0 – 500ms
09:00 · 13 AUG10:05 · 13 AUG11:15 · 13 AUG

REST ENDPOINTS · LAST 24H

ENDPOINTP50P95UPTIMESTATUS
REST · ping
1,628 checks · api.upbit.com
264ms275ms100.00%OPERATIONAL
REST · ticker
1,628 checks · api.upbit.com
261ms271ms100.00%OPERATIONAL
REST · depth
1,627 checks · api.upbit.com
261ms271ms100.00%OPERATIONAL

WEBSOCKET STREAMS · LAST 24H

STREAMCONNECTEDDELIVERINGMESSAGESMAX GAPSEQ GAPSRECONNECTSRTTSTATUS
WS · trade
trade
100.00%100.00%6,96737956ms002954msOPERATIONAL
WS · book
orderbook
100.00%100.00%57,7163600ms02954msOPERATIONAL

INCIDENT HISTORY · 90D

No incidents recorded for Upbit in the last 90 days.

Incidents are opened by up24's own state machine over its own measurements, not by Upbit's status page.

UPBIT SAID · 90D

No up24 incidents for Upbit in the last 90 days, so there is nothing to compare against their announcements.

Upbit publishes no machine-readable status feed — no status page API, no maintenance calendar, nothing with a timestamp on it. Everything on this page is up24's own measurement, because there is nothing to compare it against.