Key Highlights:
- Ubisoft shut down Rainbow Six Siege after a major security breach caused false bans, strange messages, and huge amounts of in-game currency to appear on accounts.
- The publisher confirmed players would not be punished and rolled back all progress to before the incident.
- R6 Siege servers are now back online, though the Marketplace remains offline as Ubisoft continues monitoring the situation.
Ubisoft temporarily took Rainbow Six Siege offline after a serious security incident disrupted live servers and the in-game economy. Players began reporting abnormal behaviour on December 27, including system-style messages appearing mid-match, sudden bans that later reversed themselves, and billions of Renown and R6 Credits being added to accounts without warning.
In some cases, developer-only cosmetics also became usable.
This was not a typical cheating problem. From the outside, it looked like someone had gained access far deeper than normal exploits allow.
Matches became unpredictable, accounts were flagged incorrectly, and the Marketplace economy started to spiral as players listed and sold items using currency that should never have existed.
The timing could not have been worse for Ubisoft. Rainbow 6 Siege is in the middle of anniversary celebrations, daily reward drops, and limited-time content designed to keep engagement high. The game has also been experimenting with wildcard modifiers and collaboration cosmetics, all of which rely on a stable backend and player trust. Once that trust wobbles, even briefly, the damage spreads fast.
Ubisoft responded by shutting down R6 Siege and the Marketplace entirely while investigating. The studio avoided using the word “hack” publicly, but it did confirm the shutdown was intentional and necessary. A few hours later, Ubisoft clarified several key points that helped calm the situation.
Most importantly, players would not be banned for spending the credits they received during the incident. That decision matters. If you log in and suddenly see millions of credits on your account, most players are going to interact with the store out of instinct. Punishing people for that would have been disastrous.
Ubisoft also confirmed it would roll back all accounts and transactions to 11:00 UTC on December 27, which it identified as a safe point before the disruption began. This rollback covered purchases, Marketplace sales, and other account changes made during the incident.
The studio also explained that a ShieldGuard banwave occurred around the same time, but it was unrelated to the breach itself, which helped explain some of the confusion around bans.
From a player perspective, the experience was chaotic. I have seen plenty of Siege controversies over the years, but this was different. It felt less like a balance issue or a cheater problem and more like the foundations briefly gave way. People were not asking how to counter something. They were asking whether their accounts were safe at all.
Ubisoft has now begun restoring services. R6 Siege servers are back online and matchmaking appears to be functioning normally. Accounts that were affected by the rollback are returning to their pre-incident state, with items restored and illegitimate credits removed. Marketplace transactions made during the breach are being reversed, which is why the Marketplace itself remains offline for now.
Early reports suggest most inventories and cosmetics are behaving as expected, though it would not be surprising if edge cases continue to surface over the next few days. Ubisoft is likely prioritising core play first, then the Marketplace, then missed rewards from the anniversary period. Compensation has not been confirmed, but historically Siege has offered make-good rewards when outages last this long.
This is not the first time Siege has suffered a holiday-period security scare, and that is part of why this incident has hit a nerve. For a game approaching a decade of live service, stability and confidence matter as much as new content. Ubisoft has invested heavily in anti-cheat and security messaging, so an incident of this scale naturally raises uncomfortable questions.
At the same time, live-service development is unforgiving. When things work, no one notices. When they break, everyone does. Ubisoft’s decision to shut everything down quickly, protect players from punishment, and reset the damage rather than doubling down was the correct call in my opinion.
For the time being, Siege is playable again, the worst of the chaos appears contained, and the focus shifts to whether this was a one-off breach or a warning sign. Ubisoft will need to show that the door is firmly shut this time, because patience wears thin much faster than credits ever did.