A growing cluster of Kraken customers is reporting multi-week account restrictions, with a fresh Sept. 17 complaint saying more than $890 remains inaccessible after roughly three weeks of verification and more than two weeks without substantive follow-up from support.
The latest report appeared inside an existing Kraken Support thread opened Sept. 14 by another customer whose account had already been restricted for almost two weeks.
The Sept. 17 commenter said they had supplied every detail requested by Kraken but had received no meaningful response despite repeatedly following up on the support ticket. The customer said the verification process had lasted more than three weeks and that support had not contacted them substantively for over two weeks.
The user said the inaccessible balance exceeded $890 and that the restriction was causing financial pressure. They also indicated they were considering approaching their bank because they had been unable to obtain a resolution directly from Kraken.
The allegations are unverified. The customer’s account history, balance, verification documents and reason for the restriction have not been independently established.
Another commenter in the same thread said their own restriction had lasted four weeks.
Kraken Support responded to the original poster by asking for a Public Account ID or ticket number so the case could be reviewed and escalated.
Separate Threads Show Similar Multi-Week Delays
The Sept. 17 complaint is not the only recent report involving an extended Kraken review.
A separate customer posted Sept. 15 that their account had been restricted for seven days without receiving an explanation or request for additional documentation. Kraken Support said it had escalated the case.
Follow-up comments in that thread included one user saying their problem was approaching three weeks and another saying their account had been restricted since Sept. 1 without a response.
Another Sept. 14 customer said a restriction had followed an account-information issue involving differences between the name and address recorded by Kraken and those on a bank account. Kraken Support said the case had been escalated but warned that resolution could still require several business days.
The fresh reports extend an existing pattern. Earlier this week, a Kraken customer said a USDC transfer from Bitget preceded a 13-day account restriction, providing one of the more specific potential transaction triggers seen in the recent complaints.
None of these reports proves that the same internal control is responsible for every case.
Kraken Says Transactions Can Trigger Additional Review
Kraken’s own documentation says it can restrict account services for several reasons, including suspected security issues, activity involving prohibited or scam-linked wallets, payment reversals, outdated identity information and failure to provide additional information requested for regulatory purposes.
The exchange also says account activity itself can trigger a request for additional documentation. A change in how an account is used, or the size or type of a transaction, may lead Kraken to seek further information even from an already verified customer.
Kraken says users whose funding abilities are suspended may be unable to deposit or withdraw either fiat or cryptocurrency until the account review is completed.
The company tells customers to monitor their email and respond promptly when additional documents are requested.
For a withdrawal held for internal review, Kraken says its team should normally contact the customer by email within five business days.
That published timeframe makes the reports of two or more weeks without substantive communication worth separating from ordinary short-duration withdrawal checks.
Not Every Kraken Restriction Has the Same Timeline
Kraken’s documentation also makes clear that not all restrictions follow one timetable.
Certain scam-prevention restrictions can remain in place for 90 days and cannot be removed early, according to the exchange. Other restrictions can be lifted once Kraken’s team completes its review.
Ordinary identity verification is generally much faster. Kraken says standard automated verification can be immediate, while manual verification may take a few days. Business verification can take around five days.
That means the critical missing detail in the current user cluster is the exact category of restriction each customer has received.
A three-week enhanced compliance review is different from a predetermined scam-prevention lock. A verification problem is different again.
Without the emails or notices Kraken sent to each customer, it is premature to treat the reports as one confirmed technical or compliance problem.
The pattern nevertheless resembles other recent cases in which account restrictions feed into additional identity-verification requirements, creating a second layer of friction before users can regain full access.
MultiversX Funding Delays Are a Separate Issue
Kraken is simultaneously dealing with an official funding incident, but there is no current evidence linking it to these account-specific complaints.
The exchange’s status page still lists delays affecting its MultiversX funding gateway. Kraken says EGLD deposits and withdrawals may be delayed while the issue is investigated.
The status page explicitly says all other funding methods are operating normally.
That makes it important not to combine the MultiversX incident with the customer-restriction cluster.
A user whose EGLD transfer is delayed because of an exchange-wide network gateway problem is facing a different issue from a customer whose entire account or funding functionality has been restricted following a security or compliance review.
Kraken has also recently imposed market-specific restrictions for entirely separate regulatory reasons. Kraken’s UAE customers recently lost withdrawal access to seven assets, illustrating why withdrawal limitations need to be classified before they are treated as evidence of one broader platform problem.
The Triggering Transactions Are Now the Most Useful Evidence
The important next step is not simply finding more customers who say their accounts are restricted.
It is determining what happened immediately before each restriction.
The Bitget-to-Kraken USDC case offers one possible trigger. Another customer recently said a restriction followed a bank deposit of slightly more than €100 from an account in their own name. A separate Sept. 9 user said an already verified account was pushed back into residence verification before withdrawals became unavailable.
If the newest $890 case followed a similar deposit, withdrawal or external-wallet transaction, the reports could begin to form a more coherent pattern.
If the triggering events are entirely unrelated, then the apparent cluster may simply reflect several different compliance workflows producing similar customer-facing symptoms.
This is the same distinction that matters in the growing Bybit account-restriction cluster, where investigators are trying to determine whether repeated freezes share transaction destinations or risk providers rather than assuming every restricted account has the same cause.
Communication May Be the Bigger Problem Than the Initial Restriction
A crypto exchange stopping a transaction is not inherently alarming.
It may be exactly what customers want if an account has been compromised or funds are being sent to a scammer.
The more difficult problem begins once the customer says the transaction is legitimate and supplies the requested information.
At that point, the quality of the review process matters as much as the original detection system.
A restriction lasting several hours while a suspicious withdrawal is checked is one thing.
A restriction extending for several weeks without a clear timeline creates a fundamentally different experience, particularly if the customer cannot access money needed for ordinary expenses.
That problem has appeared across several financial platforms. A Skrill customer recently said funds became inaccessible immediately after card funding, while Polymarket users have reported withdrawal delays followed by account holds.
The platforms and circumstances differ, but they expose the same operational weak point: automated or compliance-driven restrictions are relatively easy to impose and potentially much harder to resolve.
More Verification Can Create a Feedback Loop
The danger for centralized platforms is that each attempt to reduce risk can add another point of failure.
A transaction-monitoring system flags an account.
The account is restricted.
The customer enters additional verification.
The verification requires manual review.
The customer opens a support ticket.
The support team escalates the case to another department.
Before long, the original suspicious transaction may no longer be the main problem. The customer is stuck between several teams and processes that depend on one another.
That is why multi-week reviews can damage confidence even when the original restriction was justified.
Similar prolonged access problems have appeared at offshore exchanges, including extended account freezes reported by XT.com customers. But Kraken operates as a major regulated exchange, which makes predictable review procedures particularly important to its customer proposition.
The Next Useful Update Is Not Another Duration Number
Two weeks, three weeks and four weeks make attention-grabbing complaint figures.
They do not explain why the accounts were restricted.
The next useful evidence is the triggering transaction for each customer, the wording of Kraken’s restriction notice, what documents were requested, when those documents were supplied and which internal review category the account entered.
If several unrelated customers received effectively identical notices after similar transactions and then waited weeks after supplying the same information, there may be a common workflow bottleneck worth investigating.
If each customer received a different type of restriction, the current cluster is more likely to reflect several separate cases appearing at the same time.
For now, the evidence supports a narrower conclusion.
Multiple Kraken customers are publicly reporting account-specific restrictions lasting from roughly two weeks to four weeks, and at least one Sept. 17 user says more than $890 remains inaccessible after weeks of verification and limited substantive communication.
Kraken’s official status page does not show a broad withdrawal outage outside the MultiversX funding issue.
The strongest next step is therefore not outage monitoring.
It is reconstructing the review path inside each restricted account.
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.