Bybit Futures REST · ping outage, 7 min on 11 NOV 2026
Bybit Futures REST · ping — 50% of checks failing over the last minute (http_403) — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Bybit Futures's public API on 11 NOV 2026 06:14 UTC. It lasted 7 min and ended 11 NOV 2026 06:22 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, http_403.
- up24 raised it to outage — the same incident, not a second one.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Bybit Futures refused the request rather than failing it. A 403 is an access decision, not an availability one: the endpoint answered, over TLS, to say that this caller may not have it. up24 counts a refusal aimed at one of its vantage points out of that region's uptime rather than against Bybit Futures, and says so on the row.
Over the window, 37 of 1,632 checks failed: http_403 ×37; left out of the count as a declared blocked vantage: http_403 ×816.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 11 NOV 2026 05:44 UTC to 11 NOV 2026 06:52 UTC. The gap in the line is where nothing answered.
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 — 3 recorded transitions — and nothing on it is reported by Bybit Futures.