Hello there, Thank you for reaching out. WEASEL is primarily a networking error, but there are a few less-obvious causes and advanced checks that are worth going through. Below is a focused checklist that could help. 1. Rule out account / ban / multi-login issues From Bungie Help, WEASEL is a general networking error, but it can also appear: When you’re logged into the same Bungie account on multiple platforms at once with Cross Save enabled. At the moment a restriction/ban is applied (the WEASEL is an effect, not the cause). Actions: Log into Bungie.net in a browser: Check for any ban/restriction notice on your profile or the Destiny Account Restrictions and Banning Policies page. Make sure you are signed out on all other platforms (PlayStation/Xbox/Steam/Epic/etc.), then launch on just one device. 2. Do a full power cycle (not just restart the game) Bungie specifically recommends this if WEASEL stops you from launching/playing at all. Console: Hold the console’s Power button for 5–10 seconds until it fully shuts down. Unplug the power cable for 30–60 seconds. Power off your modem and router for 30–60 seconds, then power them back on. Once the internet is back, turn the console back on and try Destiny 2 again. PC: Fully shut down the PC (not sleep). Power-cycle modem and router as above. Boot PC and try Destiny 2 again. 3. Force a wired, clean network test Even if your connection is “stable” generally, Destiny 2 is sensitive to brief packet loss or strict NAT. If you’re on Wi-Fi, switch to Ethernet directly into the router. Bungie strongly recommends this for WEASEL errors. If possible, connect your console/PC directly to the modem, bypassing the home router as a test: If it works reliably that way, the router (firmware, firewall, or QoS) is likely the culprit. On your platform’s network settings, confirm your NAT Type is: Open / Type 1 / Type 2 preferred. If it’s Strict or fails UPnP tests, that can cause recurring WEASEL. If NAT is strict or moderate and doesn’t improve: Follow Bungie’s official Network Troubleshooting Guide, Optimizing Connections, and Advanced Troubleshooting: UPnP, Port Forwarding, and NAT Types (even if you’ve already tried manual port forwards — removing incorrect forwards and relying on UPnP often works better). 4. Router-specific checks Some routers cause periodic WEASEL disconnects even on otherwise strong connections (seen a lot with certain Netgear and D-Link models). If you can safely do so: Disable any extra router firewall/IDS features (e.g., SPI firewall, aggressive intrusion detection) as a test. Ensure UPnP is enabled and remove manual port forwarding rules you added while troubleshooting; misconfigured rules can hurt more than help. Temporarily turn off QoS or, in some cases, enable vendor “Dynamic QoS” if your router has a known bug in default traffic handling (documented for some Netgear Nighthawk models). If you have access to another router (even a basic one), test with that to see if the issue disappears. Only keep these changes if they actually improve the situation; otherwise revert to your previous secure config. 5. PC-specific steps (if you’re on Steam/Epic/MS Store) Community and support threads recommend these PC steps for stubborn WEASEL/BEE issues: Verify game files: Steam: Destiny 2 > Properties > Installed Files > Verify integrity. Epic/MS Store: run their equivalent “verify/repair” option. Clear the launcher cache (Steam download cache or equivalent). Make sure Windows and GPU drivers are fully up to date. Run SFC/DISM to rule out OS file corruption (optional but useful if nothing else works). Temporarily disable or exit overlays and network-filtering tools: Discord game overlay, GeForce Experience overlay, VPNs, third-party firewalls, or “gamer network optimizer” apps. 6. Clear clan invites & unlink the mobile app (older but still relevant edge cases) Some players have resolved persistent WEASEL by dealing with clan invites and the Destiny companion app: On Bungie.net, go to Memberships / Clans: Accept then immediately leave, or otherwise clear, any pending clan invites. Still on Bungie.net, under Settings → Accounts & Linking, unlink the Destiny mobile app auth. Uninstall the Destiny 2 mobile app from your phone, just as a test. Try launching the game again. 7. Test a completely different network To determine if the problem is path/ISP-related despite what they told you: Try launching Destiny 2 from: A mobile hotspot, or A different home/network (friend’s place, etc.). If it works fine on the other network, the issue is almost certainly: Your router, or The route between your ISP and Bungie (something only your ISP/Bungie can adjust). That evidence is useful if you go back to your ISP for deeper investigation of routing/packet-loss to Bungie’s endpoints.