Deribit REST · ticker degradation, 50s on 31 AUG 2026
Deribit REST · ticker — 25% of checks failing over the last minute (bad_body) — from Lauterbourg, FR and Carlstadt, US — re-graded on 12 Sep 2026: an outage grade now needs two minutes, and this lasted 50 seconds. up24 opened this incident from its own measurements of Deribit's public API on 31 AUG 2026 08:00 UTC. It lasted 50s and ended 31 AUG 2026 08:01 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, bad_body.
- 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, 8 of 2,192 checks failed: bad_body ×8.
REST latency for the failing endpoint, per minute, from 31 AUG 2026 07:30 UTC to 31 AUG 2026 08:31 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.