A wave of freezes for users from Russia and the CIS: not one cause
A wave of restrictions for users from Russia and the CIS rarely reduces to one exchange and one cause: chats mix AML exposure, a SoF request, geo/KYC limits, and a P2P dispute. Classify your notice first, not someone else's "scale". The two-day checklist is below; typical triggers are in the top reasons accounts are frozen. If withdrawals are already blocked, see exchange account unfreezing.
Similar symptoms, different mechanisms
When several people you know see a withdrawal pause in the same week, it is easy to treat it as one campaign against a region. In practice several tracks often overlap: deposit screening after label updates, a source-of-funds request on large turnover, a fiat-channel or product limit, a P2P chargeback, or a KYC and device mismatch. A shared geography does not make every ticket the same case.
Public "frozen across all platforms" totals from chats are almost never verifiable. For your account, the dashboard status, notice text, and case number matter — not someone else's infographic. Platforms publish different help articles on restricted accounts, additional information, and verification limits; use those, not a recap.
Keep the sanctions layer separate: lists and packages change, and analytics vendors refresh service labels. That can raise the frequency of manual reviews for people who touched higher-risk venues or P2P flow, but it does not turn every regional passport into an automatic ban. Class overview: top reasons exchange accounts are frozen.
AML, SoF, geo, and P2P: how to tell from the letter
Read the wording, not the chat headline. "Exposure / high-risk / origin of funds" is closer to AML/SoF. "Residency / restricted jurisdiction / complete verification" is closer to access and KYC. "Payment dispute / P2P / chargeback" is a fiat dispute. A security hold after a 2FA or password change is a separate short stop; a SoF package does not treat it.
Mixing classes hurts: a geo channel limit is answered with identity and address; an AML hold is answered with a TxID table. The same user can receive both layers in sequence. If it is unclear, save both texts and do not send a "universal archive just in case".
| Signal in the account | Likely class | First package |
|---|---|---|
| Deposit risk / exposure | AML | TxIDs, hops, trade context |
| Origin of funds / wealth | SoF / SoW | Statements, amount matching |
| Residency / restricted product | Geo / KYC | Current profile data |
| P2P / chargeback | Fiat dispute | Chat, bank, timeline |
First 48 hours: a checklist
- Sign in only through the official site or app; save a status screenshot, the email, and the case number.
- Classify the wording: AML, SoF, geo/KYC, P2P, or a security stop after 2FA.
- Build one package strictly for that request; leave extra passports and the seed phrase out.
- Submit through the official channel and record the date; do not open parallel tickets.
- Do not withdraw "anywhere" through a new hop, friends, or a second account — for AML that is a new chain.
- If the class looks like a Bybit withdrawal hold, compare with Bybit withdrawal freeze: first steps.
A fuller two-day plan is in frozen crypto: what to do. While the package is incomplete, escalation and "unfreeze it now" almost never speed up the manual queue. If the restriction already blocks withdrawals, keep exchange account unfreezing and the case studies in view. The outcome is not guaranteed.
What not to do during a wave of restrictions
- Do not rely on someone else's "scale" figures or Telegram timelines.
- Do not turn on a VPN to look like another country or open a second account "just in case".
- Do not route the remainder through an informal exchanger to "beat sanctions" — that often raises the next AML alert.
- Do not sign someone else's documents or pay an "unfreeze guarantee" upfront.
A wave in the feed is not a diagnosis of your ticket. Calm classification and one package matched to the letter beat a panic withdrawal copied from someone else. Help-center wording changes: reread the current notice in the account before you send.
Risks and limitations
- Similar symptoms across users do not mean one cause or one unfreezing route.
- A complete document package does not guarantee that a restriction will be lifted or reviewed on a set timeline.
- Sanctions lists, access rules, and AML screening thresholds are updated.
- A panic withdrawal through a new hop, a VPN, or a second account often worsens the AML picture.
- This article is a practical orientation, not legal advice and not an estimate of "market scale".