← Crypto.com status page

Crypto.com REST · depth outage, 11 min on 18 NOV 2026

Crypto.com REST · depth — 100% of checks failing over the last minute (http_4xx) — from every region. up24 opened this incident from its own measurements of Crypto.com's public API on 18 NOV 2026 09:35 UTC. It lasted 11 min and ended 18 NOV 2026 09:46 UTC, when the component started answering again.

OUTAGEREST · depth · https://api.crypto.com/exchange/v1/public/get-book?instrument_name=BTC_USDT&depth=20
DURATION
11 min
STARTED
18 NOV 2026 09:35 UTC
ENDED
18 NOV 2026 09:46 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 18 NOV 2026 09:35 UTC
    up24 opened the incident at degraded, http_4xx.
  2. 18 NOV 2026 09:37 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 18 NOV 2026 09:46 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, 179 of 2,448 checks failed: http_4xx ×178, http_429 ×1; skipped while up24 backed off after a 429: 108.

— p50‑ ‑ p95
axis 0 – 1000ms
09:06 · 18 NOV09:41 · 18 NOV10:16 · 18 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 18 NOV 2026 09:05 UTC to 18 NOV 2026 10:16 UTC. The gap in the line is where nothing answered.

DID CRYPTO.COM SAY SO?

Crypto.com 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 23 incidents for Crypto.com in the last 90 days. Nothing Crypto.com published lines up with any of them.

CRYPTO.COM — OTHER INCIDENTS

Measured by up24's own probe against Crypto.com's public API, BTC_USDT against USDT, every 5s. This page is generated from the incident's own rows — 3 recorded transitions — and nothing on it is reported by Crypto.com.