Bitget Withdrawal Pause: Balances vs. Self-Custody
Learn what the Bitget withdrawal pause means, how exchange balances differ from self-custody, and which checks matter before moving funds safely.
Author: Damon Salvatore · Senior Content Marketer Quick Answer
When an exchange pauses withdrawals, the balance in your account and your ability to move that balance are separate things. A hardware wallet cannot pull funds out of an exchange that has not processed a withdrawal. Verify the official notice, preserve your records, avoid unofficial recovery offers, and prepare a tested destination for when the relevant withdrawal service becomes available.
Bitget's September 24, 2026 security notice makes this distinction concrete. The exchange reported unauthorized wallet transfers and a withdrawal pause, while saying account balances remained accurate. The immediate question for an account holder is how to manage access and avoid a second loss while the platform responds.
This guide explains the withdrawal dependency, what different forms of reassurance establish, and how to plan a careful move into self-custody. Incident details below refer to Bitget's September 24 notice, reviewed on September 25; service availability can change after publication.
Key Takeaways
- An exchange login authorizes account requests; it does not give you the signing keys to the exchange's wallets.
- A protection-fund statement, a reserve report, and a completed withdrawal answer different questions.
- A pause alone does not prove insolvency, and an unchanged balance does not prove immediate withdrawability.
- Check the particular asset and network. A network-specific restriction and a platform-wide suspension require different responses.
- Self-custody starts after funds arrive at an address whose signing authority you control. Prepare the wallet and backup before moving a meaningful amount.
What Bitget Reported on September 24
In its official security notice, Bitget said it detected unauthorized transfers at 18:31 UTC on September 24, 2026 and estimated approximately $351.6 million was affected. It said withdrawals were temporarily suspended pending a security review, while deposits and trading remained operational.
Bitget also said its cold wallets were secure and its User Protection Fund covered the loss. Those are the exchange's statements about its systems and resources, not independent guarantees made by this article. The notice did not establish a completed root-cause investigation or a fixed reopening time. Read subsequent official notices for changes instead of treating the original announcement as a live status page.
The important operational distinction is visible without speculating about the attacker: a platform can continue showing balances and accepting trades while its outbound transfer process is unavailable. That observation does not establish whether every account has the same restrictions or predict how the incident will resolve.
Why a Balance Can Remain Visible While Withdrawals Stop
On a custodial exchange, your account normally records an entitlement within the service's ledger. To withdraw, you submit a request. The exchange checks that request, applies its controls, and arranges an on-chain transfer from wallets it manages. Your password and two-factor authentication help authorize the request, but they do not sign that blockchain transaction directly.
For example, imagine an account displays 0.1 BTC while Bitcoin withdrawals are paused. The displayed amount can remain 0.1 BTC throughout the pause. Buying a hardware wallet, creating a receiving address, or resetting the exchange password does not move it. A withdrawal must be processed and confirmed on Bitcoin before the destination wallet can spend the received coins.
This is the practical difference between custodial account access and control of wallet keys. Self-custody removes the exchange from the signing path for assets already withdrawn. It does not retroactively remove the exchange from a transfer that still awaits processing.
The opposite mistake is to read any delay as proof of theft. An account review, a maintenance window, insufficient network support, or a security hold can also interrupt withdrawals. The cause must be established from the relevant account message and official notice.
Four Signals That Should Not Be Confused
| Signal | What it can tell you | What it does not establish |
|---|---|---|
| Account balance | The amount recorded for your account | That an outbound transfer will be processed now |
| Protection-fund statement | The platform's stated resources or response commitment | A completed reimbursement or an individual payment timetable |
| Proof-of-reserves report | Information within a report's stated scope and snapshot date | The assurance of a full financial-statement audit or continuous withdrawal availability |
| Confirmed withdrawal | That a particular transfer reached its destination on the selected network | That every future withdrawal or every other account is unrestricted |
The PCAOB Office of the Investor Advocate's proof-of-reserves advisory explains that these engagements are not audits. It highlights limits involving liabilities, customer rights, borrowed assets, internal controls, and changes after a snapshot. That general advisory is useful for interpreting a report; it is not a finding about Bitget.
For a protection fund, read what is actually promised: eligible incidents, eligible customers, decision authority, valuation method, and any published claim process. Do not substitute the headline size of a fund for those details. A statement that a loss is covered and the ability to send a withdrawal today remain separate questions.
What to Do While Withdrawals Are Paused
1. Identify the scope before changing anything
Open the exchange through a saved official address or the application you already use. Record the notice date, the affected assets and networks, and whether the message applies to your account or the whole platform. Bitget's withdrawal restriction guide describes several possible causes, including account requirements, network issues, and security measures. A routine restriction article does not override an incident-specific notice.
If your withdrawal was already requested, save its request identifier and status. An exchange request number is not necessarily a blockchain transaction hash. If a hash is provided, check it on the correct network's explorer and compare the destination and amount. Do not enter wallet recovery words into an explorer or support form.
Keep three stages separate in your notes. A queued request is still awaiting the service's processing. A broadcast transaction has been sent to a blockchain network but may still await confirmation. A confirmed transaction has been included on that network; you must still check that it delivered the intended asset to the intended destination. If support says a request is complete but you cannot reconcile the hash, network, and destination, describe that exact mismatch in the ticket. Repeatedly submitting new withdrawal requests can make the record harder to follow without resolving the original problem.
2. Preserve a private record of your position
Download available account statements and transaction history. Record asset quantities, pending transfers, open support tickets, and timestamps. Keep this information somewhere private: publicly posting an account screenshot can expose balances and identifying details to people offering fraudulent help.
Separate the account record from assumptions about compensation. Documenting a balance helps you describe a problem accurately; it does not itself determine a claim's legal status or outcome. Follow an official process if one is announced, and retain copies of what you submit.
3. Secure account access without expecting it to reopen withdrawals
Review active sessions, withdrawal destinations, and API access through the genuine application. Revoke access you no longer recognize or need. If there is evidence your own account was compromised, use the exchange's security response process. Account protection and the exchange's wallet investigation are related concerns, but fixing one does not automatically fix the other.
Before changing authentication settings, read the platform's warning about any resulting security hold. An urgent but unnecessary reset can introduce another restriction. Our guide to exchange account theft and account security explains the personal-account side of this problem.
4. Reject off-platform shortcuts
An unsolicited message offering a priority withdrawal, wallet synchronization, or fund release should not be treated as support. Do not send a separate crypto payment to an address supplied in a message to unlock your balance. Verify any legitimate fee inside the official withdrawal flow.
The FTC's recovery-scam guidance warns about people who promise to retrieve lost money for an upfront fee. A live incident gives these offers a convincing pretext. Keep support conversations inside channels you reached independently, and never share a seed phrase, private key, or one-time authentication code with a purported helper.
Prepare a Withdrawal Destination Without Rushing
You can prepare a self-custody wallet while a service is paused, provided you keep preparation separate from claims that a withdrawal has succeeded. Set up the wallet through its official process, make the required backup, and verify that you understand recovery. Do not create a destination from recovery words sent by another person.
Choose the asset and network deliberately. An exchange can offer the same ticker on several networks, and a receiving application may support only some of them. A familiar-looking address does not prove that the selected network, token contract, and receiving account are compatible. A wrapped or bridged asset may also introduce dependencies different from holding the native asset.
When the relevant withdrawal route is available, use a staged procedure:
- Confirm the current official service notice and any account-specific restrictions.
- Generate the receiving address yourself and verify it on the hardware device when that function is supported.
- Check the asset, network, required memo or tag, minimum withdrawal, and displayed fee.
- Send a small test amount that satisfies the minimum and is useful after fees.
- Wait for the expected confirmations and verify the actual received asset in the destination wallet.
- Recheck the destination and network before deciding whether to send the remaining planned amount.
A successful test verifies that particular route and transfer. It is not permission to ignore details on the next request, especially if you change networks or addresses. The full exchange-to-self-custody withdrawal checklist covers these checks in more detail.
What a Hardware Wallet Can Change
Once assets have arrived at a supported address controlled by your hardware wallet, the device can protect the signing keys and require confirmation for supported transactions. This reduces reliance on the exchange for spending those particular assets. It also gives you responsibility for backups, destination verification, and safe signing.
A hardware wallet cannot resume an exchange's withdrawal service, reimburse a platform loss, validate its reserves, or remove a token issuer's controls. It cannot make a bridged asset equivalent to its native counterpart. These limits apply to UKey and to other hardware-wallet brands.
Bitcoin.org's wallet security guidance recommends separating everyday spending amounts from funds kept in a safer environment and taking backups seriously. The useful decision is how much operational access you need and which responsibilities you can manage, rather than assuming one wallet arrangement solves every risk.
For example, someone who needs a modest exchange balance for occasional trading can define that amount in advance and review it periodically. Long-term holdings can follow a separate custody plan after the owner has tested setup and recovery. This is a planning example, not a prescribed allocation or a claim that self-custody is risk-free.
Related Resources
Use the broader crypto asset security guide to connect account protection, backups, and transaction checks. If you are selecting a signing setup, compare hardware and software wallet responsibilities. For UKey-specific setup assistance, start at the official UKey Help Center.
This article provides general security education, not individualized financial or legal advice. Check current official service notices before taking action.
