Kraken Disruption on the September 11 Delisting Date: How to Check Whether Your Coin Can Still Be Withdrawn

When a crypto exchange reports that deposits and withdrawals are “delayed”, it sounds like a footnote. At Kraken it has turned this week into a condition that has now lasted seven days, and that falls on this particular day together with a deadline that is final for one of the affected tokens. The short answer to the question of what you have to do: check today whether your coin is listed as disrupted on the exchange's status page, and do not rely on what the trading view shows you. Both sources come from Kraken, and they contradict each other.

This analysis was carried out by cryptoticker.io on September 11, 2026. We pulled the exchange's public status page and its public market data interface on the same morning and compared them line by line. What came out of it appears in no announcement by the exchange.

What Kraken Reports as a Funding Incident and What It Means for Your Account

Funding is the umbrella term at a crypto exchange for everything that brings balance onto the account or takes it off again: deposits from your own wallet, withdrawals to your own wallet, plus transfers in euros or dollars. Trading itself is expressly not part of it. That very separation explains why the current situation feels so harmless: prices are running, charts are updating, buying and selling work. Only the way out is blocked for part of the networks.

Kraken keeps a separate entry for every single network on its public status page. Such an entry can take four states, and the most important dividing line runs between “operational” and everything else. Where it says degraded performance, it means in the language of the exchange: the gateway for this network is working, but not reliably. A withdrawal may go through, it may take hours, it may get stuck. No commitment as to when the condition ends comes with it.

Disrupted Since September 4: 19 Networks From the Cosmos Ecosystem

The incident at issue carries the title “Funding delays for select blockchain networks” at Kraken and was opened on September 4, 2026 at 21:43 UTC. It names 19 affected networks: Akash (AKT), Babylon (BABY), Celestia (TIA), Cosmos (ATOM), dYdX (DYDX), Dymension (DYM), Fetch.ai (FET), Initia (INIT), Injective (INJ), Juno (JUNO), Kava (KAVA), Mantra (MANTRA), Neutron (NTRN), Osmosis (OSMO), Saga (SAGA), Secret Network (SCRT), Sei (SEI), Terra Classic (LUNA) and THORChain (RUNE).

That list has a pattern you should not miss. Almost all the chains named belong to the Cosmos ecosystem or speak its transfer protocol. That points to a shared technical cause in the connection path rather than 19 independent failures on the same evening. Kraken itself has published nothing on the cause to date. Eight status updates since September 4 contain essentially the same sentence: work on a solution continues. The most recent of those updates is dated September 10, 12:33 UTC.

The incident still sits at the processing state “identified”. That means the cause is known to the exchange and the fix is in progress. This state names no target date, and Kraken has not supplied one since.

Our Own Analysis: 725 Funding Services Checked, Nine Flagged as Disrupted

For this article we pulled the status page on September 11, 2026 at around 12:55 UTC via its public data interface. The page timestamp reported in the response itself is 12:29:12 UTC on the same day. The analysis covers 831 entries spread across seven areas. By far the largest of them is “Digital Currency Funding” with exactly 725 individual services, meaning one entry for every combination of coin and network.

Of those 725 services, nine were not on “operational” at the moment we pulled the data. Sorted by the time since which each entry has been flagged as disrupted:

• Stablr Euro (EURR) and Stablr USD (USDR) on Ethereum: both since August 12, 2026. The associated incident reaches back further: it was opened on May 24, 2026, after a problem occurred in the underlying smart contract. Kraken suspended deposits and withdrawals for both tokens and set the markets to “post only”.
• MemeCore (M) on BNB Chain: since August 19, 2026, 08:20 UTC. Here the exchange released withdrawals again after a few hours and instead switched off deposits as a precaution.
• Fetch.ai (FET), Juno (JUNO), Mantra (MANTRA), Osmosis (OSMO) and THORChain (RUNE): all since September 4, 2026, 21:43 UTC, so for exactly one week.
• Polkadot (DOT): since September 11, 2026, 10:05 UTC, the morning of this article.

What is remarkable about this list is less its length than what is missing from it. Of the 19 networks the September 4 incident originally named, only five are flagged as disrupted today. Cosmos (ATOM), Celestia (TIA), Injective (INJ), Sei (SEI) and ten others are back on “operational”, while the incident itself formally stays open. Anyone reading only the incident notice therefore assumes 19 networks are affected, while by our measurement it is five. The reliable information sits in the individual service entries, not in the headline above them.

