Thread title says it all, really.
I did all the troubleshooting I could, including resetting my router, assigning a static IP, changing DNS servers, clearing out the console's network cache, even making a fresh installation of the game. You name it, I've probably tried it. This happens both with wired and wireless connections.
Logging in is a feat in and of itself, and the few times I've managed to do it I'm getting constantly bombarded with currant and centipede errors every time I either try to load into an activity (where sometimes I get locked into loading screens between zones) or load out of a cutscene or a mission into orbit. And even there, the 'contacting destiny 2 server' message flashes more often than not.
It's worth noting that this is literally the only game I'm having issues with.
I've also tested my connection and there's no packet loss issues whatsoever. Please look into this.
-
1 ReplyHi there, Thanks for reaching out. Currant and Centipede errors are indicative of network issues. These can be caused by problems affecting your specific network hardware, packet loss, or greater issues affecting your ISP which are being passed on to you. Further, all of this is possible even if your connection seems fine at a glance. To that point, we recommend consulting our [url=https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide]Network Troubleshooting Guide[/url] to explore potential solutions you haven't already tried. If that doesn't help, the next step would be checking our [url=https://help.bungie.net/hc/en-us/articles/360049024092-Optimizing-Connections-Improving-Latency-and-Packet-Loss]Optimizing Connections[/url] page. Following that, if issues still persist, we would recommend reaching out to your ISP for more hands-on assistance in troubleshooting your network setup.