Deribit WS · book outage, 43 min on 05 NOV 2026
Deribit WS · book — 100% of windows stalled over the last minute (stalled) — from every region. up24 opened this incident from its own measurements of Deribit's public API on 05 NOV 2026 15:00 UTC. It lasted 43 min and ended 05 NOV 2026 15:43 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, stalled.
- up24 raised it to outage — the same incident, not a second one.
- up24 saw Deribit's own status flag switch on, at its poll.
- up24 saw Deribit's status flag switch off, at its poll.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.
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: true”. 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: true · 05 NOV 2026 15:24 UTC · a live flag up24 watched change, not a timestamp the venue published
up24 opened 255 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 — 5 recorded transitions — and nothing on it is reported by Deribit.