Deribit REST · ticker degradation, 2 min on 20 NOV 2026
Deribit REST · ticker — p95 783ms over the last five minutes, 6.9× the 7-day baseline of 113ms — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Deribit's public API on 20 NOV 2026 15:46 UTC. It lasted 2 min and ended 20 NOV 2026 15:48 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, 388 of 2,232 checks failed: bad_body ×358, timeout ×30.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 20 NOV 2026 15:16 UTC to 20 NOV 2026 16:18 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 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 — 2 recorded transitions — and nothing on it is reported by Deribit.