Binance Hack 2026: Which Withdrawals Have Resumed?
By Hyun Lee · Network status checked November 6, 2026, at 14:37 UTC
Binance has resumed withdrawals on some routes, but the November 6 announcement is not an all-clear. At our check, AXL withdrawals showed as normal on BNB Smart Chain, while Arbitrum One showed a low hot-wallet balance. PENDLE showed as normal on both networks. Check the exact asset and network, not just the coin name or the date in the announcement.

Binance withdrawal status by asset and network
Recovery Update #9 scheduled a phased rollout starting November 6 at 04:00 UTC. It did not give each route its own opening time. We compared that schedule with the withdrawal column of Binance’s public network status page. The table covers examples across all nine networks in Update #9, plus three routes from the November 1 phase in Update #4.
In a separate November 6 update, Binance said it was targeting the end of the following week for withdrawals of HYPE, INJ, APT, PLASMA, NEAR and LTC, and for remaining assets on already-restored networks. That is a target, not a confirmation that those routes are open.
| Asset | Withdrawal network | Announced rollout (UTC) | Withdrawal status at 14:37 UTC, Nov 6 |
|---|---|---|---|
| BTC | Bitcoin | Nov 1, #4 | Normal |
| ETH | Ethereum | Nov 1, #4 | Normal |
| XRP | XRP Ledger | Nov 1, #4 | Normal |
| PENDLE | Arbitrum One | Nov 6, #9 | Normal |
| PENDLE | BNB Smart Chain | Nov 6, #9 | Normal |
| XRP | Ethereum | Nov 6, #9 | Normal |
| ETH | Optimism | Listed in #4 and again in #9 | Normal |
| ZRO | Arbitrum One | Nov 6, #9 | Normal |
| ZRO | Base | Nov 6, #9 | Normal |
| ZRO | Optimism | Nov 6, #9 | Normal |
| ZRO | BNB Smart Chain | Nov 6, #9 | Normal |
| ZRO | Polygon PoS | Nov 6, #9 | Normal |
| ZRO | Avalanche C-Chain | Nov 6, #9 | Normal |
| AXL | Arbitrum One | Nov 6, #9 | Not open — low hot-wallet balance |
| AXL | Base | Nov 6, #9 | Not open — low hot-wallet balance |
| AXL | BNB Smart Chain | Nov 6, #9 | Normal |
| AXL | Optimism | Nov 6, #9 | Not open — low hot-wallet balance |
| AXL | Polygon PoS | Nov 6, #9 | Not open — low hot-wallet balance |
| AXL | Avalanche C-Chain | Nov 6, #9 | Not open — low hot-wallet balance |
| U (United Stables) | Ethereum | Nov 6, #9 | Normal |
| U (United Stables) | Tron | Nov 6, #9 | Not open — token marked unsupported |
| FDUSD | Sui | Nov 6, #9 | Not open — wallet congestion |
“Normal” is what Binance’s public withdrawal column showed, not proof that a transfer was sent or received. We did not initiate a withdrawal or check account-specific eligibility. For unlisted routes, check the live status page; this sample does not establish whether they are open or closed.
How to check your route now


Both screenshots of Binance’s public status page were taken on November 6, 2026, at 11:52 UTC, before the table’s 14:37 UTC check. CoinPop added the numbered callouts. The screenshots show where to look, not live availability. Use the live status page to check your route now.
- Open the official network status page, search for the asset and expand its row. Read Withdrawal Status for the specific network. A normal deposit status does not mean withdrawals are available.
- In your own account, confirm that the same network is selectable on the withdrawal screen. A route that shows as normal publicly may still be unavailable to your account. Check the destination’s supported network and any required memo or tag separately.
- If the route is unavailable, recheck its status rather than choosing a similarly named network. U is not USDT, and XRP on Ethereum is not XRP on XRP Ledger.
What happened in the Binance hack?
In its October 30 incident update, Binance reported that hot wallets were compromised on October 29 and estimated the loss at about US$6.3 billion. The FBI attributed the theft to North Korea’s TraderTraitor actors. Binance announced a first reopening phase for November 1 and expanded the rollout in later updates, including the November 6 notice above.
Frozen funds, asset replenishment and Proof of Reserves are different
| Measure | Reported figure or scope | What it does not show |
|---|---|---|
| Stolen funds frozen | Chainalysis reported about US$2.8 billion frozen as of 11:30 a.m. ET on November 3. | A freeze restricts movement; it is not evidence that the funds were returned to Binance or customers. |
| Affected assets replenished | Binance Update #7 reported replacing about 98% of the impacted amount as of November 4, with purchases of remaining tokens still under way. | This is Binance’s report of replacement assets, not the percentage retrieved from the attacker or the percentage of withdrawal routes reopened. |
| Proof of Reserves (PoR) | Binance said its November 4, 00:00 UTC reserve snapshot covered 44 tokens, up from 10 in the previous snapshot. | A snapshot addresses backing for assets in scope at that time. It is not a full solvency audit, proof that stolen funds were recovered, or a check of today’s withdrawal routes. |
The November 4 snapshot and its cryptographic proof are separate. Update #7 said the proof was still being generated when the snapshot was announced. On November 6, Binance reported that the proof for its latest snapshot was ready. That is the exchange’s announcement; we did not independently run the proof verification. Check the date on the specific report before relying on it.