Bitget to End Services for Selected Users Amid Russia Restrictions
Key Takeaways
- •Bitget publicly announced on October 17 that it would end services for selected customers, while operations continue as usual for users who receive no notification.
- •The updated English Terms of Use, marked October 16, designate Russia, Belarus, and Kazakhstan as prohibited jurisdictions, applying to both residents and entities established or operating there.
- •No unified cutoff date was published, so each account's individual notice serves as its binding timetable, with one user reporting an October 21 end of service.
- •Bitget described the terminations as a one-time exercise, stated that customer funds remain safe, and did not disclose the number of affected accounts or any specific regulatory order behind the decision.
- •The notice came more than three weeks after a September 24 wallet breach with losses revised to approximately 387.5 million dollars, though the exchange did not connect the account terminations to that attack.

Bitget will discontinue services for a selected group of customers, with each affected account set to receive its own deadline, next steps and withdrawal instructions. The cryptocurrency exchange publicly announced the measure on October 17 and said operations would continue as usual for all other users.
The move follows an update to Bitget's English Terms of Use, marked as updated on October 16, which list Russia, Belarus and Kazakhstan among prohibited jurisdictions for residents and operators. Eligibility clauses of this kind are a standard compliance feature among globally operating exchanges, which define who can open and hold accounts by where those customers live and operate. The main announcement gave no shared cutoff date, although one customer reported an October21 end of service for his account.
The company described the action as a one-time exercise and said customer funds remained safe. It did not disclose the number of affected accounts or identify a specific regulatory order behind the terminations.
Bitget Sends Individual Notices With Withdrawal Instructions
According to the announcement, affected customers will receive emails, in-app messages and/or push notifications. These messages will set out the steps required before service ends, including arrangements for taking assets off the platform. Bitget support will assist with outstanding orders and account questions throughout the process.
The exchange did not publish a single withdrawal procedure applicable to every affected account; each account's arrangements are being communicated directly through its own notices. With no shared cutoff in place, each recipient's notice effectively serves as the binding timetable for completing those steps. A user posting under the name FrontMan said on October 16 that he had received one of the notices. His notification reportedly set October 21 as the end of service for his account.
Customers who receive no official notification can continue using their accounts under the existing terms and conditions. The company did not describe the exercise as an exchange-wide shutdown, nor did it announce any suspension of trading.
The announcement also directed users toward official channels for updates and assistance, naming the website, app, Support Center and verified social accounts, while warning against phishing links and impersonation attempts — a caution with practical weight in a rollout where genuine instructions arrive one account at a time.
Russia Restrictions Appear in Updated Eligibility Terms
Bitget lists Russia, Belarus and Kazakhstan within a broader group of locations excluded from its services. The English agreement labels that group as prohibited countries and allows the exchange to designate additional locations.
Under the document, restricted persons include individuals residing in those places as well as entities established or operating there. The eligibility section states that restricted persons cannot register for accounts or use the services. The wording connects access to residence and operations, rather than nationality alone.
Bitget support separately addressed a question about restrictions on users in Russia, citing the country list and compliance with national regulations. According to The Defiant, the reply did not name a specific law, regulator or enforcement action.
The terms also cover know-your-customer and anti-money-laundering procedures, commonly grouped as KYC/AML requirements. Users must provide accurate information and update it when circumstances change, and the agreement allows Bitget to request further documents and conduct enhanced due diligence.
The agreement further permits the platform to restrict access or close accounts when users no longer meet eligibility conditions. It allows the closure of outstanding positions, depending on the circumstances, and leaves some risk assessment criteria confidential. This authority also extends to legal or regulatory restrictions, concerns, requests and other requirements.
Those standing KYC/AML provisions do not identify the reason for the latest service withdrawals, and the main notice did not say that every customer in a named jurisdiction had received an identical timetable. For users in the listed countries who have not been notified, the updated terms still read as written: restricted persons cannot use the services, and the agreement leaves the platform room to act on accounts that no longer meet those conditions.
Notice Follows September Wallet Breach
Bitget issued the service notice more than three weeks after a September 24 wallet breach. Its September 25 security update put transfers to attacker-controlled addresses at approximately 387.5 million dollars, a revised figure that exceeded the initial estimate of 351.6 million dollars.
The company said the difference reflected a fuller classification of transfers, including assets on Zcash and TRON, and stressed that the revision did not represent further unauthorized transfers. The security update said investigators had identified and repaired the vulnerability, with external specialists Mandiant and SlowMist assisting the investigation alongside Bitget's internal security and technical teams.
The exchange did not connect the account terminations to that attack. The scale of the exercise and its stated basis remain open points — the number of accounts affected, any regulatory order behind them and whether a broader timetable emerges — and any further detail would have to come from additional Bitget statements or the notices reaching individual accounts.
This article is based on reporting by Blockonomi.