← Crypto.com status page

Crypto.com REST · ping outage, 3 min on 11 SEP 2026

Crypto.com REST · ping — 100% of checks failing over the last minute (timeout) — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Crypto.com's public API on 11 SEP 2026 00:06 UTC. It lasted 3 min and ended 11 SEP 2026 00:10 UTC, when the component started answering again.

OUTAGEREST · ping · https://api.crypto.com/exchange/v1/public/get-valuations?instrument_name=BTCUSD-INDEX&valuation_type=index_price&count=1
DURATION
3 min
STARTED
11 SEP 2026 00:06 UTC
ENDED
11 SEP 2026 00:10 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 11 SEP 2026 00:06 UTC
    up24 opened the incident at degraded, timeout.
  2. 11 SEP 2026 00:06 UTC
    up24 raised it to outage — the same incident, not a second one.
  3. 11 SEP 2026 00:10 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, 3 of 1,525 checks failed: timeout ×398.

— p50‑ ‑ p95
axis 0 – 2000ms
23:37 · 10 SEP00:08 · 11 SEP00:40 · 11 SEP

REST latency for the failing endpoint, per minute, from 10 SEP 2026 23:36 UTC to 11 SEP 2026 00:40 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 — 3 recorded transitions — and nothing on it is reported by Crypto.com.