← Bybit status page

Bybit REST · depth degradation, 4 min on 07 SEP 2026

Bybit REST · depth — p95 1578ms over the last five minutes, 4.7× the 7-day baseline of 335ms — from Carlstadt, US and Lauterbourg, FR. up24 opened this incident from its own measurements of Bybit's public API on 07 SEP 2026 16:37 UTC. It lasted 4 min and ended 07 SEP 2026 16:41 UTC, when the component started answering again.

DEGRADEDREST · depth · https://api.bybit.com/v5/market/orderbook?category=spot&symbol=BTCUSDT&limit=20
DURATION
4 min
STARTED
07 SEP 2026 16:37 UTC
ENDED
07 SEP 2026 16:41 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 07 SEP 2026 16:37 UTC
    up24 opened the incident at degraded.
  2. 07 SEP 2026 16:41 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, 768 of 2,302 checks failed: http_4xx ×768.

— p50‑ ‑ p95
axis 0 – 2000ms
16:08 · 07 SEP16:39 · 07 SEP17:11 · 07 SEP

REST latency for the failing endpoint, per minute, from 07 SEP 2026 16:07 UTC to 07 SEP 2026 17:11 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.