Withdrawals suspended: what 136 incidents on nine crypto exchange status pages reveal about your coins

When you try to move your balance off a crypto exchange and it does not work, it is rarely because the whole exchange is down. Far more often a single coin is affected: deposits and withdrawals for one network are paused while trading, login and the app carry on as usual. That is exactly why you notice nothing until you are in a hurry.

We counted how often this actually happens. Between August 1 and September 7, 2026, nine public status pages run by trading venues and wallet providers reported 136 incidents between them. 63 of those, or 46.3 percent, involved deposits or withdrawals. Fourteen of these suspensions were still open on September 7 at 15:50 UTC, the oldest since August 10.

This analysis was compiled by cryptoticker.io itself on September 7, 2026.

136 incidents in 38 days: what nine crypto exchange status pages reported in August

A status page is a provider's public fault list: the company itself records which part of its service is not working, since when and how badly. Almost every large trading venue runs one, and almost all of them also publish it as a machine-readable interface. It is barely read all the same, because it only becomes interesting once something is stuck.

This is how the 136 incidents were distributed across the measurement window:

• Coinbase: 38 incidents, 1 of them still open, 22 related to deposits or withdrawals
• Kraken: 36 incidents, 5 of them still open, 25 related to deposits or withdrawals
• Bitvavo: 20 incidents, 4 of them still open, 6 related to deposits or withdrawals
• Ledger: 19 incidents, all closed, none related to deposits or withdrawals
• Gemini: 9 incidents, 1 of them still open, 5 related to deposits or withdrawals
• Crypto.com: 6 incidents, 3 of them still open, 3 related to deposits or withdrawals
• Bitstamp: 4 incidents, all closed
• Bitpanda: 3 incidents, all closed, none related to deposits or withdrawals
• Blockchain.com: 1 incident, closed

These figures are explicitly not a reliability ranking. They measure first how thoroughly a house documents its own problems, and only then how many it has. How to tell the two apart is covered further down.

How we counted: method, time window and the limits of the measurement

The method in one sentence: on September 7, 2026 we called the public incident interface of nine status pages, restricted all entries to the window from August 1, 2026 to September 7, 2026, 15:50 UTC, and counted the number, severity, run time and deposit or withdrawal impact for each provider.

Objects checked: nine status pages carrying 136 incidents between them inside the window. The pages retrieved were those of Kraken, Coinbase, Bitpanda, Bitvavo, Bitstamp, Crypto.com, Gemini, Blockchain.com and Ledger, each with HTTP 200.

The time window is no accident. The interface returns at most 50 incidents per page, and at the two busiest houses that list only reaches back to July 26 and July 18 respectively. A longer window would have delivered truncated figures for Kraken and Coinbase and complete ones for Bitpanda. August 1 is the earliest cut-off date on which all nine pages are covered without gaps.

What we could not check belongs to the survey as well: Binance serves no readable status page at the address we tested (HTTP 404), OKX, Bitfinex and MetaMask were unreachable from the measurement environment, Trezor redirects. For Bison and Trade Republic no public status page could be found at the addresses we checked. The analysis therefore says nothing about these providers, good or bad.

Also not covered: scheduled maintenance windows. The interface lists them separately from incidents, and announced maintenance is a different matter from an unplanned suspension.

Almost every second incident hits deposits and withdrawals, not trading

The most important finding of the count is the distribution. 63 of the 136 incidents involved deposits or withdrawals, the moving of balances. For trading itself the number was markedly lower. That inverts the widespread assumption that an exchange problem is above all a problem for traders.

For you as a holder, the withdrawal side is the more critical one. If trading is stuck, you miss a price. If the withdrawal is stuck, you cannot reach your balance at all, for as long as the provider needs. Among the incidents analysed that was often more than an afternoon: 14 closed suspensions inside the window ran longer than 72 hours.

The cause usually lies outside the exchange. If a blockchain jams after a hard fork, if a network is halted or if there are signs of an attack, a trading venue freezes deposits and withdrawals for exactly that network and lets everything else run. From the provider's point of view that is the right call; in practical terms it works on you like a lockout.

