Deribit WS · book degradation, 1 min on 23 OCT 2026
Deribit WS · book — 6.7% of windows stalled over the last five minutes (stalled) — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 23 OCT 2026 22:03 UTC. It lasted 1 min and ended 23 OCT 2026 22:05 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, stalled.
- 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, 5 of 1,113 ten-second windows failed: conn ×3, stalled ×2.
A stream has no latency of its own — a feed either delivers or it does not — so this is Deribit's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.
DID DERIBIT SAY SO?
Deribit publishes a status feed and nothing in it lines up with this incident. That is not proof they stayed silent; it is what their feed says.
up24 opened 186 incidents for Deribit in the last 90 days. Nothing Deribit published lines up with any of them.
DERIBIT — OTHER INCIDENTS
Measured by up24's own probe against Deribit's public API, BTC-PERPETUAL against USD, every 5s. This page is generated from the incident's own rows — 2 recorded transitions — and nothing on it is reported by Deribit.