I have been having these issues for the last 2 weeks. Nothing much before that. No networking settings was changed on my end pre and post TFS. This week appears to be much more error prone.
From time to time, ''Contacting Destiny 2 servers'' pops up and then data lags a bit. Sometime it's followed by weasels and it's assorted group of error code friends. I am not sure what to do, i tried making sure Firewall is letting D2 pass, restarting my routers and systems and nth seems to work.
I dun have any issue with network with World of Warcraft for example, no lag outs or even anything remote at all. I can stream videos without breaks with Destiny 2 on and D2 seems to be the only program that's having ''connectivity issues''.
Any help out there Guardians?
-
1 답변Same problem here. Everything was fine before The Final Shape. I don't know what happened, it's really annoying to play pvp for example when you get that "Connecting..." message all the time
-
Just an update, i contacted my ISP again after another week of contacting and weasel and my ISP escalated internally and routed my net service to another route on their end. The problem APPEARS to be gone for now. I do not need to use VPN and so far, not much contacting and error code. Will cont to monitor this.
-
5 답변I'm having same issue as you currently , its a constant battle of error codes and Contacting Destiny 2 servers pop up messages. I'm very very frustrated . It was fine a week ago then suddenly i started to have this issue. pls bungie help
-
작성자: Soleras 6/20/2024 1:57:23 PMWell it seems to have started again. During prime time lol it does appear that Bungie's server's buckling under the load. Edit: So i tried a VPN to US and i dun have any connection error codes or pop up BUT i am not able to matchmake anything at all. Currently at wits end on how to fix this issue. Edit 2: constantly getting weaseled at Char screen.
-
2 답변also getting weasel randomly during my gameplay, tried everything they suggested to do from their help page, still facing the issue. if you found a solution, please share it, would love to find a fix for this issue.