Fourteen withdrawal suspensions are still running: which coins are not leaving the exchange right now

On September 7, 2026 at 15:50 UTC, 14 of the analysed incidents were still listed as unresolved. The longest of them, by run time from the start of the entry:

1. RVN at Bitvavo, deposits and withdrawals suspended since August 10, according to the entry because of a security incident. Run time around 669 hours, a good 27 days. The only open case rated at the severity "major".
2. ONE at Bitvavo, entry standing since August 12 in connection with a security incident at Harmony. Around 635 hours.
3. ONE, ORAI and RAVEN at Crypto.com, deposits and withdrawals suspended since August 12. Around 632 hours.
4. Toncoin at Gemini, deposits, withdrawals and trading unavailable since August 17. Around 497 hours. Anyone holding TON there has been unable to reach the position for three weeks.
5. Memecore (M) at Kraken, deposits disabled since August 19. Around 463 hours.
6. NES at Bitvavo and at Kraken, in each case since August 24, around 337 hours.
7. TON staking at Crypto.com, since August 26, around 297 hours.
8. Cronos (CRO) at Kraken, disruptions to deposits and withdrawals since August 30, around 192 hours.

Shorter open entries come on top of that: Monad (MON) at Kraken since September 2, a collective notice about delays on selected networks at Kraken since September 4, halted trading for Core (CORE) at Bitvavo since September 4, a restricted derivatives display at Coinbase since September 3 and a collective deposit suspension covering several assets at Crypto.com dated September 7.

The list is a snapshot and ages quickly. Its value lies in the order of magnitude rather than in the individual names: at every point in the measurement window a double-digit number of deposit and withdrawal routes was closed somewhere, and the run times were measured in weeks.

Why a high incident count at Kraken and Coinbase does not make them the worse exchange

Coinbase and Kraken lead the count with 38 and 36 entries, Bitpanda stands at three. Concluding from that that Bitpanda runs twelve times more stably would be a measurement error. Both houses at the top maintain a very fine-grained status page with several hundred individually monitored components, and they record every delay on a single network there. Whoever records less looks better in this statistic.

What carries meaning is therefore the type of entry rather than the volume. At Kraken, 32 of the 36 entries were rated "minor" and four "none", the two lowest levels. At Coinbase, 22 entries were "none" and 16 "minor". Bitstamp reported only four incidents in the same period, two of them at the highest severity "critical" and two at "major". Four severe disruptions can hit you harder than 38 documented trifles.

So if you are picking an exchange for reliability, the raw incident count helps you little. Three other questions are more useful: does the provider run a public status page at all, does it record uncomfortable cases there too, and how long do its entries stay open? Our crypto exchange comparison places fees, product range and regulation in context; the status page is the addition that tells you how a house communicates when something breaks.

What "none", "minor", "major" and "critical" mean on a status page

The four levels are an industry standard and are assigned by the provider itself. "none" marks pure information without noticeable restriction, "minor" a limited disruption of individual functions, "major" a substantial impairment and "critical" an outage of the core service. The rating is self-reported and not an audited metric. An entry filed as "none" can still hit you hard if it happens to affect exactly the coin you want to move. At Crypto.com all six entries in the measurement window ran under "none", among them a staking disruption lasting around 314 hours.

When a withdrawal suspension and a migration deadline collide: the Harmony case

In practical terms the most dangerous finding of the count is an overlap. At Crypto.com, deposits and withdrawals for ONE have been suspended since August 12; at Bitvavo an entry about a security incident at Harmony has stood since the same day. At the same time a deadline is running for ONE holders: as we reported on September 7, 2026, Harmony is shutting down its mainnet, and the details are in our piece Harmony is shutting down its mainnet.

For you that means a deadline keeps running even while the route to your balance is closed. No migration plan waits for a trading venue to reopen its withdrawals. Anyone relying on handling the swap shortly before the end has no buffer for a suspension that nobody announced.

