← Deribit status page

Deribit REST · ping degradation, 2h 06m on 12 NOV 2026

Deribit REST · ping — p95 1731ms over the last five minutes, 5.4× the 7-day baseline of 318ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 12 NOV 2026 13:39 UTC. It lasted 2h 06m and ended 12 NOV 2026 15:45 UTC, when the component started answering again.

DEGRADEDREST · ping · https://www.deribit.com/api/v2/public/get_time
DURATION
2h 06m
STARTED
12 NOV 2026 13:39 UTC
ENDED
12 NOV 2026 15:45 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 12 NOV 2026 13:39 UTC
    up24 opened the incident at degraded.
  2. 12 NOV 2026 15:45 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, 27 of 13,680 checks failed: timeout ×27.

— p50‑ ‑ p95
axis 0 – 5000ms
11:33 · 12 NOV14:42 · 12 NOV17:52 · 12 NOV

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