Bybit Futures API status
OPERATIONALUPTIME · LAST 90 DAYS · ALL REST ENDPOINTS
Over the 42 days of a 90-day window up24 has measured so far, Bybit Futures's REST API answered 99.99% of 2,039,447 checks, with a typical p95 of 278ms and a typical p50 of 180ms. Its worst day was 10 SEP 2026, at 99.88%. up24 opened 4 incidents against it in that window — uptime counts REST checks only, and an incident is as often a WebSocket feed that stalled or a socket that dropped. Is Bybit Futures down right now? →
| REGION | P50 | P95 | UPTIME | CHECKS |
|---|---|---|---|---|
Asia Singapore, SG | 10ms | 24ms | 100.00% | 51,807 |
Europe Lauterbourg, FR · shown above | 177ms | 217ms | 100.00% | 51,837 |
US East Carlstadt, US · 51,803 refused, not counted | — | — | not measured | 0 |
Latency is measured from each region separately and never averaged between them — the distance is the measurement. Uptime, incidents and the 90-day bars above are the opposite: they combine every region by quorum, so one probe box losing its route to an exchange is not recorded as that exchange going down. Quorum is a counting rule and it only holds while a majority can still see the venue; where a vantage point cannot measure this venue at all, its refusals are named below and left out of every number on the page rather than being left to a vote.
US East — not measured. Bybit Futures does not serve Carlstadt: 51,803 checks were refused there in the last day, since 30 Aug 2026, and none of them is a measurement of whether Bybit Futures is up. They are out of this row's uptime and out of the 90-day figure. Carlstadt is refused with HTTP 403 on every REST endpoint, on every check, while Lauterbourg and Singapore are served normally. The venue says why in the body of the refusal: “The Amazon CloudFront distribution is configured to block access from your country”. A refusal from the venue’s own edge, not a route that failed, and not a measurement of whether the venue is serving anybody else — so a reading carrying this class is discounted wherever it was recorded, the socket’s ten-second windows included — though the refused count beside this note is REST checks only.
REST ENDPOINTS · LAST 24H · LAUTERBOURG
| ENDPOINT | P50 | P95 | UPTIME | STATUS |
|---|---|---|---|---|
REST · ping 17,279 checks · every 5s · api.bybit.com | 176ms | 216ms | 100.00% | OPERATIONAL |
REST · ticker 17,279 checks · every 5s · api.bybit.com | 177ms | 212ms | 100.00% | OPERATIONAL |
REST · depth 17,279 checks · every 5s · api.bybit.com | 177ms | 222ms | 100.00% | OPERATIONAL |
WEBSOCKET STREAMS · LAST 24H · LAUTERBOURG
| STREAM | CONNECTED | DELIVERING | MESSAGES | MAX GAP | SEQ GAPS | RECONNECTS | RTT | STATUS |
|---|---|---|---|---|---|---|---|---|
WS · trade publicTrade.BTCUSDT | 100.00% | 100.00% | 130,422 | 53s | — | 0 | 167ms | OPERATIONAL |
WS · book orderbook.50.BTCUSDT | 100.00% | 100.00% | 2,220,336 | 2824ms | 0 | 0 | 167ms | OPERATIONAL |
BYBIT FUTURES SAID · 90D
up24 opened 4 incidents for Bybit Futures in the last 90 days. Nothing Bybit Futures published lines up with any of them.
Bybit Futures publishes no machine-readable status feed — no status page API, no maintenance calendar, nothing with a timestamp on it. Everything on this page is up24's own measurement, because there is nothing to compare it against.
INCIDENT HISTORY · 90D
4 incidents over 42 measured days, grouped into 4 distinct faults. A component that fails the same way twice a week has one fault many times, not many faults, and a list that prints it once per firing hides the difference behind its own length.
BY FAULTranked by how often each fired · every occurrence links to its own page
REST · depth · timeoutBybit Futures 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 seconds1×15sMEDIAN12 SEPLAST SEEN
Every occurrence, newest first. 12 SEP 2026 → 12 SEP 2026.
REST · depthBybit Futures REST · depth — p95 1340ms over the last five minutes, 4.4× the 7-day baseline of 302ms — from Carlstadt, US and Lauterbourg, FR1×40sMEDIAN07 SEPLAST SEEN
Every occurrence, newest first. 07 SEP 2026 → 07 SEP 2026.
REST · tickerBybit Futures REST · ticker — p95 1269ms over the last five minutes, 5× the 7-day baseline of 256ms — from Carlstadt, US and Lauterbourg, FR1×6 minMEDIAN07 SEPLAST SEEN
Every occurrence, newest first. 07 SEP 2026 → 07 SEP 2026.
REST · pingBybit Futures REST · ping — p95 1433ms over the last five minutes, 4.4× the 7-day baseline of 326ms — from Carlstadt, US and Lauterbourg, FR1×6 minMEDIAN07 SEPLAST SEEN
Every occurrence, newest first. 07 SEP 2026 → 07 SEP 2026.
Incidents are opened by up24's own state machine over its own measurements, not by Bybit Futures's status page. One WebSocket carries every stream a venue publishes, so a dropped socket is recorded once, against the connection, rather than once per stream.
The USDT-margined linear perpetual (BTCUSDT), which is `category=linear` on the same REST host as Bybit spot and a separate socket. Server time is the venue-wide clock, shared with spot. Measured on public market data only: top of book, the REST depth snapshot and the trade and orderbook streams. Order placement, margin, the liquidation engine and funding are not measured. Bybit Futures's own note on this