← Deribit status page

Deribit REST · ping outage, 6 min on 05 OCT 2026

Deribit REST · ping — 22.4% of checks failing over the last five minutes (timeout) — from every region. up24 opened this incident from its own measurements of Deribit's public API on 05 OCT 2026 12:24 UTC. It lasted 6 min and ended 05 OCT 2026 12:30 UTC, when the component started answering again.

OUTAGEREST · ping · https://www.deribit.com/api/v2/public/get_time
DURATION
6 min
STARTED
05 OCT 2026 12:24 UTC
ENDED
05 OCT 2026 12:30 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 05 OCT 2026 12:24 UTC
    up24 opened the incident at degraded, timeout.
  2. 05 OCT 2026 12:26 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 05 OCT 2026 12:30 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, 34 of 2,345 checks failed: timeout ×33, http_5xx ×1.

— p50‑ ‑ p95
axis 0 – 2000ms
11:55 · 05 OCT12:27 · 05 OCT13:00 · 05 OCT

REST latency for the failing endpoint, per minute, from 05 OCT 2026 11:54 UTC to 05 OCT 2026 13:00 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 173 incidents for Deribit in the last 90 days. Nothing Deribit published lines up with any of them.

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.