Fri. Sep 11th, 2026

Kraken Withdrawal-Hold Complaints Cluster as One User Reports Two-Week Release

ByShane Neagle

September 11, 2026 #Kraken
Crypto Exchange KrakenCrypto Exchange Kraken

Users Report Reviews Running Beyond Kraken’s Five-Day Guidance

A small cluster of Kraken users is reporting cryptocurrency withdrawals remaining under manual review for considerably longer than the exchange’s stated five-business-day communication window, although a separate customer said Friday that two withdrawals were finally released after roughly two weeks.

The complaints do not currently point to a platform-wide withdrawal halt. Kraken’s status page shows most funding methods operating normally, while the exchange is separately reporting technical delays affecting specific blockchain networks. The accounts emerging through Kraken’s public support forum instead appear more consistent with individual withdrawals being flagged for internal security or compliance review.

One complaint posted September 10 described a Bitcoin withdrawal initiated on August 31 that remained marked “On hold” 12 days later.

The poster said they were a fully verified Swiss customer who deposited funds by bank transfer in their own name, bought BTC through Kraken’s BTC/CHF market and attempted to send it to an address already stored on their withdrawal whitelist.

According to the user, Kraken emailed on August 31 saying the withdrawal was being reviewed and that the review should be completed within five business days. The customer said that period passed without a resolution, request for additional documentation or explanation.

The poster also claimed to have sent four follow-up messages without receiving a reply.

More unusually, the customer said Kraken’s AI support assistant would not transfer the case to a human because an active support ticket already existed, while at the same time indicating that the ticket remained categorized as “New.” The poster interpreted that to mean it had not yet been handled by a support agent.

The user said no transaction had appeared onchain and that the BTC therefore remained on Kraken rather than having been broadcast to the destination wallet. Kraken’s public support account responded to the Reddit post by asking the customer to privately provide their Public Account ID so the case could be checked.

Other customers joined the thread with similar allegations.

One said a withdrawal had been pending since August 28, while another claimed to have been waiting two to three weeks. Kraken support publicly asked the August 28 complainant for a ticket number and said it would escalate the case. These remain individual user claims and have not been independently verified.

A separate September 10 complaint described a broadly similar sequence involving euros deposited by SEPA, converted into USDC and then submitted for withdrawal. That customer said Kraken’s AI support system told them they would be contacted within five business days but that the deadline passed without communication. Kraken again responded publicly by requesting the user’s account details.

Comments under that post included another customer claiming a withdrawal had been pending for almost two weeks and a separate user alleging a considerably longer restriction. Those posts are unverified and may involve different compliance, funding or account-security circumstances.

Kraken acknowledges that some withdrawals can require manual intervention.

Its support documentation says transactions may be held for internal review and that the exchange may reject transfers involving wallets associated with prohibited activity. Kraken describes such reviews as both a regulatory requirement and a customer-security measure and says that when a withdrawal is held for internal review, its team will contact the customer by email within five business days.

Separate automatic holds can arise from particular funding methods. Kraken says some card or digital-wallet purchases can result in 72-hour withdrawal holds, while purchases funded through ACH Plaid can produce seven-day restrictions. Other transactions marked “On Hold” require manual action from Kraken support rather than expiring automatically.

The recent complaints are notable because users are specifically describing waits that exceed those normal periods.

There is also at least one fresh resolution.

On September 11, another customer posted that two withdrawals had been released after their funds had been locked for approximately two weeks. The user said both withdrawals were released Friday morning and the money was returned to their account, encouraging other affected customers to continue working with Kraken’s support moderators.

Others responding to that resolution post said they were still waiting, including one customer who reported more than a week without resolution despite sending three email reminders and contacting Kraken through Reddit. Kraken support replied that it had responded to that person’s separate case.

The pattern is not entirely new. In June, another customer reported that a withdrawal held for about two weeks was eventually released after contacting Kraken support through Reddit. Kraken’s support account acknowledged the resolution publicly.

