← Deribit status page

Deribit REST · ticker degradation, 50s on 20 NOV 2026

Deribit REST · ticker — 25% of checks failing over the last minute (timeout) — from Singapore, SG and Carlstadt, US — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of Deribit's public API on 20 NOV 2026 17:39 UTC. It lasted 50s and ended 20 NOV 2026 17:40 UTC, when the component started answering again.

DEGRADEDREST · ticker · https://www.deribit.com/api/v2/public/ticker?instrument_name=BTC-PERPETUAL
DURATION
50s
STARTED
20 NOV 2026 17:39 UTC
ENDED
20 NOV 2026 17:40 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 20 NOV 2026 17:39 UTC
    up24 opened the incident at degraded, timeout.
  2. 20 NOV 2026 17:40 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, 7 of 1,764 checks failed: timeout ×7.

— p50‑ ‑ p95
axis 0 – 2000ms
17:10 · 20 NOV17:34 · 20 NOV17:58 · 20 NOV

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