Bitget Restricts Russia, Belarus and Kazakhstan Accounts

• Bitget’s October 16 terms list Russia, Belarus and Kazakhstan as prohibited jurisdictions.
• Some notified customers face trading restrictions on October 18 and account closures on October 21.
• Open derivatives, withdrawal access and inconsistent support documentation create additional risks.

Bitget is discontinuing services for selected customers after updating its Terms of Use on October 16, 2026, placing Russia, Belarus and Kazakhstan on its prohibited-jurisdiction list.

The exchange says affected users will receive individual instructions and deadlines.

However, notices reported by Russian news agency Interfax indicate that some customers have been given only a few days to close positions and withdraw their cryptocurrency before account access is restricted.

Bitget has described the offboarding as a one-off exercise and said users who receive no notification can continue using their accounts under its terms. The policy change nevertheless creates immediate operational risks for customers with leveraged trades, assets committed to exchange products or withdrawals still awaiting completion.

What Affected Bitget Traders Should Do First

Customers who have received a termination notice should establish their account-specific deadline before taking further action.

• Verify the notice through Bitget. Open the official app or website directly. Avoid withdrawal links in unsolicited messages, and check the deadline shown in the authenticated account notification.
• Review derivatives and margin exposure. Identify open futures positions, pending orders, trading bots and outstanding loans. Where closure is required, consider execution costs and whether the position hedges assets held elsewhere.
• Check committed assets. Review Earn subscriptions, locked balances and other products that may require redemption or settlement before funds become withdrawable.
• Confirm withdrawal compatibility. Check the destination address, token and blockchain network. For example, USDT transferred through Ethereum and Tron uses different network standards. A small test transfer may help where time and fees permit.
• Export account records. Save transaction histories, funding payments, account statements and withdrawal confirmations before login access changes.

Users should not attempt to bypass geographic restrictions using false identity documents or misleading location information. Such activity can create additional compliance problems and jeopardize account access.

Bitget’s assurances that customer funds remain safe do not eliminate the need to follow account-specific withdrawal procedures.

October 18 and 21: The Reported Offboarding Schedule

According to Interfax’s October 17 report, notifications sent to certain customers describe two stages of restrictions.

The reported schedule is as follows:

BITGET / ACCOUNT OFFBOARDING Two Dates Affected Traders Need to Check

Reported customer-notice schedule. All times are Moscow local time (UTC+3).

October 18, 202610:00 MSK / 07:00 UTC New activity restricted

Notified customers are told that new trades, orders and subscriptions will become unavailable. Existing exposure still requires attention.

October 21, 202610:00 MSK / 07:00 UTC Position and withdrawal deadline

Affected users are instructed to close positions and withdraw assets. Remaining positions may be closed automatically, with login restrictions following the cutoff.

IMPORTANT QUALIFICATION

These dates come from reported customer notifications. Bitget has not established a single deadline for every affected account. Check the instructions issued to your own account.

Source: Interfax, October 17, 2026, citing customer notifications. Operational requirements should be verified through Bitget’s official Terms of Use and authenticated account messages.

The deadline distinction is particularly important because Bitget has not published a universal closure timetable. Its public communication describes individualized notifications rather than a blanket suspension at a single hour.

Forced Closures Can Turn Paper Losses Into Realized Losses

Bitget’s Terms of Use give the exchange authority to restrict services and take action against outstanding positions when customers no longer meet eligibility requirements.

For derivatives traders, an account closure can produce financial consequences even without a margin liquidation.

Consider a trader holding a $30,000 Bitcoin perpetual futures position supported by $3,000 in collateral. A 2% adverse move in the underlying price would generate approximately $600 in trading losses before fees and funding adjustments, equivalent to 20% of the initial collateral.

If the exchange closes the position at that price, the loss is realized. The trader also loses the option to keep the position open, although remaining invested would itself carry further market risk.

This is an illustrative calculation, not a documented loss arising from Bitget’s restrictions.

Forced closure can be especially disruptive for traders using perpetual futures as hedges.

Closing a short Bitcoin position while leaving a corresponding spot holding elsewhere would remove the protection against further price declines.

Customers with pending withdrawals face a separate risk. Bitget’s contractual powers include restrictions on transfers and, under specified conditions, asset conversions. The exchange’s assurance that customer funds remain safe should therefore be read separately from questions about withdrawal timing and continued account access.

The Terms Changed, but the Compliance Explanation Is Incomplete

The geographic restrictions also require closer examination.

Bitget’s October 16 English agreement names Russia, Belarus, Kazakhstan and Thailand among its prohibited jurisdictions. However, an older support-hosted version already listed Kazakhstan, while omitting Russia and Belarus.

That means Kazakhstan’s appearance in the current list should not automatically be described as a newly introduced prohibition. The clearest documented additions relative to that older version are Russia and Belarus, alongside Thailand.

The older documentation also illustrates a practical problem: customers consulting different versions of Bitget’s terms may receive conflicting information about eligibility.

Bitget’s compliance framework permits geographic restrictions based on sanctions exposure, regulatory requirements and internal risk assessments. Yet the company has not publicly identified a specific new law or enforcement decision requiring this particular offboarding exercise.

That leaves several questions unanswered: whether affected customers were selected by verified residence, operating location or other compliance criteria; how many accounts are being terminated; and what procedures remain available for withdrawals after login access is restricted.

The exchange has not provided a verified breakdown of affected balances or reported withdrawal problems by asset and blockchain network. Without those records, isolated customer complaints cannot establish a wider withdrawal failure.

For notified traders, the most important immediate document remains the account-specific notice. For the wider market, Bitget’s handling of withdrawals and outstanding positions will determine whether the policy change proceeds as an orderly compliance exercise or creates additional customer disputes.

The post Bitget Restricts Russia, Belarus and Kazakhstan Accounts appeared first on ETHNews.