← Bybit Futures status page

Bybit Futures WS · connection degradation, 4 min on 12 NOV 2026

Bybit Futures WS — 33% of windows failing over the last minute (http_5xx) — from Singapore, SG and Carlstadt, US — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of Bybit Futures's public API on 12 NOV 2026 12:06 UTC. It lasted 4 min and ended 12 NOV 2026 12:11 UTC, when the component started answering again.

DEGRADEDWS · connection · the shared socket
DURATION
4 min
STARTED
12 NOV 2026 12:06 UTC
ENDED
12 NOV 2026 12:11 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 12 NOV 2026 12:06 UTC
    up24 opened the incident at degraded, http_5xx.
  2. 12 NOV 2026 12:11 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.

HOW IT FAILED

Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.

— p50‑ ‑ p95
axis 0 – 1000ms
11:37 · 12 NOV12:09 · 12 NOV12:41 · 12 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.