CRY
Crypto.com API status
OPERATIONALBTC_USDT · api.crypto.com · 3 REST endpoints · 2 streams
UPTIME · 90D
100.00%
TYPICAL P50 · 24H
268ms
TYPICAL P95 · 24H
286ms
INCIDENTS · 90D
0
UPTIME · LAST 90 DAYS · ALL REST ENDPOINTS
■ operational■ degraded■ outage■ not measured
16 MAY29 JUN13 AUG
— p50‑ ‑ p95
axis 0 – 2000ms09:00 · 13 AUG10:10 · 13 AUG11:20 · 13 AUG
REST ENDPOINTS · LAST 24H
| ENDPOINT | P50 | P95 | UPTIME | STATUS |
|---|---|---|---|---|
REST · ping 1,649 checks · api.crypto.com | 271ms | 403ms | 100.00% | OPERATIONAL |
REST · ticker 1,649 checks · api.crypto.com | 270ms | 415ms | 100.00% | OPERATIONAL |
REST · depth 1,649 checks · api.crypto.com | 269ms | 332ms | 100.00% | OPERATIONAL |
WEBSOCKET STREAMS · LAST 24H
| STREAM | CONNECTED | DELIVERING | MESSAGES | MAX GAP | SEQ GAPS | RECONNECTS | RTT | STATUS |
|---|---|---|---|---|---|---|---|---|
WS · trade trade.BTC_USDT | 100.00% | 100.00% | 3,363 | 124629ms | — | 0 | 248ms | OPERATIONAL |
WS · book book.BTC_USDT.10 | 100.00% | 100.00% | 28,005 | 5093ms | 0 | 0 | 248ms | OPERATIONAL |
INCIDENT HISTORY · 90D
No incidents recorded for Crypto.com in the last 90 days.
Incidents are opened by up24's own state machine over its own measurements, not by Crypto.com's status page.
CRYPTO.COM SAID · 90D
No up24 incidents for Crypto.com in the last 90 days, so there is nothing to compare against their announcements.
- no end published
- no end published
- 02 AUG 2026 04:49 UTC → 02 AUG 2026 08:03 UTC
- 31 JUL 2026 05:32 UTC → 31 JUL 2026 07:03 UTC
- 23 JUL 2026 07:41 UTC → 24 JUL 2026 05:20 UTC
- 07 JUL 2026 15:33 UTC → 08 JUL 2026 03:28 UTC
- 25 JUN 2026 18:37 UTC → 26 JUN 2026 01:37 UTC
- no end published
- 28 MAY 2026 15:20 UTC → 29 MAY 2026 07:10 UTC
- 27 MAY 2026 07:11 UTC → 11 JUN 2026 07:44 UTC
- 22 MAY 2026 07:59 UTC → 22 MAY 2026 13:12 UTC
- 18 MAY 2026 16:09 UTC → 17 JUL 2026 07:36 UTC
- 15 MAY 2026 14:07 UTC → 27 MAY 2026 04:31 UTC
Read from status.crypto.com every 5 minutes. Times are the venue’s own.