Constant error codes since the new season when I rarely got any before
Ever since the new season, but especially in the past 2 weeks, my connection to the game has gotten worse and worse, to the point where I physically cannot play the game anymore.
Before season 18, I very rarely received error codes or had connection issues. I would get weaseled from time to time at random, but that's been happening since D1. But now, I get so many weasel, baboon and anteater codes that I can't even play the game anymore. I am constantly contacting Destiny 2 servers, and I get kicked to orbit or to the title screen so often I can barely finish an expedition, let alone a raid encounter or an entire one. I started getting more error codes as the season went on, but it was still bearable. In the last week, I've been getting kicked from almost every activity and I've had to drop out of every raid I've attempted after getting error coded multiple times per encounter. It's now a coin flip on if I'll get kicked to the title screen before I can finish an expedition.
I am pretty sure the issue is not on my end, as I am still able to play any other game just fine and even while I am disconnecting from the game, I am still perfectly able to talk to my friends on discord. I know other clanmates have also seen WAY more frequent error codes, but I haven't seen anyone else disconnect as often as I have.
I've tried contacting my ISP but everything is apparently fine on that side.
Is there anything I can do? Does anyone else have this issue? What in the actual hell is up with the servers this season?
I’ve got the same problem, started this season, can barely log in and when I do manage to get into the game I tend to get a couple hours of stable play time at most. Sometimes it takes half an hour or more to even sign in. It’s definitely not my internet which is actually better than it was last season after my ISP did a big hardware upgrade, and all other online games and services are fine so it can’t be a hardware issue, so the logical conclusion is that it’s a problem on the server side. I was hoping today’s (September 22nd) maintenance might help but it is now post maintenance and it almost seems worse.