← Deribit status page

Deribit REST · depth degradation, 14 min on 11 NOV 2026

Deribit REST · depth — p95 818ms over the last five minutes, 8.7× the 7-day baseline of 94ms — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Deribit's public API on 11 NOV 2026 17:14 UTC. It lasted 14 min and ended 11 NOV 2026 17:28 UTC, when the component started answering again.

DEGRADEDREST · depth · https://www.deribit.com/api/v2/public/get_order_book?instrument_name=BTC-PERPETUAL&depth=20
DURATION
14 min
STARTED
11 NOV 2026 17:14 UTC
ENDED
11 NOV 2026 17:28 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 11 NOV 2026 17:14 UTC
    up24 opened the incident at degraded.
  2. 11 NOV 2026 17:28 UTC
    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, 1 of 2,664 checks failed: timeout ×1.

— p50‑ ‑ p95
axis 0 – 2000ms
16:45 · 11 NOV17:21 · 11 NOV17:58 · 11 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 11 NOV 2026 16:44 UTC to 11 NOV 2026 17:58 UTC. The gap in the line is where nothing answered.

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.