The same constellation threatens with every migration under way. For ICX, for instance, we described two deadlines ahead of the shutdown of the ICON blockchain on August 17, 2026; at Bitvavo an entry about a security incident at Icon additionally ran between August 27 and the start of September. When a suspension and a cut-off date overlap, you lose more than time: you lose the option.

What a status page does not show: the blind spots of the measurement

A status page is self-reporting, and it has systematic gaps. First, it shows only what the provider records. Second, it says nothing about the cause: whether a suspension goes back to a problem on the blockchain, to an order from a supervisory authority or to an internal decision is rarely stated there. Third, it says nothing about the solvency of the house. A provider can keep an immaculate status page and still get into difficulty.

For Bitpanda with three entries, Blockchain.com with one and Bitstamp with four, the same caveat therefore applies as for the leaders, only in the other direction: the low number can speak for a quiet house or for a coarse-grained status page. That cannot be decided from the number alone, and we make no such claim.

At Ledger, the only wallet manufacturer in the selection, the picture looks different from the trading venues: 19 entries, 14 of them at "major" and two at "critical", but none related to deposits or withdrawals. The entries almost all concern the connection to individual blockchains inside the application. The longest ran around 22 hours. With a hardware wallet that affects you differently than at an exchange, because your keys stay in your possession the entire time.

Check the status page before you sell: the three signals that matter

From the count a short check routine can be derived that protects you from the most expensive surprise: the sale that cannot be paid out.

First signal, the component. On the status page, look for the name of your coin or its network, and not for the name of the exchange. The relevant notice is almost never headed "exchange disrupted"; it carries a ticker in the title.

Second signal, the start date. An entry from this morning is usually settled within hours. An entry that has stood open for three weeks will still be open tomorrow. In our count the median run time of the open cases was over a week.

Third signal, the direction. Check whether the entry names deposits, withdrawals or both. For you the withdrawal almost always counts. A blocked deposit costs you an entry point, a blocked withdrawal costs you access.

If you do not want to run this check every time, there is a more sensible way to shift the problem: a balance you are not actively trading sits in self-custody, out of reach of anyone else's withdrawal suspensions. Which devices come into question for that and what sets them apart is covered in our hardware wallet comparison further down. The price is that you carry responsibility for the keys yourself.

Why you subscribe to the status page instead of visiting it

All nine pages checked offer notification by email or RSS, in most cases per component as well. That is the real benefit: you learn about a suspension when it starts, and not in the moment you want to sell. For assets with a swap deadline running, such a subscription is the cheapest insurance available in this field.

Security incident, network problem or maintenance: how to gauge how long a suspension lasts

The count shows a pattern in the run times. Entries describing a technical delay were as a rule settled within hours to a few days; the longest closed delay of this kind ran around 146 hours at Kraken. Entries citing a security incident on the blockchain as the trigger ran considerably longer. The longest closed case in this category stood open at Bitvavo for around 598 hours, just under 25 days.

The explanation suggests itself: a delay ends when the technology works again. A security-driven suspension ends only once somebody has judged whether the chain can be trusted again, and that judgement often does not sit with the trading venue at all. If you read the words security incident in an entry, count on weeks and not on days.

One limitation belongs with this: the observation rests on 38 days and nine pages. It is a pattern inside this window and no robust rule spanning years. We will re-check it in coming analyses.

Checking crypto exchange status pages: what to take away

1. Check your provider's status page before every planned withdrawal, and specifically for the ticker of your coin. Whether your provider runs a public and maintained status page at all is a selection criterion in itself; which houses are licensed and supervised in the EU is shown in our overview of regulated crypto exchanges.
2. Move holdings you are not actively trading off the exchange before you need them. A withdrawal suspension only hits a balance that is still sitting with the provider. Suitable devices and their differences are in the hardware wallet comparison.
3. Handle swap and migration deadlines with a buffer, not on the last day. When a suspension and a cut-off date coincide, the cut-off date wins. If you want to move your balance to another trading venue anyway, the alternatives and their fees are in the crypto exchange comparison.

(As of September 7, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)

The raw data for this analysis comes from the providers' public status pages, such as the Kraken status page and the Bitvavo status page. Both pages are freely accessible and can be re-checked at any time.