Crypto Status: How to Check Exchange and On-Ramp Outages

What you need before you start

You can only check your status if you have the necessary information. Please gather this information before contacting customer support, as the same information is requested in every support queue:

• The transaction hash or bank identifier—not just the amount and date.
• The exact timestamp when you initiated the transfer, both in your local time zone and in UTC.
• The recipient’s address or account number you used, to rule out the possibility of a simple typo.
• A bookmark to the exchange’s status page, which most major platforms host separately from their main marketing website, often on a subdomain.
• Access to a public blockchain explorer for the relevant network—Bitcoin, Ethereum, or any other chain through which the transfer was made.
• Your login credentials to access your account, as some status pages and all support systems require you to log in before they display your incident history or allow you to file a ticket.

The status page and online chat are designed to address different issues. On the status page, you can find out if there are any known issues with the platform itself; while in the chat or through the ticket system, you can resolve issues specifically related to your account. If you don’t check the status page first, you’ll often end up waiting in line for a support response that has already been posted.

First, you need to obtain the transaction hash and timestamp—this is the single step that will ultimately save you the most time.

Steps to check a deposit, withdrawal, or on-ramp issue

1. First, check the exchange’s status page. Look for an open incident tagged “deposit,” “withdrawal,” or one that specifies the particular network you used. A general banner stating “all systems are operational” does not mean that all transaction channels are available—some providers log incidents for individual functions rather than displaying a single, general status.
2. Verify the transaction in a public blockchain explorer using the hash you saved. If the transaction appears as confirmed on the blockchain but has not been credited to your exchange account, the delay is due to the exchange, not the network.
3. Compare the number of confirmed blocks with the required number. The transaction may be perfectly valid but remain in the queue until it meets the exchange’s own confirmation threshold, which is generally not related to any operational issues.
4. Compare the amount to the exchange’s minimum deposit. For example, Kraken specifies a minimum deposit of 1 USD. A transfer for an amount below this threshold may be included in the blockchain but simply won’t appear in your balance, which looks exactly like a stuck transfer.
5. If the transfer was in fiat currency rather than cryptocurrency, distinguish between the actions of the bank and the exchange. Bank transfers and SEPA transfers are often displayed as “processing” for reasons unrelated to the exchange—such as cut-off times, intermediary banks, or delays on the bank’s part due to regulatory compliance.
6. Check the exchange’s official social media accounts or community forum for reports of a similar issue. A platform-wide outage usually triggers a flood of similar posts within a few minutes, which is a faster indicator than waiting for the status page to refresh.
7. If none of the above explains the delay, open a support ticket, attaching the transaction hash, timestamp, and screenshots from both the blockchain explorer and your account history. Tickets without this information generally take longer to be processed.

Most delays are resolved as soon as the blockchain's processing time is separated from the exchange's processing time; it is precisely the conflation of these two factors that causes a slow transfer to be perceived as a crisis.

Fees and limits that complicate status checks

Status pages rarely explicitly mention fees or limits, but both factors influence whether a transfer appears to be “stuck,” even though it may simply not have reached the threshold yet or is currently being processed.

None of this is unique to any single provider. Related products have their own limitations, which should be checked separately—for example, Kraken Borrow applies its own limits, which are discussed in the article Kraken Borrow Launch for U.S. Users: What We Know So Far. Banking relationships also affect the processing speed of fiat transfers behind the scenes; Kraken’s parent company, Payward, is in talks with BNY Mellon, as detailed in the article BNY Mellon Is in Talks with Payward, Kraken’s Parent Company: Implications for the U.S., which addresses issues of asset custody and banking infrastructure that underpin deposit and withdrawal timelines.

A transfer whose amount is below the minimum threshold, or one received outside the designated banking window, appears to be a system error until the figures are verified.

Common problems and how to read them

Outages are not unique to any single provider. Coinbase has had its own publicized incidents, discussed in Coinbase Down? What Exchange Outages Mean for You, which is useful background for judging whether a delay pattern is normal across the industry or specific to one exchange.

If the status page is clean and the explorer shows the transaction unconfirmed, the problem sits with the network, not the platform — and no support ticket will speed that up.