Toobit said on October 11 that withdrawals had resumed for MMT, WAL, CETUS, SUI and HAEDAL on the Sui network, following a series of earlier service notices affecting transfers through the exchange.
The restoration announcement identifies all five assets and says withdrawals are available again. The update concerns Toobit's withdrawal service on a specified network; it is not a declaration that every exchange has restored the same routes or that every customer's pending transfer has completed.
Earlier October 11 notices separately covered SUI, HAEDAL and MMT withdrawals, WAL withdrawals and CETUS withdrawals. Another notice on the same date reported the restoration of SUI, HAEDAL and MMT deposits. The distinction matters because deposits and withdrawals are separate directions of service, even when the same assets and blockchain are involved.
What the restoration changes
A withdrawal is the exchange-side instruction to send assets out to a blockchain address. When that route is unavailable, a customer may still see a balance in an account without being able to move it through the affected network. A notice restoring the route removes the announced service restriction; it does not provide a receipt for an individual transaction.
For example, an order to sell a token within an exchange and a request to transfer that token to an external address are different operations. Successful trading inside an account would not by itself demonstrate that a blockchain withdrawal was available. Conversely, restoring withdrawals does not establish anything about a particular trading pair's depth or price.
Our self-custody guide explains the separation between a service-account balance and direct control over signing keys. A transfer to a wallet changes where an asset is held, but its completion still depends on the withdrawal being processed and the resulting transaction reaching the intended destination.
A network-specific notice, not a blanket guarantee
The reported restoration is explicitly for the Sui route. A ticker alone does not identify the blockchain used by a transfer. Matching the named asset, supported network and destination instructions is therefore more informative than treating a familiar symbol as sufficient confirmation.
The reviewed announcement does not establish independently measured transaction success for every account, eliminate account-specific restrictions or report how many requests were affected. It also does not quantify a backlog or promise a completion time for already submitted requests. Those questions require actual account records or additional operational evidence.
Nor does a platform's service pause, taken by itself, prove a blockchain-wide outage or security exploit. Exchange-side availability and network-wide operation are different claims. This report does not infer the latter from the former.
The immediate development is Toobit's published restoration for five named assets on one network. Users reviewing an earlier suspension notice now have a later official status statement to compare with it, while the actual progress of an individual withdrawal remains a separate check.