{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/14/2023 6:06:11 PM
10
Constant Baboon/Weasel errors since ~2 hours before reset today
Hello,
I've been getting constant "Contacting Destiny 2 Servers..." all morning and into this afternoon's reset. I've been getting kicked from instances with the "Baboon" error code and occasionally getting "Weasel" errors when I'm in an activity.
There doesn't seem to be any issues with my internet, other applications on my home and work PCs work fine with no connection issues. In game it says I have a "Moderate NAT Type", I switched to Open NAT through my router but that did not help. I've tried reseting my router and restarting my PC several times.
I've been keeping an eye on BungieHelp Twitter to see if it's a more widespread issue, but so far it seems to be an issue specific to me. I rarely have connection issues like this outside of the typical issues the servers have.
Is there anything else I can try other than what I have listed above?
-
1 返信Same issue and it started for me when I changed the ISP, since I am on fiber optics problem started. If I use a mobile phone for connection it works fine. Is it something about the fiber optics type of connection that causes the problems? Or just a cheap router that comes with it. The first idea was it is wi-fi connection that is weak or it clashed with other networks around me. But then I used LAN cable to connect and same problems. For now, I think it is a cheap router and lacks of options in the settings, or something about fiber connection. If I find any solution I will post it here. P.S. During the first encounter in the raid I lost connection around 5-6 times and seconds before finishing it I dropped the connection and lost a chance for sweet loot. Then I decided to use a hot spot from a phone to finish the raid.
-
2 通の返信Also me, same problem. I have amazing internet connection, 1GB-down1GB-up, 1000% is not on my end.