Kraken’s live status page does not currently indicate a general withdrawal-processing outage. It does show funding disruptions affecting particular networks, including a September 10 MultiversX issue and continuing work related to a group of blockchain networks first reported on September 4. Kraken states that other funding methods remain operational in the MultiversX notice.

That distinction leaves the emerging complaints looking less like an exchange-wide inability to process withdrawals and more like a backlog, communication problem or unusually slow handling of accounts selected for manual review.

The Support Queue May Be the More Important Issue

The most useful signal from these complaints is not that Kraken sometimes holds withdrawals.

Every large regulated crypto exchange has systems for detecting fraud, sanctions exposure, suspicious wallet activity and potential scams. A transaction being stopped for manual review is therefore not, by itself, evidence that anything is wrong with the exchange.

The issue is what happens after the transaction is stopped.

Kraken publicly tells customers that its team will contact them within five business days when a withdrawal is placed under internal review.

Several of the current complaints describe something different: that period expires, no documents are requested, no substantive update arrives and customers struggle to establish whether anyone is actively working on their ticket.

If those descriptions are accurate, the weakness is not necessarily the compliance system. It may be the queue behind it.

That matters because automated risk controls can scale much faster than manual compliance teams. An exchange can instantly flag hundreds or thousands of transactions using wallet analytics, behavioral rules or fraud models. Each false positive, however, may then require a human employee to understand the customer’s funding source, destination wallet and transaction history before releasing the funds.

A sufficiently aggressive risk model combined with limited review capacity can therefore produce an uncomfortable outcome: the security system works exactly as designed, but legitimate customers wait far longer than expected.

The September 11 resolution supports that interpretation more than a liquidity or solvency theory.

That user says two withdrawals were eventually released after around two weeks. Another June case describes a similar outcome.

If Kraken were experiencing a broad inability to meet withdrawals, one would expect a much wider pattern across assets, more consistent reports and potentially a corresponding operational notice. That evidence is not present here. Kraken’s own status page instead isolates current technical withdrawal problems to particular networks.

The AI-support element is nevertheless worth watching.

Automation is useful when it routes routine questions quickly. It becomes counterproductive if a customer whose money is already under manual review gets trapped between an automated assistant that says an active ticket prevents escalation and a ticket queue that does not appear to be advancing.

That creates a communication failure precisely when customers are most sensitive to silence.

For an exchange, prolonged withdrawal reviews are reputationally expensive even when every hold is justified. A customer does not see the sanctions-screening model or internal fraud investigation. They see an account marked verified, a withdrawal marked pending and repeated days without access to their money.

The next signal to watch is therefore not simply whether another withdrawal complaint appears.

It is whether Kraken begins resolving this September cluster, whether affected users consistently report waits of roughly two weeks, and whether support starts explaining why reviews are running beyond the five-business-day window.

At the moment, the evidence supports a narrower story: some Kraken customers appear to be stuck in unusually long manual-review queues, while at least one fresh case shows those holds can eventually be released.

That is a customer-support and operational-capacity issue worth monitoring, but it is not currently evidence of a platform-wide withdrawal freeze.

Financial Markets Analyst and Digital Assets Journalist at  |  More Posts

Shane Neagle is a financial markets analyst and digital assets journalist specializing in cryptocurrencies, memecoins, prediction markets, and blockchain-based financial systems. His work focuses on market structure, incentive design, liquidity dynamics, and how speculative behavior emerges across decentralized platforms.

He closely covers emerging crypto narratives, including memecoin ecosystems, on-chain activity, and the role of prediction markets in pricing political, economic, and technological outcomes. His analysis examines how capital flows, trader psychology, and platform design interact to create rapid market cycles across Web3 environments.

Alongside digital assets, Shane follows broader fintech and online trading developments, particularly where traditional financial infrastructure intersects with blockchain technology. His research-driven approach emphasizes understanding why markets behave the way they do, rather than short-term price movements, helping readers navigate fast-evolving crypto and speculative markets with clearer context.

Leave a Reply

Your email address will not be published. Required fields are marked *