← Deribit status page

Deribit REST · ping outage, ongoing since 20 NOV 2026

Deribit REST · ping — 69% of checks failing over the last minute (timeout) — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 20 NOV 2026 19:24 UTC. It is still open, 1h 21m in.

OUTAGEREST · ping · https://www.deribit.com/api/v2/public/get_time
DURATION
1h 21m
STARTED
20 NOV 2026 19:24 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:24 UTC
    up24 opened the incident at degraded, timeout.
  3. 20 NOV 2026 19:30 UTC
    up24 raised it to outage — the same incident, not a second one.

HOW IT FAILED

Over the window, 2,693 of 5,832 checks failed: http_5xx ×2,585, timeout ×108.

— p50‑ ‑ p95
axis 0 – 2000ms
18:04 · 20 NOV19:24 · 20 NOV20:45 · 20 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 20 NOV 2026 18:03 UTC to 20 NOV 2026 20:46 UTC. The gap in the line is where nothing answered.

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 — 3 recorded transitions — and nothing on it is reported by Deribit.