← Deribit status page

Deribit WS · connection outage, ongoing since 20 NOV 2026

Deribit WS — 100% of windows failing over the last minute (http_5xx) — from every region. up24 opened this incident from its own measurements of Deribit's public API on 20 NOV 2026 19:36 UTC. It is still open, 1h 09m in.

OUTAGEWS · connection · the shared socket
DURATION
1h 09m
STARTED
20 NOV 2026 19:36 UTC
ENDED
ONGOING
VENUE FLAG
FLAG ON

WHAT HAPPENED

  1. 20 NOV 2026 19:16 UTC
    up24 saw Deribit's own status flag switch on, at its poll.
  2. 20 NOV 2026 19:36 UTC
    up24 opened the incident at outage, http_5xx.

HOW IT FAILED

Over the window, 2,921 of 4,962 ten-second windows failed: http_5xx ×2,592, stalled ×323, conn ×6.

— p50‑ ‑ p95
axis 0 – 5000ms
18:27 · 20 NOV19:36 · 20 NOV20:45 · 20 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: 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 · 20 NOV 2026 19:16 UTC · a live flag up24 watched change, not a timestamp the venue published

up24 opened 261 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.