Crypto.com REST · depth degradation, 5 min on 13 SEP 2026
Crypto.com REST · depth — p95 1314ms over the last five minutes, 4.4× the 7-day baseline of 296ms — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Crypto.com's public API on 13 SEP 2026 17:44 UTC. It lasted 5 min and ended 13 SEP 2026 17:49 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, 0 of 2,326 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 13 SEP 2026 17:14 UTC to 13 SEP 2026 18:19 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.