Deribit REST · depth degradation, 30s on 25 SEP 2026
Deribit REST · depth — 22% of checks failing over the last minute (timeout) — from Singapore, SG 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 25 SEP 2026 12:17 UTC. It lasted 30s and ended 25 SEP 2026 12:18 UTC, when the component started answering again.
WHAT HAPPENED
- 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.
HOW IT FAILED
Over the window, 5 of 2,186 checks failed: timeout ×5.
REST latency for the failing endpoint, per minute, from 25 SEP 2026 11:47 UTC to 25 SEP 2026 12:48 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 173 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.