Crypto.com REST · depth degradation, 3 min on 23 AUG 2026
Crypto.com REST · depth — p95 1323ms over five minutes, 4.5× the 7-day baseline of 296ms — from every region. up24 opened this incident from its own measurements of Crypto.com's public API on 23 AUG 2026 15:31 UTC. It lasted 3 min and ended 23 AUG 2026 15:35 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- 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 1,535 checks failed: timeout ×1.
REST latency for the failing endpoint, per minute, from 23 AUG 2026 15:01 UTC to 23 AUG 2026 16:05 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.