Deribit WS · connection degradation, 4 min on 14 OCT 2026
Deribit WS — 33% of windows failing over the last minute (conn) — 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 14 OCT 2026 08:42 UTC. It lasted 4 min and ended 14 OCT 2026 08:47 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, conn.
- 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, 18 of 2,334 ten-second windows failed: conn ×18.
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 180 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.