Bybit Futures WS · book degradation, 4 min on 13 OCT 2026
Bybit Futures WS · book — 33% of windows stalled over the last minute (stalled) — from every region. up24 opened this incident from its own measurements of Bybit Futures's public API on 13 OCT 2026 06:50 UTC. It lasted 4 min and ended 13 OCT 2026 06:54 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, stalled.
- 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, 7 of 1,167 ten-second windows failed: stalled ×6, conn ×1.
A stream has no latency of its own — a feed either delivers or it does not — so this is Bybit Futures's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.
DID BYBIT FUTURES SAY SO?
Bybit Futures 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 5 incidents for Bybit Futures in the last 90 days. Nothing Bybit Futures published lines up with any of them.
BYBIT FUTURES — OTHER INCIDENTS
Measured by up24's own probe against Bybit Futures'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 Futures.