Deribit REST · depth degradation, 3 min on 19 NOV 2026
Deribit REST · depth — 6.7% of checks failing over the last five minutes (timeout) — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 19 NOV 2026 15:40 UTC. It lasted 3 min and ended 19 NOV 2026 15:43 UTC, when the component started answering again.
WHAT HAPPENED
- up24 saw Deribit's own status flag switch on, at its poll.
- up24 opened the incident at degraded, timeout.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
- up24 saw Deribit's status flag switch off, at its poll.
HOW IT FAILED
Over the window, 16 of 2,268 checks failed: timeout ×16.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 19 NOV 2026 15:10 UTC to 19 NOV 2026 16:13 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 · 16 NOV 2026 10:21 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 — 4 recorded transitions — and nothing on it is reported by Deribit.