← Bybit status page

Bybit REST · depth degradation, 15s on 12 SEP 2026

Bybit REST · depth — 100% of checks failing over the last five minutes (timeout) — from Carlstadt, US and Lauterbourg, FR — re-graded on 12 Sep 2026: an outage grade now needs two minutes, and this lasted 15 seconds. up24 opened this incident from its own measurements of Bybit's public API on 12 SEP 2026 15:04 UTC. It lasted 15s and ended 12 SEP 2026 15:04 UTC, when the component started answering again.

DEGRADEDREST · depth · https://api.bybit.com/v5/market/orderbook?category=spot&symbol=BTCUSDT&limit=20
DURATION
15s
STARTED
12 SEP 2026 15:04 UTC
ENDED
12 SEP 2026 15:04 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 12 SEP 2026 15:04 UTC
    up24 opened the incident at degraded, timeout.
  2. 12 SEP 2026 15:04 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, 0 of 1,056 checks failed: http_4xx ×379, http_403 ×328, timeout ×129.

— p50‑ ‑ p95
axis 0 – 500ms
14:35 · 12 SEP15:04 · 12 SEP15:34 · 12 SEP

REST latency for the failing endpoint, per minute, from 12 SEP 2026 14:34 UTC to 12 SEP 2026 15:34 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.