{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/17/2022 5:15:46 PM
33
Unable to connect to Destiny 2 Servers
I can find no evidence of an outage. I'm able to launch the game, but never get to the guardian selection. Anything going on? I get a weasel error code. Can someone help?
English
#Help
-
2 RepliesHi there, thank you for your report. We are aware of players reporting this issue and are actively investigating.
-
Am having sever issues for the past two days, now contacting destiny 2 severs bullsh*t
-
Mines down for more than 8 hours . Its double rank weekend and bungie does this . very impressive
-
Now again. What is this. This is a joke....
-
Now i got the error again.
-
Hi. This error is a pain. Why do i get this all the time, but the other in my team dont. Dont live far apart, We have same internett connection fiber 500 mb down 500 mb up. Iam om PC. Dont think its my pc spec thats holding me back. Done all i can find on the problem, but still it pops up "weasel" error. Hardware Cpu Ryzen 9 5900x Hk: Msi Meg Unify x570 Gpu KFA2 GeForce RTX 3080 Ti EXG Mem: Team group T-force xtreem argb ddr4-3600 cl14 32gb (2X16gb) M2 Drives: Samsung 980 PRO 1Tb ,Samsung 960 Evo 512Gb, Kingston 1Tb Psu: 2 Corsair AX 1200W/tot 2400W My god this error is getting me angry.
-
I'm facing the same issue since half and hour, got connected once but it worked fine for few minutes, their server status website says there's a maintenance update going on without any exact ETA
-
I restarted my console and that seemed to work. Dunno if that actually did anything though.
-
3 RepliesEdited by ADragonWithin: 8/17/2022 5:47:48 PMThe connection fails were definitely noticed, even several of us Mentors also had the issue; it may be fixing itself now as some people are able to log in and play now. It was relatively quick, so is possible Bungie might or might not announce that it was an issue since it seems to be getting resolved. Start trying to log in now to see if everything's all set. If not, give it a bit more time and try again. Bungie.net and the apps also had a funky thing where they were showing no characters for D2; characters didn't get deleted, it was just the API having trouble reading the data.
-
i can't stay connected to save my life i can play the game for a minute to even an hour before it starts giving me Weasel Error new modem and everything same problem unistalled the game reinstalled it verified game files still same results and season is nearly over and im afraid ill miss out on the pass rewards :(
-
Hi internet connection checked, modem reset but when I try and choose a character I get error code weasel.
-
same here
-
1 ReplySame issue here had the weasel code pop about more than 50 times.
-
same boat but there are people playing
-
2 RepliesSame thing, also companion app will not work
-
I keep getting a weasel error every time I try to log in as well. East coast USA
-
I’m getting the same code weasel
-
Edited by Madducks: 8/17/2022 5:32:18 PMI'm seeing the same thing. My game, nor 3rd party apps are able to connect to Bungie servers. Date: 8/17/22 Time: 10:30 AM Pacific. Issue: Unable to connect to Destiny 2 servers Error code: Weasel. Hardware: Xbox series X Location: near Seattle, WA Service Provider: Xfinity Note: Other games working without issue. Description: When attempting to connect in-game, I either receive the error after hitting 'A' on the launch screen (on Xbox Series X), or the Character Selection screen. After multiple attempts, I can only get to the Character Selection screen occasionally.
-
Bump, same issues here.
-
Same here "weasel error code" 1:24pm East coast
-
1 ReplySame issue as well
-
I have been having the same issue with logging on and with the D2 app as well!
-
Same. I got to the character selection screen finally once, but then right after got the weasel error like the rest of the time.
-
Update it fixed itself I just kept reloading D2. I’m on Series X
-
I also am receiving error trying to log on
-
same with me
