Deribit REST · depth degradation, ongoing since 26 OCT 2026
Deribit REST · depth — p95 941ms over the last five minutes, 5.3× the 7-day baseline of 177ms — from Carlstadt, US only; 2 regions had too little evidence. up24 opened this incident from its own measurements of Deribit's public API on 26 OCT 2026 23:04 UTC. It is still open, 2h 30m in.
WHAT HAPPENED
- up24 opened the incident at degraded.
HOW IT FAILED
Over the window, 0 of 2,210 checks failed.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 26 OCT 2026 20:33 UTC to 27 OCT 2026 01:34 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 189 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 — 1 recorded transitions — and nothing on it is reported by Deribit.