One limit of this survey belongs with it: it is a snapshot of a single data pull. It says nothing about how many withdrawals were actually delayed, how long an individual transaction took and how many customers were affected. Only the exchange has those figures, and it does not publish them.

Polkadot (DOT) Since This Morning: The Second, Separate Incident

The Polkadot entry is not part of the Cosmos disruption but an incident of its own with its own notice. Kraken opened it today at 10:05 UTC: it was investigating a problem with the Polkadot funding gateway, deposits and withdrawals might be delayed, all other funding methods were working normally. At 11:14 UTC came the follow-up that the cause had been found and a fix was being deployed.

That is the usual course of events, and in most cases such an entry has disappeared again after a few hours. It is still relevant to you, because it shows how quickly a network can slip into this state. Anyone who checked yesterday evening whether DOT was withdrawable had a green display in front of them. This morning that answer no longer holds.

Why the Trading Interface Reports “enabled” While the Status Page Shows a Disruption

Alongside the status page, Kraken runs an open market data interface that keeps a status entry for every tradable asset. We pulled it in the same working step: 843 entries, of which 841 carry the note “enabled”. Only two assets, ANSEM and NATG, sit there on “withdrawal_only”, meaning they may be withdrawn but not deposited.

JUNO shows as “enabled” in that interface. So do FET, MANTRA, OSMO, RUNE and DOT. The same exchange, the same minute, two opposing statements about the same coin.

Technically that is not a contradiction, because the two systems answer different questions. The market data interface describes whether an asset is generally cleared for trading. The status page describes whether the gateway to the respective network is working right now. In practice the difference is awkward all the same, because many portfolio trackers, trading apps and tax tools read their status information from the market data interface. Anyone relying on that gets a completely unremarkable display for a disrupted coin. The disruption is simply not provided for in these tools.

The JUNO Case: A Delisting Deadline Meets a Broken Withdrawal Gateway

Two processes converge here that are each known on their own and together add up to a problem. At the end of August, Kraken announced that it would remove 21 assets from its offering. Affected are XTER, IR, GAIA, SCA, VANRY, BNC, SBR, RBC, MIR, JUNO, HDX, ACA, MULTI, RIZE, EPT, MAT, CQT, CXT, BKS, VULT and M. The dates are set out in the exchange's notice and are unambiguous: deposits and trading end on September 11, 2026 at 14:00 UTC, withdrawals on December 10, 2026 at 15:00 UTC. Whatever is still sitting in the account after that, Kraken sells itself between December 14 and 18.

The exchange states the consequence of that sale unusually plainly. Several of the affected assets have only thin or inactive markets left, it says, so the proceeds could be well below the prices last seen and in some cases minimal or zero. That is not our reading; it is what the delisting notice says.

Two names from that list now also appear in our disruption analysis: JUNO has been flagged as disrupted since September 4, MemeCore (M) since August 19. For JUNO that means in concrete terms: trading ends today at 14:00 UTC, so the convenient route of simply selling the position and leaving the proceeds in euros falls away. What remains is the withdrawal to your own wallet, and that runs through exactly the gateway that has been flagged as disrupted for a week. Anyone who does not get that withdrawal through by December 10 ends up in the automatic disposal.

Three months is a lot of time for that, and the disruption will in all likelihood be fixed long before. Even so, it is the difference between a task you handle today in five minutes and one you have to sort out with customer support in December under time pressure. For MemeCore (M) the situation is more relaxed: there, according to the status notice, only deposits are switched off, while withdrawals were released again on the same day.

Checking the Funding Status Yourself: The Two Addresses You Need

The good news about this case is that you need neither an account nor a tool for the check. Kraken puts its status page openly on the web, and it is readable in a browser. At status.kraken.com you will find the “Digital Currency Funding” area with the 725 individual services. There you look for the name of your coin and read off the state next to it. Anything other than “operational” is a reason not to leave your withdrawal until the last day.

The second address is the exchange's own delisting notice. It sits at support.kraken.com and names the affected assets along with all three dates. You can open both pages without signing in, and both are the position the exchange commits to itself.

This check is not a Kraken peculiarity. Almost every larger exchange runs a page of this kind, and in a separate analysis of several exchange status pages on September 7 we showed how differently detailed these pages are kept. Anyone regularly active on several venues should bookmark the relevant addresses once. Which venues offer that kind of transparency at all is, incidentally, a usable selection criterion and feeds into our crypto exchange comparison.

