I’m constantly getting “contacting destiny servers” while sitting in the tower. Anyone I open the vault or change clothes.
Crucible and Gambit are throwing non-stop baboon errors everyone someone is killed in addition to the “contacting destiny servers”.
I haven’t had this problem EVER until the last Tuesday patch prior to this Tuesday's patch. I’ve flushed DNS and ensured that I’m on a 5g signal. Also does the same thing on a wired connection.
I know it’s not my connection. It’s definitely something on Bungies side and they’re not giving any useful information except blaming everyone else’s connection.
English
-
Bearbeitet von GoldEagleOne: 6/22/2023 8:55:23 AMSo this [i]could[/i] be on their end after all and nothing is wrong with my connection? The only reason I’m assuming this is indeed on my end is because it doesn’t seem to be such a widespread issue, They haven’t mentioned any increase in these errors on their Twitter and from looking at the help forums most of people’s issues don’t seem to be similar to mine. I’ve never experienced issues this bad as I’ve described and it only started about 4-5 days ago.
-
Exactly, that’s when I noticed it as well and am assuming that it has to do with the previous Tuesday patch. I myself have been searching Twitter and Google for a mention of it because I know it’s not on my side of networking. All other activities (except for crucible & gambit) for me seem to be somewhat ok other than the tower and switching gear/subclasses. That’s when it starts with the non-stop contacting destiny servers.
-
Well for me it’s been worse, I can’t really complete [i]any[/i] activity, at some point I just get contacting destiny 2 servers, then baboon, then weasel Patrolling, the tower, master lost sectors, strikes, raids and even just being in orbit. Can’t even join or rejoin people sometimes. It’s driving me crazy and I’m nonstop messing with my router and network settings and what not
-
Haha look at it now, they’re finally admitting it was them and not us!!
-
Funnily enough a few days ago my issue just solved by itself it seemed like, no weasel or baboon errors and my NAT type was suddenly open. I did have some trouble joining people manually as it said sometimes “unable to join target player due to a network error” but after restarting my router I was able to join people. But yeah, them finally admitting it now is hilarious, servers have been in shambles lately