← Deribit status page

Deribit REST · ticker outage, 1h 30m on 05 NOV 2026

Deribit REST · ticker — intermittently degraded: 4 episodes since it opened, most recently 33% of checks failing over the last minute (timeout) — from Lauterbourg, FR and Carlstadt, US — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of Deribit's public API on 05 NOV 2026 14:45 UTC. It lasted 1h 30m and ended 05 NOV 2026 16:16 UTC, when the component started answering again.

OUTAGEREST · ticker · https://www.deribit.com/api/v2/public/ticker?instrument_name=BTC-PERPETUAL
DURATION
1h 30m
STARTED
05 NOV 2026 14:45 UTC
ENDED
05 NOV 2026 16:16 UTC
VENUE FLAG
FLAG ON

WHAT HAPPENED

  1. 05 NOV 2026 14:45 UTC
    up24 opened the incident at degraded, timeout.
  2. 05 NOV 2026 14:47 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 05 NOV 2026 15:24 UTC
    up24 saw Deribit's own status flag switch on, at its poll.
  4. 05 NOV 2026 15:39 UTC
    up24 saw Deribit's status flag switch off, at its poll.
  5. 05 NOV 2026 16:16 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, 990 of 9,792 checks failed: timeout ×506, bad_body ×462, http_5xx ×22.

— p50‑ ‑ p95
axis 0 – 5000ms
13:15 · 05 NOV15:30 · 05 NOV17:46 · 05 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 05 NOV 2026 13:14 UTC to 05 NOV 2026 17:46 UTC. The gap in the line is where nothing answered.

DID DERIBIT SAY SO?

Deribit's own status flag was on during this incident: “platform locked: true”. The flag is the venue's; when it switched is up24's own observation, polled every five minutes, so no lead time is read off it.

platform locked: true · 05 NOV 2026 15:24 UTC · a live flag up24 watched change, not a timestamp the venue published

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 — 5 recorded transitions — and nothing on it is reported by Deribit.