← Deribit status page

Deribit WS · book outage, 1 min on 10 NOV 2026

Deribit WS · book — 13.3% of windows stalled, and 20% failing otherwise over the last five minutes (stalled) — none of the 6 windows over the last minute failed — from Lauterbourg, FR and Carlstadt, US; Singapore, SG read outage by another measure. up24 opened this incident from its own measurements of Deribit's public API on 10 NOV 2026 09:48 UTC. It lasted 1 min and ended 10 NOV 2026 09:49 UTC, when the component started answering again.

OUTAGEWS · book · book.BTC-PERPETUAL.100ms
DURATION
1 min
STARTED
10 NOV 2026 09:48 UTC
ENDED
10 NOV 2026 09:49 UTC
VENUE FLAG
FLAG ON

WHAT HAPPENED

  1. 10 NOV 2026 09:44 UTC
    up24 saw Deribit's own status flag switch on, at its poll.
  2. 10 NOV 2026 09:48 UTC
    up24 opened the incident at outage, stalled.
  3. 10 NOV 2026 09:49 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
  4. 10 NOV 2026 09:59 UTC
    up24 saw Deribit's status flag switch off, at its poll.

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.

— p50‑ ‑ p95
axis 0 – 500ms
09:19 · 10 NOV09:49 · 10 NOV10:19 · 10 NOV

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 · 10 NOV 2026 09:44 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 — 4 recorded transitions — and nothing on it is reported by Deribit.