Skip to content

Outage tracker / Crypto.com

Is Crypto.com down?

Short linkrlup.io/down/crypto-com

I'm having a problem

Vendor lists an old incident, not shown as liveWhat Crypto.com reports

Crypto.com still lists an incident opened on 2026-08-12 with no update since it opened; we do not show it as live.

As of the last successful poll, 2026-11-05 17:57 UTC.

Crypto.com's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 3 minutes ago

Our checks of Crypto.com pass from all 4 regions we check.

As of Nov 5, 2026, 6:03 PM UTC, RealUptime's checks of Crypto.com passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 6:03 PM UTC
US-East2584 msChecks passing
US-West2194 msChecks passing
Europe1249 msChecks passing
Asia-Pacific828 msChecks passing
their status pagetheir claim, not our reading

Crypto.com reports: All systems operational (“All Systems Operational”)

from Crypto.com's own status page, checked Nov 5, 2026, 4:33 PM UTC
Crypto.com's own status page shows no incident, and our checks of Crypto.com pass right now.

Crypto.com's own component breakdown, as they publish it

  • API ServerOperational
  • BuyOperational
  • Main PageOperational
  • NFT LoginOperational
  • Pay Your FriendsOperational
  • GiftcardOperational
  • NFT WebsiteOperational
  • SellOperational
  • Track CoinsOperational
  • AirtimeOperational
  • NFT PurchaseOperational
  • NotificationsOperational
  • SendOperational
  • Web ServerOperational
  • Checkout, Invoice, SubscriptionsOperational
  • NFT SaleOperational
  • OnboardingOperational
  • Card and StakingOperational
  • NFT WithdrawOperational
  • RefundsOperational
  • WithdrawalsOperational
  • WithdrawalsOperational
  • DepositsOperational
  • DepositsOperational
  • Merchant DashboardOperational
  • NFT DepositOperational
  • Exchange AppOperational
  • Fiat WalletsOperational

These are Crypto.com's components, named and scored by Crypto.com. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Crypto.com's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Crypto.com response time, by region

US-East
2.0sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
US-West
2.6sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
Europe
2.7sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
Asia-Pacific
2.4sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5

Check your own site while you wait on Crypto.com

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Crypto.com. It cannot diagnose Crypto.com's own systems.

What we measured, function by function

Crypto.com answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region

Email me when Crypto.com reports an incident on its status page, and again when it reports it resolved.

Get an email when Crypto.com reports an incident

Email me when Crypto.com reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Crypto.com's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 2584msstatus code: 200checked: Nov 5, 2026, 6:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Crypto.com normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 2194msstatus code: 200checked: Nov 5, 2026, 6:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Crypto.com normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionCrypto.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionCrypto.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionCrypto.com is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 1249msstatus code: 200checked: Nov 5, 2026, 5:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Crypto.com normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionCrypto.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 828msstatus code: 200checked: Nov 5, 2026, 5:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Crypto.com normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionCrypto.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionCrypto.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Crypto.com, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Crypto.com yet, which is not evidence that nothing is wrong.

Recent probe events

Predictions trading disruption for Crypto.com Main App users, 2h 18mdeclared on their status page2026-11-02
Deposits / Withdraws of DBG token have been paused temporarily, 13mdeclared on their status page2026-11-02
PayPal Service Disruption for EEA Users, 92h 58mdeclared on their status page2026-10-29
OSMO Staking Temporary Service Disruption, 23h 35mdeclared on their status page2026-10-29
Main App Users experiencing Intermittent Passkey Errors During Crypto Withdrawals, 37mdeclared on their status page2026-10-21
TIA staking rewards temporarily paused, 49h 7mdeclared on their status page2026-10-20
Delays in Standard Chartered AED bank processing, 69h 39mdeclared on their status page2026-10-19
Crypto.com Main App Web login Issues, 10mdeclared on their status page2026-10-15

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Crypto.com since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Crypto.com covering any window you pick, with our check readings and Crypto.com's own claim at the time, side by side.

Full check history for Crypto.com: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Crypto.com uptime by RealUptime's checksLive, from this page's own readings.
[![Crypto.com uptime by RealUptime's checks](https://realuptime.io/outages/crypto-com/badge.svg?days=30)](https://realuptime.io/outages/crypto-com)
<a href="https://realuptime.io/outages/crypto-com"><img src="https://realuptime.io/outages/crypto-com/badge.svg?days=30" alt="Crypto.com uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Crypto.com down?", https://realuptime.io/outages/crypto-com. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.crypto.com/exchange/v1/public/get-tickers?instrument_name=BTC_USD
secondary
https://crypto.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.crypto.com

RealUptime is not affiliated with Crypto.com; the name identifies what we checked, and nothing here speaks for Crypto.com's own team. We send a single web request to Crypto.com from 4 regions on our own schedule and time the response. We do not see inside Crypto.com's systems, do not use an account or real transaction, and are not the same signal Crypto.com's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Crypto.com is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Crypto.com operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 2560 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

ANZAbsa GroupAdyenAffirmAfterpay