Bybit REST · ping degradation, 50s on 20 AUG 2026
Bybit REST · ping — 22% of checks failing over the last minute (timeout) — re-graded on 12 Sep 2026: an outage grade now needs two minutes, and this lasted 50 seconds. up24 opened this incident from its own measurements of Bybit's public API on 20 AUG 2026 10:23 UTC. It lasted 50s and ended 20 AUG 2026 10:24 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, timeout.
- 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, 2 of 728 checks failed: timeout ×2.
REST latency for the failing endpoint, per minute, from 20 AUG 2026 09:53 UTC to 20 AUG 2026 10:54 UTC. The gap in the line is where nothing answered.
DID BYBIT SAY SO?
Bybit 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 19 incidents for Bybit in the last 90 days. Nothing Bybit published lines up with any of them.
BYBIT — OTHER INCIDENTS
Measured by up24's own probe against Bybit's public API, BTCUSDT against USDT, every 5s. This page is generated from the incident's own rows — 2 recorded transitions — and nothing on it is reported by Bybit.