← Deribit status page

Deribit REST · ping outage, 30 min on 05 NOV 2026

Deribit REST · ping — 25% of checks failing over the last minute (timeout) — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Deribit's public API on 05 NOV 2026 14:53 UTC. It lasted 30 min and ended 05 NOV 2026 15:23 UTC, when the component started answering again.

OUTAGEREST · ping · https://www.deribit.com/api/v2/public/get_time
DURATION
30 min
STARTED
05 NOV 2026 14:53 UTC
ENDED
05 NOV 2026 15:23 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 05 NOV 2026 14:53 UTC
    up24 opened the incident at degraded, timeout.
  2. 05 NOV 2026 15:05 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 05 NOV 2026 15:23 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, 211 of 3,312 checks failed: timeout ×191, http_5xx ×20.

— p50‑ ‑ p95
axis 0 – 5000ms
14:23 · 05 NOV15:08 · 05 NOV15:54 · 05 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 05 NOV 2026 14:22 UTC to 05 NOV 2026 15:54 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 — 3 recorded transitions — and nothing on it is reported by Deribit.