← Deribit status page

Deribit WS · book degradation, 2 min on 11 NOV 2026

Deribit WS · book — 6.7% of windows stalled over the last five minutes (stalled) — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 11 NOV 2026 23:54 UTC. It lasted 2 min and ended 11 NOV 2026 23:56 UTC, when the component started answering again.

DEGRADEDWS · book · book.BTC-PERPETUAL.100ms
DURATION
2 min
STARTED
11 NOV 2026 23:54 UTC
ENDED
11 NOV 2026 23:56 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 11 NOV 2026 23:54 UTC
    up24 opened the incident at degraded, stalled.
  2. 11 NOV 2026 23:56 UTC
    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.

— p50‑ ‑ p95
axis 0 – 1000ms
23:25 · 11 NOV23:55 · 11 NOV00:26 · 12 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 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 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 — 2 recorded transitions — and nothing on it is reported by Deribit.