Stablr USD and Stablr Euro: When a Disruption Lasts Three Months

The oldest open entry in our analysis is also the most uncomfortable one. On May 24, 2026, Kraken suspended deposits and withdrawals for the two stablecoins Stablr USD (USDR) and Stablr Euro (EURR), because a problem had occurred in the underlying smart contract. In the same breath the exchange stated that there was no indication its own wallets or systems were affected, and set the markets to “post only”. The last substantive status update on this is dated July 1, 2026 and says work on a solution continues.

That leaves this incident open for more than three and a half months. For a stablecoin, a token whose entire purpose is to be redeemable one to one against a currency at any time, that is a remarkable condition. It shows that “temporarily suspended” is a very elastic statement at an exchange. There is no deadline by which an exchange would have to resolve such a state.

What “degraded performance” Does Not Mean Legally at an Exchange

A status notice is operational information, not a commitment. No entitlement to a withdrawal within a particular period follows from the entry “degraded performance”, and it is not an admission of fault either. Conversely, “operational” does not mean that an individual withdrawal will go through; it can get stuck for entirely different reasons, such as a source-of-funds check or a missing approval on your side.

This distinction matters so that you hold the right expectation. The status page tells you whether a known problem exists. It does not tell you when it will be fixed, and it does not replace a query to customer support when a specific transaction is stuck.

Withdrawal Stuck: These Steps, in This Order

If a withdrawal is not going through for you right now, work through the following order before you write to customer support. It costs a few minutes and answers most cases.

Network Status First, Everything Else After

Check on the status page whether your coin or your chosen network is listed as disrupted. Many coins can be withdrawn over several chains, and the entries differ: a token can run normally on Ethereum and stand still on a second chain. If the entry is disrupted, your withdrawal is as a rule still sitting in the queue and is not lost.

Check Whether Another Network Is Open

If your preferred route is flagged as disrupted but another one is on “operational”, you can often simply switch the withdrawal route. Make sure that your receiving wallet really supports the chain you choose. A withdrawal to an address on the wrong chain is the most expensive mistake in this whole process and is usually not recoverable.

Only Then Support and Documentation

If the status stays green and your withdrawal is stuck anyway, the cause most likely lies with your account rather than with the network. Then it is a matter of approvals, checks or a stored withdrawal address. How to secure that route in advance is something we have described using the example of the withdrawal whitelist.

Move Delisted Tokens in Time Instead of Letting Them Be Liquidated

For the 21 assets whose trading ends today at 14:00 UTC, a logic of their own applies. After the trading halt only the transfer remains. Where to depends on the token: some remain listed on other venues, others practically nowhere. Which routes exist for this and what to watch out for during the transfer is set out in our piece on delisted tokens and fallback exchanges. The announcement itself and its dates we wrote up in our coverage of the trading halt for 21 tokens.

Anyone shying away from the effort should take the exchange's warning seriously that the disposal proceeds in December may be minimal or zero. With a holding of a few euros that is a defensible decision. With a position of any size it is not.

What This Case Says About Custody on an Exchange

The actual lesson of this episode has little to do with Kraken. As long as your coins sit on a trading venue, your access depends on that venue's infrastructure. If a gateway is not running, your balance is there, visible and tradable, but it does not come out. That is no accusation against a single exchange but a property of custody with a third party.

No panic follows from this, and no immediate withdrawal of all holdings. What follows is a split: what you actively trade belongs on the trading venue. What you want to hold for longer belongs in custody that nobody else has a switch for. Which devices come into question for that and how they differ is set out in our hardware wallet comparison, linked in the final section.

Checking Kraken's Funding Status: What to Take Away

1. Check today whether your coin is affected. Open the “Digital Currency Funding” area on the status page and look for your asset. If it says anything other than “operational”, do not plan your withdrawal for the last day. Where else you can trade is set out with the respective providers in our exchange comparison.
2. If you hold one of the 21 delisted assets, act before 14:00 UTC. After that, selling is no longer possible and only the withdrawal until December 10 remains. For JUNO that route currently runs through a disrupted gateway. Whether your venue is supervised at all is answered by a look at the comparison of regulated crypto exchanges.
3. Separate your trading holdings from your long-term holdings. What you do not move does not have to sit on the exchange. The right custody for the dormant part is set out in our hardware wallet comparison.

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