I had this problem (Weasel error every 2 hours basically on the dot) for a long time and it turned out to be the router's fault. If you have the Netgear Nighthawk R7000P router, you can find posts all over reddit and here with this exact issue being described. You can fix the issue completely by enabling a setting on your router called Dynamic QoS. I honestly trashed my nighthawk router after realizing it was causing me so many problems for years in favor of a tp-link that has done perfectly fine for me since. If you have a different router, look for the QoS setting in your router settings to enable it to see if it fixes it. Hopefully this fixes your issue, I'm trying to spread the word!

I've managed to be completely free of this awful issue for over a year. As of this last patch June 14th, the issue is back in full force, weasel error coded every 2 hours. Bungie please help. :(

Posting again as after almost two months of no issues, this is back with a vengeance. No amount of cache clearing, modem/router cycling, etc seems to fix it. Really wish I could get help resolving this for good, it ruins raiding and end game.

Just posting here again because this is still a problem. 2 years and counting! Weirdly after the Beyond Light launch I was fortunate enough to have [b]zero issues with this for like 5 weeks[/b], but suddenly this has reared its ugly head again. Every 2 hours or so, weasels like clockwork. Tried everything I can try. Wish Bungie could help get this figured out.

It may help soms people who are constantly getting kicked out of game. Every few minutes you get message where it says connecting to destiny servers and then it kicks you to main screen with error code weasel. I will create a video later. I will explain what i did in brief. I was getting this error because of router. My router is D-Link dir 816. Have 50mbps up and down connection. So coming to steps, 1. You have to disable SPI in firewall section of router. Also disable any firewall in router. 2. on your console go to network settings and take photo of the connection details such as ip address, subnet mask, gateway, mac address depending on your conection wired or wireless you should note address. You are going to nedd this. 3.now log into your router. And assign a static local ip address to your console. For which you took photo. In Dlink router there is section of dhcp reservation you should enable that and assign ip to your console and save. 4. Once you assign ip. Go to network setting on your console and ip setting and assign the ip address reserved in router to your console. You can refer this link https://portforward.com/networking/static-ip-xbox-one/ 5. After all this done check test your connection you should get open nat and connection is working fine. If there is mismatch in details while updating ip setting in console then you might get connection issues. 6.If you get connection ok message and nat is open we go to last step. 7. Again log back into router. Activate DMZ. And add your console and its IP into dmz and save. You can google what it is. Thats what available in dlink router in other you need to check. Now you will no longer get weasel error.i have tested this, it worked for me should work for others.

Since Season of Arrivals I and my wife are having this exact issue, it's maddening for raids! We have UPnP enabled on our router; we have 400+ Mbps down/25+ up; and I have not changed ISPs or any hardware other than a new router that is the same manufacturer. My Xbox One is wired to the LAN, wife's is on WiFi. We will USUALLY get Weaseled the same time, two hours after we start playing, on the dot. Every two hours. However, once in a while (last night it was twice) where one of us is Weaseled and the other isn't. I'm an IT professional. I've went over my Netgear R7000P routers settings several times. I've done most of the basic troubleshooting (flush of Xbox One caches, factory reset both it and the router; hard restart of the Xboxes and so on). I'm very reluctant to turn off UPnP and do port forwarding since I have other devices on the network that utilize it. I really think this must be on the Xbox One/Bungie side of things but find no answers or responses from either company on this issue. So frustrating that I can't enjoy the game as intended and do end level content reliably.

Try this guide https://quoramarketing.com/destiny-2-error-code-weasel-fix/

And not surprisingly, within two hours of play in Shadowkeep, after months of no problems, error code weasel returns and kicks me. Same thing yesterday. I assume based on the trend that I’ll be dealing with this for at least the next month since Bungie doesn’t seem to care about it. Edit: they stopped showing up for me last week, faster than expected!

Update: completely disappeared for months and instantly reappeared when Season of Opulence dropped. I get error code Weasel every two hours on repeat. Has been going on for a week now. Bungie, please help me, this is awful.

I feel you man. I have the EXACT SAME problem. Wired Xbox X. Solid internet connection. Ports forwarded per instructions... I get a Weasel error pretty consistently every 2 hours or so. It'll flash "Contacting Destiny Servers" twice, then white screen, Weasel error. It almost always dumps me back to the title screen after that. I first noticed it post Forsaken, and just like you, it stopped for a bit at some point (maybe during Black Armory??)... it's now back again. It was only once, but I went to a friend's for a LAN party recently, and it even happened there too. I've just been putting up with it, but it is very annoying. Luckily, I don't raid much, so the worst I've had it happen is the occasional drop from a Gambit match or something like that.

Aaaand with Season of the Drifter these are magically back. No problems for many months. Every couple hours I get kicked with error code weasel. Bungie, please fix this!