← Deribit status page

Deribit REST · ping outage, 1h 30m on 18 AUG 2026

Deribit REST · ping — 25% of checks failing over the last minute (http_5xx). up24 opened this incident from its own measurements of Deribit's public API on 18 AUG 2026 09:00 UTC. It lasted 1h 30m and ended 18 AUG 2026 10:31 UTC, when the component started answering again.

OUTAGEREST · ping · https://www.deribit.com/api/v2/public/get_time
DURATION
1h 30m
STARTED
18 AUG 2026 09:00 UTC
ENDED
18 AUG 2026 10:31 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 18 AUG 2026 09:00 UTC
    up24 opened the incident at outage, http_5xx.
  2. 18 AUG 2026 10:31 UTC
    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, 1,032 of 3,251 checks failed: http_5xx ×1,032.

— p50‑ ‑ p95
axis 0 – 1000ms
07:31 · 18 AUG09:46 · 18 AUG12:01 · 18 AUG

REST latency for the failing endpoint, per minute, from 18 AUG 2026 07:30 UTC to 18 AUG 2026 12:01 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.