Binance Japan restored withdrawals for nine additional tokens following the October 29 Binance Global security breach, but 16 assets remained restricted, including NEAR, which had been listed as fully restored just a day earlier. Separately, Latin American exchange Bitso reported a third-party authentication outage that temporarily prevented customers from accessing perpetual trading and lending services. Today’s crypto roundup examines the uneven recovery at Binance Japan and the trading-access problems behind Bitso’s brief service interruption.
Binance Japan restores nine tokens but keeps 16 restricted
Binance Japan published its ninth service recovery update on November 12, confirming that withdrawals had fully resumed for nine additional cryptocurrencies following the security incident at Binance Global.
The newly restored assets are Cardano (ADA), Algorand (ALGO), Astar (ASTR), Avalanche (AVAX), Enjin Coin (ENJ), GIGGLE, Pepe (PEPE), Bittensor (TAO) and Stellar (XLM).
The update, published at 09:07 UTC, describes service availability as of 17:00 Japan Standard Time, nearly two weeks after Binance Global suffered approximately $6.34 billion in unauthorized cryptocurrency withdrawals on October 29.
Despite the latest restorations, Binance Japan reported that withdrawals remained unavailable for 16 cryptocurrencies: BCH, HBAR, DOT, ATOM, XTZ, NEO, THETA, A, GALA, QTUM, TRB, ONT, ZIL, IOTX, IOST and NEAR.
Another five assets, ARB, FET, FIL, GRAM and MASK, were available only on certain supported blockchain networks.
The list is shorter, but not, it turns out, entirely a one-way recovery.
The restrictions have progressively eased since November 2, when Binance Japan had restored full withdrawal access for only eight major cryptocurrencies. As covered in an earlier DaveFinances roundup on Binance Japan’s withdrawal restrictions, 29 assets remained completely unavailable on November 9.
The number fell to 24 in the November 11 update and subsequently to 16 on November 12, although the movement between categories was not entirely consistent.
Binance Japan confirmed that cryptocurrency trading, yen deposits and yen withdrawals continued operating normally. Cryptocurrency deposits also remained available, apart from existing restrictions affecting DOT, QTUM and ZIL because of unrelated chain-swap work.
The exchange reiterated that its October 30 inspection of wallet systems and balances found no impact on Japanese customer assets. It has maintained that local customer holdings were held in seperate custody infrastructure from the assets affected by the global incident.
NEAR returns to Binance Japan’s withdrawal blacklist
The most unusual change in the November 12 announcement concerns NEAR Protocol, which appeared in the fully restored withdrawal category in Binance Japan’s eighth recovery notice on November 11.
That earlier announcement explicitly identified NEAR among seven additional assets whose withdrawals had resumed completely, alongside CHZ, ETC, KAIA, LTC, LPT and SEI.
One day later, NEAR was back among the 16 assets classified as unavailable for withdrawal.
It had previoulsy been cleared for withdrawal, and now it wasn’t.
Binance Japan did not provide a token-specific explanation for the reversal. Its ninth notice also did not identify an additional technical incident affecting NEAR or establish whether withdrawals had been processed successfully during the period between the two announcements.
The categorization changes extend beyond NEAR. GRAM moved from the unavailable category on November 11 into partially restored withdrawals on November 12. AVAX, previously subject to partial withdrawal access, advanced to full restoration.
Consequently, the nine newly fully restored assets did not translate into a reduction of nine in the completely restricted category. The net reduction was eight, reflecting movements involving NEAR, GRAM and the other restored tokens.
The latest restrictions trace back to the October 29 breach of Binance Global’s hot-wallet infrastructure. The exchange subsequently committed to replacing affected assets using corporate resources and customer protection funds, as detailed in DaveFinances’ earlier reporting on the $6.3 billion Binance hack.
Regulatory attention followed the incident. Abu Dhabi Global Market’s Financial Services Regulatory Authority confirmed in an October 30 regulatory statement that it was engaging with Binance and monitoring the unauthorized asset withdrawals.
The recovery of stolen assets and the restoration of withdrawal services at regional affiliates are separate operational processes. Binance Japan has not reported a loss of locally held customer assets, but precautionary restrictions continue to prevent transfers of certain cryptocurrencies to external wallets.
The custody reassurance still stands, at least as the Japanese company describes it.
Binance Japan has not published an estimated completion date for the remaining withdrawals or explained whether NEAR will require further security checks before becoming available again.
Bitso perpetual traders lose access during provider outage
Latin American cryptocurrency exchange Bitso reported a separate service disruption on November 11 after a major outage at an external provider caused authentication errors across its Vaults and Perps products.
The incident began at 15:19 UTC, when Bitso warned that customers might be unable to sign in, view existing positions or place and manage trades through the affected services.
The exchange described the problem as an access failure rather than a compromise of customer funds, stating that no assets had been moved or lost.
At 15:20 UTC, Bitso reported that a fix had been implemented and that engineers were monitoring the results. The company formally resolved the incident at 15:38 UTC, giving it a recorded duration of approximately 19 minutes.
The fix was quick, the all-clear came 18 minutes later.
Although the disruption was relatively brief, its reported scope included functions used to manage existing leveraged positions. Customers unable to access Perps during the incident could potentially have been prevented from modifying orders, adjusting exposure or closing positions through the affected interface.
For someone managing leverage, nineteen minutes can feel rather long.
Bitso has not disclosed how many traders encountered authentication failures, the number or value of affected positions, or whether any submitted orders were delayed or rejected.
The status report also did not identify the external provider responsible for the authentication problem or specify whether alternative trading interfaces remained accessible throughout the interruption.
The outage followed other recent operational problems at Bitso. On November 3, the exchange experienced an account-access disruption lasting approximately three hours and 18 minutes. A separate incident on November 4 affected trading performance and Mexican peso withdrawals through the SPEI payment network for approximately 48 minutes.
Those earlier incidents were documented in DaveFinances’ roundup of trading infrastructure disruptions, which covered technical failures affecting Bitso and several other financial platforms.
Bitso has not established a common cause between the November 3–4 interruptions and the November 11 authentication outage. The latest incident specifically involved a third-party provider, while the earlier disclosures did not identify the same underlying dependency.
The available status records are not sufficent to establish whether the interrupted trading access resulted in any realized customer losses. Bitso confirmed that customer funds had not been moved or lost during the authentication failure, but did not publish transaction-level data on trading activity during the interruption.
By November 12, the two exchanges were reporting different operational outcomes. Bitso had resolved its authentication incident within 19 minutes, while Binance Japan was still restoring cryptocurrency withdrawal routes nearly two weeks after the global security breach.
For Binance Japan, the unresolved questions concern the remaining 16 restricted assets and NEAR’s unexpected return to the unavailable category. At Bitso, the provider behind the failure and its actual effect on customers’ ability to manage open positions remain undisclosed.
Johan Shamshad is Editor-in-Chief at Dave Finances, covering financial markets, digital assets, trading platforms, brokers, fintech, payments and regulation. Since 2023, he has also worked as an editor at Gulf News, the UAE English-language newspaper published by Al Nisr Publishing LLC. His work focuses on market-moving developments, company disclosures, regulatory changes and trading infrastructure, with an emphasis on primary-source verification and practical context for traders and investors.