Bybit REST · ticker degradation, 10s on 31 AUG 2026
Bybit REST · ticker — p95 1275ms over five minutes, 4× the 7-day baseline of 317ms — from Carlstadt, US and Lauterbourg, FR. up24 opened this incident from its own measurements of Bybit's public API on 31 AUG 2026 11:44 UTC. It lasted 10s and ended 31 AUG 2026 11:44 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, 719 of 2,149 checks failed: http_4xx ×719.
REST latency for the failing endpoint, per minute, from 31 AUG 2026 11:14 UTC to 31 AUG 2026 12:14 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.