How to Fix Destiny 2 Error Code Weasel (Disconnected)
What Error Code Weasel means
Error code Weasel is one of Destiny 2's most common disconnect errors, and it's frustratingly vague: mid-activity — sometimes mid-raid — the screen freezes for a second and you're suddenly staring at the title screen with a small "WEASEL" error message and a prompt to log back in. No crash, no frozen console, just an abrupt boot from the game.
Bungie's official help page gives two main explanations. The first is a Cross Save issue: players with Cross Save enabled who log in to the same account on multiple platforms simultaneously will receive a WEASEL error on whichever platform they logged in on first. In other words, if you open Destiny 2 on your PC and then boot it up on your PlayStation with the same account, the PC session gets kicked. The second is a ban-related one: if you're in an activity at the moment a ban is applied to your account, you're returned to the title screen with the Weasel error. Beyond those official explanations, players and Bungie's own troubleshooting guides also associate Weasel with server maintenance and general network trouble — packet loss, ISP congestion, and unstable Wi-Fi connections can all produce it.
The good news is that your account and progress are almost always fine. Weasel is a session disconnect, not a corruption or deletion event — your characters, gear, and seasonal progress live on Bungie's servers, not on your device. The fix is about restoring a clean, single session: making sure nothing else is logged into your account, confirming the servers are actually up, and ruling out your network. That's exactly the order the steps below follow, because checking the server status first saves you from an hour of pointless troubleshooting when the real problem is maintenance.
Common causes
- Logged in on two platforms at once: with Cross Save enabled, opening Destiny 2 on a second device kicks the first session back to the title screen with Weasel.
- Destiny companion app session: the phone app keeps a session tied to your Bungie account, which can trigger Weasel exactly like a second logged-in console.
- Server maintenance or background updates: during scheduled maintenance or major content drops, sessions get dropped and Weasel appears.
- Unstable network connection: Wi-Fi packet loss, ISP congestion, or a flaky route to Bungie's servers can disconnect you mid-activity.
- Corrupted console cache or stale session data: temporary files and a stale connection handshake can keep the error returning until the hardware is fully power-cycled.
How to fix Error Code Weasel — step by step
Work through these fixes in order. Weasel is frequently a Bungie-side problem, which is why the list starts with the check that saves you from troubleshooting something you can't fix.
- Check Bungie's server status first. Before changing anything, confirm the problem isn't on Bungie's side. Open the Bungie Help page or the @BungieHelp account on X and look for maintenance notices or a known outage. Error code Weasel frequently appears during scheduled maintenance or background updates, and when that's the cause, no amount of troubleshooting on your end will fix it — the game simply has to come back online. If maintenance is announced, log out and wait until Bungie confirms the servers are stable again before continuing.
- Make sure you're logged in on only one platform. According to Bungie's official help documentation, Weasel appears when players with Cross Save enabled attempt to log in to the same account on multiple platforms at the same time. If Destiny 2 is open on your PC and also booted on a console, the first session gets kicked back to the title screen with the Weasel error. Quit the game completely on every other device — PC, PlayStation, Xbox, or mobile via the companion app — and log in on just one platform. Then relaunch and sign in again.
- Power-cycle your console or PC. Temporary files and a stale network session can keep the error coming back. On PlayStation or Xbox, power the console down completely, unplug the power cable for about 30 seconds, then plug it back in and boot up. On PC, shut the machine down fully instead of restarting, wait a few seconds, then start it again. This clears the console cache and forces a fresh connection handshake with Bungie's servers.
- Switch to a wired connection and restart your network. Bungie's own troubleshooting guidance for Weasel recommends switching from Wi-Fi to a wired Ethernet connection, at least temporarily. Unplug your router and modem for at least 60 seconds, plug them back in, and wait for the connection lights to stabilize. If you normally play over Wi-Fi, run an Ethernet cable to your PC or console for the test session. Packet loss and unstable wireless connections are common silent triggers for Destiny 2 disconnections.
- Unlink the Destiny companion app from your account. The Destiny companion app on your phone keeps a session tied to your Bungie account, and that background session can trigger Weasel the same way a second logged-in console would. Sign in at bungie.net, click your profile icon, and open Settings. Go to Accounts & Links, find the companion app under linked applications, and select Unlink. Then sign out of the app on your phone and uninstall it. Relaunch Destiny 2 on your main platform and test whether the error is gone.
- Clear pending clan invites or leave your clan temporarily. Some players report that lingering clan issues can contribute to connection errors. Sign in at bungie.net, open the Clan section, and clear out any pending clan invites. If you're a member of a clan, consider leaving it temporarily as a test — open the Destiny 2 companion features on bungie.net, go to the Clan menu, open your Clan Profile, and choose the leave option. Let your clan admin know first so you can rejoin afterward. If the error stops, the clan data was the culprit.
Did this fix it? Quick checklist
- You can log in and stay in orbit without a Weasel error
- Bungie's status page shows no active maintenance or outage
- Destiny 2 is running on only one platform and the companion app is unlinked
- Your console or PC is on a stable wired connection
If Weasel still keeps appearing, try logging in on a different platform to rule out a device-specific problem, and check that no one else shares your account credentials on another machine. As a last resort, a clean reinstall of Destiny 2 clears every cached file, but try the full list above first — reinstalling a game this large is slow and rarely fixes what is fundamentally a session or network problem.
Frequently asked questions
What does error code Weasel mean in Destiny 2?
According to Bungie's official help page, error code Weasel appears in two main situations. First, when a player with Cross Save enabled logs in to the same account on multiple platforms at the same time — the platform logged in first gets disconnected to the title screen. Second, when a player is in an activity at the moment a ban is applied to their account, they are returned to the title screen with the Weasel error. It can also show up during server maintenance and general network trouble.
Does error code Weasel mean I've been banned?
Not necessarily. A ban is only one possible trigger — Bungie notes that if you're in an activity when a ban is applied, the disconnect happens with a Weasel error. But the vast majority of Weasel errors are caused by logging in on two platforms at once, the companion app session, or network issues. If you haven't received any ban notification from Bungie, assume it's a session or network problem and work through the fixes above.
Why do I get Weasel even when I'm only logged in once?
The second session doesn't have to be a second console. The Destiny companion app on your phone holds a session on your Bungie account, and Bungie.net logged in on another browser can count too. If the error persists after unlinking the app, also try switching from Wi-Fi to a wired connection and power-cycling your network hardware — packet loss and unstable routes to Bungie's servers can produce the same error message.
Can server maintenance cause error code Weasel?
Yes. Weasel is one of several Destiny 2 error codes that appear during scheduled maintenance, background updates, and new content drops. When Bungie's servers are under maintenance, the game can fail to keep your session alive and drop you to the title screen with Weasel. Always check @BungieHelp on X or the Bungie Help status page before troubleshooting — if maintenance is announced, the only fix is to wait it out.
How long does error code Weasel usually last?
If the cause is on Bungie's side — maintenance or a server outage — it typically clears within a few hours once their team restores normal service. If the cause is on your side, such as a second logged-in session or a bad network connection, it lasts until you fix the underlying problem. Most players who follow the steps in order are back in the game within 15 minutes.