← Crypto.com status page

Crypto.com REST · ping degradation, 50s on 20 AUG 2026

Crypto.com REST · ping — p95 1237ms over five minutes, 4.2× the 7-day baseline of 295ms. up24 opened this incident from its own measurements of Crypto.com's public API on 20 AUG 2026 14:30 UTC. It lasted 50s and ended 20 AUG 2026 14:31 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api.crypto.com/exchange/v1/public/get-valuations?instrument_name=BTCUSD-INDEX&valuation_type=index_price&count=1
DURATION
50s
STARTED
20 AUG 2026 14:30 UTC
ENDED
20 AUG 2026 14:31 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 20 AUG 2026 14:30 UTC
    up24 opened the incident at degraded.
  2. 20 AUG 2026 14: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 of 732 checks failed: timeout ×1.

— p50‑ ‑ p95
axis 0 – 2000ms
14:01 · 20 AUG14:31 · 20 AUG15:01 · 20 AUG

REST latency for the failing endpoint, per minute, from 20 AUG 2026 14:00 UTC to 20 AUG 2026 15:01 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 70 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.