A Gemini withdrawal complaint that initially involved a single customer has developed into a small two-user cluster after another customer reported the same problem on September 30, although there is still no evidence of a platform-wide withdrawal outage.
The original complaint was posted on September 27 by a Gemini user who said the exchange was preventing cryptocurrency withdrawals while also rejecting a recent bank deposit. The customer asked Gemini to remove restrictions on the account but did not disclose the amount involved, the cryptocurrency being withdrawn or the exact reason Gemini provided for the restriction.
Three days later, a second user joined the same Reddit thread and said: “It doesn’t let me withdraw either and I get the same message.”
That changes the evidence slightly. One withdrawal complaint can easily represent an isolated account issue. Two people independently describing what they say is the same error makes it more useful to investigate whether Gemini has a common automated restriction state affecting otherwise unrelated customers.
But two reports are still far from evidence of a widespread problem, and Gemini has not publicly linked the accounts or acknowledged a broader withdrawal issue.
Gemini’s Status Page Shows No Matching Crypto Withdrawal Outage
The strongest evidence against treating this as a platform-wide incident comes from Gemini’s own operational status history.
Gemini currently lists its digital-currency services and major cryptocurrency deposit and withdrawal systems as operational. No general crypto-withdrawal incident was reported on September 29, and the platform was not showing a corresponding withdrawal disruption on September 30 when checked.
That resembles a recent Coinbase customer complaint involving a stuck Bitcoin Lightning payment, where an individual user reported a serious access problem even though the exchange’s status page showed no matching system-wide failure.
Public status pages generally describe infrastructure incidents affecting groups of customers. They do not necessarily disclose individual security reviews, compliance restrictions, unsettled deposits or account-specific risk controls.
That makes an account-level restriction entirely compatible with a status page showing green across the board.
The September 27 Bank Deposit Failure May Be a Separate Clue
There is, however, an important complication in the original Gemini report.
Gemini did experience an official ACH incident on September 27, the same day the first customer said their bank deposit was rejected.
The exchange reported delayed or unsuccessful ACH deposits and withdrawals during the incident and later said transfers had returned to normal. Gemini also advised customers whose ACH deposit for a cryptocurrency purchase failed or was canceled to initiate another deposit where necessary to cover advanced funds and return their accounts to good standing.
That means the rejected bank deposit described by the first Reddit user may have been connected to a documented Gemini funding incident rather than whatever caused the withdrawal message.
It could also potentially matter to the withdrawal block. Gemini’s own help material states that pending ACH transfers can temporarily prevent cryptocurrency withdrawals because funds may be credited for trading before the bank transfer fully settles.
If an ACH payment failed after Gemini had already credited buying power, an account could require reconciliation before assets became withdrawable.
That is only one possible explanation. The Reddit user has not disclosed enough transaction detail to establish whether their rejected deposit funded a cryptocurrency purchase, whether Gemini had advanced funds or whether the withdrawal restriction appeared before or after the ACH failure.
The Second User Makes the Error More Interesting, Not Yet Systemic
The September 30 reply matters because the second user specifically said they received the same message.
What is still missing is the actual wording of that error and the conditions surrounding both accounts.
If both customers can produce identical screenshots showing a Gemini-specific restriction message, that would strengthen the case that they have entered the same internal account state. It would still not establish that the trigger was the same.
One account might be dealing with an unsettled bank transfer while another has encountered a device-security check, identity review or compliance flag.
Gemini publicly lists several reasons cryptocurrency withdrawals can be temporarily restricted, including signing in from a newly detected device, pending ACH or debit-card transfers, password changes, authentication changes, incomplete verification and other account-security conditions.
Some restrictions have clearly defined waiting periods. Others can require additional verification or support intervention.
That distinction has become increasingly important across centralized exchanges. Dave Finances recently covered a Bybit compliance case that reached 70 days, illustrating how a restriction that begins as an internal review can eventually become a much larger customer-access issue when no clear resolution date is available.
A Regulatory Complaint Allegedly Ended Another Gemini Restriction
A third participant in the September 30 thread added a potentially relevant historical comparison, but it needs to be treated cautiously.
The commenter said they previously had a similar experience with Gemini and eventually filed a complaint with the New York State Department of Financial Services. According to that user, Gemini subsequently closed the account but allowed the remaining funds to be withdrawn.
There is no independent evidence connecting that historical case with either of the two current users.
It nevertheless highlights an important feature of Gemini’s regulatory structure. New York’s Department of Financial Services has issued specific customer-service and complaint-handling guidance for regulated virtual-currency firms, including expectations that companies provide timely updates, escalation mechanisms and information about how customers can submit complaints to the regulator.
A regulatory complaint does not automatically force an exchange to release funds, and the Reddit commenter’s account closure should not be treated as evidence of a standard Gemini policy.
But escalation becomes more relevant when an internal account restriction stops behaving like an ordinary short security hold and begins stretching into an open-ended access problem.
The Real Issue Is the Difference Between an Outage and an Account State
For retail investors, the most interesting part of this story is not whether Gemini’s servers are functioning.
They apparently are.
The more important question is what happens when the platform’s infrastructure works normally but an individual customer’s account does not.
A centralized exchange can show Bitcoin withdrawals as “operational” while one user remains unable to transfer Bitcoin because their personal account is under review. From the exchange’s technical perspective, nothing is broken. From the customer’s perspective, the withdrawal system is completely unavailable.
That difference helps explain why customer complaints sometimes appear disconnected from official status pages.
Recent cases involving large balances held during source-of-wealth reviews demonstrate the same structural issue. Assets can remain visible inside an account while the customer’s practical ability to move them is restricted by a separate compliance or risk-control layer.
That is not evidence that an exchange lacks the assets. A withdrawal restriction and an insolvency problem are fundamentally different claims.
But for the individual user, access risk can still be economically significant.
Two Users Are a Signal, but a Pattern Needs More Evidence
This is where the current Gemini story sits.
The evidence has moved beyond a single complaint, but not by much.
To establish a meaningful cluster, the next useful information would be the exact error wording from both customers, the assets they attempted to withdraw, whether each account had a recent ACH transaction, whether funds were fully settled, when the accounts were created and what Gemini support told each customer privately.
If additional unrelated users begin reporting the same error without pending deposits or obvious security holds, the case for a shared Gemini restriction state becomes stronger.
If the original user’s problem clears once the September 27 ACH issue is reconciled while the second user turns out to have an unrelated verification problem, the apparent cluster may disappear.
That is why the distinction between correlation and common cause matters.
The same error message can be the frontend result of multiple risk controls.
Custody Convenience Comes With Access Risk
There is also a broader lesson here for investors who keep significant balances on trading platforms.
Centralized custody solves several problems. Users do not have to secure their own private keys, maintain backups or manage blockchain transactions directly.
But they exchange those responsibilities for dependence on the platform’s internal ledger, risk controls and withdrawal permissions.
Self-custody removes that particular dependency, although it introduces its own substantial risks. The recent Coldcard security investigation illustrates how difficult recovery and even basic loss measurement can become once funds are controlled entirely through individual wallets.
Neither model eliminates risk. It moves it.
For Gemini, the immediate question is narrower: whether the two September withdrawal reports represent unrelated account events or the first visible examples of a shared restriction mechanism.
The official status page currently points away from a platform-wide outage. The September 27 ACH incident offers one plausible explanation for part of the first user’s experience. The second user’s matching error keeps the story alive.
The next useful development will not be another generic complaint. It will be evidence showing what the message actually says, what both accounts have in common and whether Gemini ultimately restores withdrawals, requests additional verification or closes either relationship.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.