← Deribit status page

Deribit REST · depth outage, 21 min on 28 SEP 2026

Deribit REST · depth — 100% of checks failing over the last minute (http_5xx) — from every region. up24 opened this incident from its own measurements of Deribit's public API on 28 SEP 2026 09:00 UTC. It lasted 21 min and ended 28 SEP 2026 09:22 UTC, when the component started answering again.

OUTAGEREST · depth · https://www.deribit.com/api/v2/public/get_order_book?instrument_name=BTC-PERPETUAL&depth=20
DURATION
21 min
STARTED
28 SEP 2026 09:00 UTC
ENDED
28 SEP 2026 09:22 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 28 SEP 2026 09:00 UTC
    up24 opened the incident at degraded, http_5xx.
  2. 28 SEP 2026 09:02 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 28 SEP 2026 09:22 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, 624 of 2,950 checks failed: http_5xx ×623, timeout ×1.

— p50‑ ‑ p95
axis 0 – 1000ms
08:31 · 28 SEP09:11 · 28 SEP09:52 · 28 SEP

REST latency for the failing endpoint, per minute, from 28 SEP 2026 08:30 UTC to 28 SEP 2026 09: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 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.