Deribit REST · depth degradation, 3 min on 16 OCT 2026
Deribit REST · depth — p95 873ms over the last five minutes, 5.6× the 7-day baseline of 157ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 16 OCT 2026 18:01 UTC. It lasted 3 min and ended 16 OCT 2026 18:05 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- 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, 0 of 2,302 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 16 OCT 2026 17:31 UTC to 16 OCT 2026 18:35 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 182 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.