Crypto.com WS · trade degradation, 23 min on 16 AUG 2026
Crypto.com WS · trade — intermittently degraded: 2 episodes. up24 opened this incident from its own measurements of Crypto.com's public API on 16 AUG 2026 07:59 UTC. It lasted 23 min and ended 16 AUG 2026 08:22 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, stalled.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.
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. 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 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.