← Bybit Futures status page

Bybit Futures WS · book degradation, 4 min on 19 NOV 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 19 NOV 2026 06:42 UTC. It lasted 4 min and ended 19 NOV 2026 06:47 UTC, when the component started answering again.

DEGRADEDWS · book · orderbook.50.BTCUSDT
DURATION
4 min
STARTED
19 NOV 2026 06:42 UTC
ENDED
19 NOV 2026 06:47 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 19 NOV 2026 06:42 UTC
    up24 opened the incident at degraded, stalled.
  2. 19 NOV 2026 06:47 UTC
    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, 6 of 1,167 ten-second windows failed: stalled ×6.

— p50‑ ‑ p95
axis 0 – 500ms
06:13 · 19 NOV06:45 · 19 NOV07:17 · 19 NOV

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, measured from Lauterbourg, FR. 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 7 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.