How R6 bans actually happen
There is no single 'ban button'. Understanding which system caught you decides what you have to fix.
- BattlEye detection: kernel-level scans of loaded drivers, injected modules, hooked functions and signature matches. Detections are usually batched into ban waves rather than issued instantly.
- Server-side analytics: Ubisoft models headshot ratio, time-to-kill, flick velocity, wall-tracking and pre-aim consistency. Statistical outliers get flagged for review even if BattlEye sees nothing.
- Player reports + replays: Siege ships with Match Replay. Any reported player's rounds can be re-watched from every angle, which makes visual tells far more dangerous in R6 than in games without replays.
Most cheaters who get banned with a clean, undetected build were caught by the last two systems — not the first.
Hardware identity: spoof before you ever launch
BattlEye HWID bans persist across accounts. If you have ever been banned on this machine, a new account on the same hardware is banned again within days.
- Run your HWID spoofer BEFORE the first launch of the session, every session — never mid-game, never after Siege is already running.
- Spoof the full identifier set: SMBIOS/motherboard serial, disk serials, MAC address, GPU/monitor EDID, TPM where the spoofer supports it.
- Reboot after spoofing if the spoofer requires it. A half-applied spoof is worse than none because it produces an inconsistent fingerprint.
- Never mix a clean account with a previously banned Windows install without spoofing. Same install, same fingerprint, same ban.
See our HWID guide for the identifier-by-identifier breakdown.
Account and purchase hygiene
Ubisoft links accounts through payment methods, emails, IP history and friend graphs. One banned account can drag its siblings down.
- One cheating account per email, per payment method. Never buy Siege on the account you care about with the same card as a burner.
- Do not add your main friends list to a cheat account. Shared-lobby graphs are a manual-review signal.
- Age the account: play 5-10 unranked matches without cheats before you turn anything on. Brand-new-account plus impossible stats is the fastest flag in the game.
- Avoid free/trial and heavily discounted key-reseller accounts — they carry pre-existing risk flags.
Network and VPN discipline
Network signals rarely ban you alone, but they connect accounts together.
- Pick one consistent identity per account: either always your real IP or always the same VPN exit. Jumping between five countries per week looks like account sharing or resale.
- Use residential or clean datacentre exits. Widely-abused free VPN ranges are already correlated with thousands of banned accounts.
- Never run two Siege accounts from the same IP in the same session if one of them is a burner.
Cheat configuration that survives ban waves
Even undetected builds get you banned if the configuration produces impossible telemetry.
- Aimbot FOV: 3-5 degrees. Anything above 15 degrees is visible in a replay to a casual viewer.
- Smoothing 25-40, humanisation/jitter 30-50%, first-shot delay 80-180ms. These three settings are what turn 'flagged outlier' into 'good player'.
- Hold-to-aim on ADS only. Never toggle-on aim — it snaps while you sprint, rappel and reload, and every snap is a replay frame.
- ESP: skeletons only, 20-40m cap, no health bars, no through-wall boxes across the map. Prefer radar, which never appears in a replay.
- Turn off no-recoil, silent aim, instant-kill and any 'server-side' feature. Those write impossible values into match telemetry, which is server-detected regardless of BattlEye.
- Never stream, screen-share or screenshot with the overlay visible. Discord screen share of your own overlay is a common self-report.
Behaviour during ban waves and updates
Most R6 bans arrive in clustered waves, usually shortly after a patch or seasonal update.
- Do not launch after a Siege patch until your provider confirms the build is updated and safe. Launching an outdated cheat into a patched anti-cheat is the single most common ban cause.
- Check the status page before every session. If a product is marked updating, stay off the game entirely, not just off the cheat.
- If your community reports a wave in progress, take 48-72 hours off. Detections in-wave get retroactively applied to sessions already played.
Keep your stats under the review ceiling
Analytics flag distributions, not single kills.
- Target a 45-60% headshot rate. Above 70% sustained is a review trigger at any rank.
- Keep your K/D under roughly 3.0 in ranked. Dropping 40-kill games repeatedly guarantees reports and manual review.
- Lose rounds and matches. A 100% win streak across dozens of ranked games gets accounts reviewed on its own.
- Do not smurf-stomp low ranks with cheats on. Skill-gap-plus-cheat telemetry is trivially separable from legitimate high-skill play.
If you do get banned
Assume the ban is permanent and hardware-linked until proven otherwise.
- Do not appeal with a false story. Appeals get your case read by a human with your full telemetry in front of them.
- Re-spoof HWID, use a new Windows account or install, new Ubisoft account, new email, new payment method.
- Work out which layer caught you: instant ban mid-match usually means detection; ban days later after a reported game usually means replay review; ban in a cluster with other users means a wave.
- Fix the layer that failed before you play again. Buying a different cheat does not fix a behavioural ban.