Deribit WS · book outage, 15 min on 20 NOV 2026
Deribit WS · book — 82.6% of windows stalled, and 17.4% failing otherwise over the last five minutes (stalled) — from Singapore, SG and Lauterbourg, FR; Carlstadt, US read outage by another measure. up24 opened this incident from its own measurements of Deribit's public API on 20 NOV 2026 21:20 UTC. It lasted 15 min and ended 20 NOV 2026 21:35 UTC, when the component started answering again.
WHAT HAPPENED
- up24 saw Deribit's own status flag switch on, at its poll.
- up24 opened the incident at outage, 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, 650 of 1,046 ten-second windows failed: http_5xx ×456, stalled ×194.
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, measured from Lauterbourg, FR. 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's own status flag was on during this incident: “platform locked: partial”. The flag is the venue's; when it switched is up24's own observation, polled every five minutes, so no lead time is read off it.
platform locked: partial · 20 NOV 2026 19:16 UTC · a live flag up24 watched change, not a timestamp the venue published
up24 opened 263 incidents for Deribit in the last 90 days. Deribit publishes only a live status flag, no reports, so there is no notice to measure a lead against; where the flag was on during an incident, that incident says so.
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 — 3 recorded transitions — and nothing on it is reported by Deribit.