Upbit REST · ping degradation, 14 min on 31 AUG 2026
Upbit REST · ping — intermittently degraded: 2 episodes in the last hour, most recently p95 1111ms over five minutes, 4.2× the 7-day baseline of 266ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Upbit's public API on 31 AUG 2026 13:18 UTC. It lasted 14 min and ended 31 AUG 2026 13:32 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- 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, 1 of 2,592 checks failed: timeout ×1.
REST latency for the failing endpoint, per minute, from 31 AUG 2026 12:48 UTC to 31 AUG 2026 14:02 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.