Detailed analysis
Error Code: Weasel in Destiny 2 means you got disconnected from Bungie's servers. It's the most common Destiny 2 error code and covers everything from server outages to your account being logged in elsewhere. The fastest fix: make sure you're not signed in on another platform, restart your router, and switch to a wired Ethernet connection if you're on Wi-Fi.
What's actually happening
Weasel is Bungie's catch-all disconnection code. When the connection between your game client and Bungie's servers drops for any reason, you get Weasel. Unlike more specific error codes (Baboon for packet loss, Centipede for total connection failure), Weasel just means the link was broken and Bungie isn't sure why. It can happen because of server problems, your network, or even account-level conflicts.
The particularly frustrating thing about Weasel is that it boots you from whatever activity you're in — and in Destiny 2, that can mean losing raid progress, a Trials card, or a Nightfall completion. Getting disconnected at the final boss of a two-hour raid is a special kind of pain, and it's why sorting this out matters.
The most common causes (in order of likelihood)
Bungie server instability — Destiny 2's servers have rough patches, especially around weekly resets (Tuesdays), new season launches, and when Xur arrives on Fridays. During these windows, Weasel affects huge numbers of players simultaneously and there's nothing to fix on your end.
Cross-save account conflict — If you have cross-save enabled and you're logged into Destiny 2 on your PC and someone (or you) logs in on your PlayStation, Xbox, or another device, Bungie immediately kicks the first session with a Weasel error. Only one active session is allowed per account across all platforms.
Wi-Fi instability — Destiny 2 is one of the most network-sensitive online games. It uses a hybrid peer-to-peer and server architecture for many activities, which means even tiny packet drops that you'd never notice in other games cause disconnects. Wi-Fi drops packets constantly, especially on crowded 2.4GHz bands.
NAT type issues — Destiny 2 relies heavily on peer-to-peer connections for fireteam activities. If your NAT type is Strict (Type 3), your console or PC can't properly connect to other players' machines, and the connection falls apart in activities that require peer communication.
ISP routing problems — Some ISPs have intermittent routing issues to Bungie's data centers. Your general internet works fine, but the specific path to Bungie's servers hits a congested or broken node.
How to fix it
First, check if it's Bungie's fault. Go to help.bungie.net and look for active alerts, or check @BungieHelp on Twitter/X. If they've posted about known issues, you're done troubleshooting — wait for Bungie to fix it. You can also check downdetector.com/status/destiny-2 for a spike in player reports. If thousands of people are all getting Weasel at the same time, the servers are having a bad day.
Make sure your account isn't logged in elsewhere. If you have cross-save enabled, check that Destiny 2 isn't running on another platform — PlayStation, Xbox, Stadia (cloud), or another PC. Close the game on all other devices before trying again. This is one of the most overlooked causes because people forget they left the game running on a console in another room.
Switch to a wired Ethernet connection. This single change fixes Weasel for more people than any other step. Destiny 2's network code is unforgiving — a Wi-Fi connection that's perfectly fine for streaming or web browsing will cause constant disconnects in D2. Run an Ethernet cable from your router to your PC or console. If that's not physically possible, a powerline adapter (which sends network signal through your home's electrical wiring) is the next best option. It's not as fast as direct Ethernet but it's far more stable than Wi-Fi for gaming.
Restart your router and modem. Unplug both from power, wait a full 60 seconds (actually count — this matters because capacitors need to fully discharge), then plug the modem in first. Wait for all its lights to stabilize (usually 2-3 minutes), then plug in the router. This clears the NAT table, refreshes your IP lease, and resolves routing weirdness.
Fix your NAT type. On PC, open your router's admin page (usually 192.168.1.1 or 192.168.0.1 in a browser) and enable UPnP (Universal Plug and Play). This lets Destiny 2 automatically open the ports it needs. If UPnP doesn't help, manually port forward these ports to your PC's local IP address: TCP 80, 443, 1935-1936, 3097, 3478-3480 and UDP 3074, 3097, 3478-3479. You can find your local IP by opening Command Prompt and typing ipconfig — look for IPv4 Address under your active connection.
Flush your DNS. Open Command Prompt as Administrator and run ipconfig /flushdns. Consider switching to Cloudflare DNS (1.1.1.1 / 1.0.0.1) or Google DNS (8.8.8.8 / 8.8.4.4) for faster and more reliable DNS resolution.
Verify game files if you're on PC. In Steam, right-click Destiny 2 > Properties > Installed Files > Verify Integrity of Game Files. On Epic Games Store, click the three dots next to Destiny 2 and select Verify. Corrupted game files can cause Weasel during activity transitions.
Disable any VPN. Bungie's servers actively reject connections from many VPN IP ranges. If you're using a VPN for privacy, disable it before launching Destiny
2. The connection will be direct and Bungie won't flag it.
Is this a hardware or software problem?
Weasel is a network problem. Your GPU, CPU, RAM, and storage are not involved at all. The fix is always about stabilizing the connection between your machine and Bungie's servers. If Weasel happens once every few weeks, it's probably Bungie's servers having a hiccup — don't worry about it. If it happens multiple times per session, focus on your network: wired connection, NAT type, and router health are the big three. If you can play other online games like Fortnite or Warzone without disconnects, Destiny 2's unique peer-to-peer networking is likely clashing with your NAT type or router configuration. If you're not sure, Crashless can check your drivers, temps, VRAM, and 400+ known patterns automatically — just use the chat above.
Games commonly affected
Weasel is specific to Destiny 2, but the network fixes here apply to other Bungie titles (Marathon when it launches). Similar connection-drop errors in other games include Warzone's "Connection Failed" messages, Apex Legends' code:leaf and code:net, and Fortnite's network timeout errors. If you're getting disconnected across multiple online games, the issue is definitely on your network side.
Frequently asked questions
Q: I got Weasel during a raid and lost my checkpoint. Is there any way to get it back?
A: Destiny 2 raid checkpoints persist for the weekly reset. If you were the fireteam leader and had the checkpoint before getting disconnected, you should still have it when you log back in. Launch the raid solo and check if the checkpoint loads. If someone else was leader, ask them to invite you back.
Q: Does getting Weasel in competitive or Trials count as a loss?
A: Yes. Bungie treats all disconnects as losses in competitive playlists, and repeated disconnects in Trials will result in a temporary matchmaking restriction. Fix the underlying issue before playing competitive modes.
Q: Weasel only happens during specific activities like Gambit or Trials. Why?
A: Activities with heavy peer-to-peer networking (Gambit, Crucible, Trials) are more sensitive to NAT and packet loss than server-authoritative activities (Strikes, Raids). If Weasel only hits in PvP modes, your NAT type is almost certainly the issue. Enable UPnP or port forward.