← Deribit status page

Deribit REST · depth degradation, 5 min on 20 NOV 2026

Deribit REST · depth — p95 736ms over the last five minutes, 6.5× the 7-day baseline of 113ms — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 20 NOV 2026 16:03 UTC. It lasted 5 min and ended 20 NOV 2026 16:09 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
5 min
STARTED
20 NOV 2026 16:03 UTC
ENDED
20 NOV 2026 16:09 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 20 NOV 2026 16:03 UTC
    up24 opened the incident at degraded.
  2. 20 NOV 2026 16:09 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, 14 of 2,376 checks failed: timeout ×14.

— p50‑ ‑ p95
axis 0 – 5000ms
15:34 · 20 NOV16:06 · 20 NOV16:39 · 20 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 20 NOV 2026 15:33 UTC to 20 NOV 2026 16:39 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.