← Deribit status page

Deribit WS · trade outage, 5 min on 13 OCT 2026

Deribit WS · trade — 100% of windows stalled over the last minute (stalled) — from every region. up24 opened this incident from its own measurements of Deribit's public API on 13 OCT 2026 09:41 UTC. It lasted 5 min and ended 13 OCT 2026 09:47 UTC, when the component started answering again.

OUTAGEWS · trade · trades.BTC-PERPETUAL.100ms
DURATION
5 min
STARTED
13 OCT 2026 09:41 UTC
ENDED
13 OCT 2026 09:47 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 13 OCT 2026 09:41 UTC
    up24 opened the incident at outage, stalled.
  2. 13 OCT 2026 09:47 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, 543 of 1,176 ten-second windows failed: http_5xx ×530, stalled ×13.

— p50‑ ‑ p95
axis 0 – 1000ms
09:12 · 13 OCT09:44 · 13 OCT10:17 · 13 OCT

A stream has no latency of its own — a feed either delivers or it does not — so this is Deribit's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.

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 179 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.