← Crypto.com status page

Crypto.com WS · connection degradation, 1 min on 20 NOV 2026

Crypto.com WS — 6.7% of windows failing over the last five minutes (conn) — from Carlstadt, US and Singapore, SG. up24 opened this incident from its own measurements of Crypto.com's public API on 20 NOV 2026 00:28 UTC. It lasted 1 min and ended 20 NOV 2026 00:30 UTC, when the component started answering again.

DEGRADEDWS · connection · the shared socket
DURATION
1 min
STARTED
20 NOV 2026 00:28 UTC
ENDED
20 NOV 2026 00:30 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 20 NOV 2026 00:28 UTC
    up24 opened the incident at degraded, conn.
  2. 20 NOV 2026 00:30 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, 10 of 2,226 ten-second windows failed: conn ×10.

— p50‑ ‑ p95
axis 0 – 1000ms
23:59 · 19 NOV00:29 · 20 NOV01:00 · 20 NOV

A stream has no latency of its own — a feed either delivers or it does not — so this is Crypto.com's REST endpoints over the same window, per minute, as the median across them, measured from Lauterbourg, FR. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.

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 — 2 recorded transitions — and nothing on it is reported by Crypto.com.