← Deribit status page

Deribit REST · ticker outage, 7 min on 21 AUG 2026

Deribit REST · ticker — 33% of checks failing over the last minute (bad_body). up24 opened this incident from its own measurements of Deribit's public API on 21 AUG 2026 15:05 UTC. It lasted 7 min and ended 21 AUG 2026 15:12 UTC, when the component started answering again.

OUTAGEREST · ticker · https://www.deribit.com/api/v2/public/ticker?instrument_name=BTC-PERPETUAL
DURATION
7 min
STARTED
21 AUG 2026 15:05 UTC
ENDED
21 AUG 2026 15:12 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 21 AUG 2026 15:05 UTC
    up24 opened the incident at outage, bad_body.
  2. 21 AUG 2026 15:12 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, 31 of 804 checks failed: bad_body ×31.

— p50‑ ‑ p95
axis 0 – 200ms
14:36 · 21 AUG15:09 · 21 AUG15:42 · 21 AUG

REST latency for the failing endpoint, per minute, from 21 AUG 2026 14:35 UTC to 21 AUG 2026 15:42 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 — 2 recorded transitions — and nothing on it is reported by Deribit.