Keep getting centipede everytime i log on. Tried everything, nat type is open, hard reset, uninstall and reinstall. Nothing works! Cant even play the game
-
Same here down in FL my power went out for a sec a few days ago then after that centipede I'm able to play once in a while if I keep trying
-
From what I`ve read, this seems to affect florida spectrum users...me included. Everything works like it should except D2 The DNS change will do nothing for console users. NOTHING The ONLY way I can get on the game is to reset my modem. Either unplug it..wait a bit..plug it in..wait for connection..fire up xbox and log in to D2. Or you can reset using the spectrum app. So far it`s worked every time. BUT THIS IS NOT A FIX I have to do this every time I want to get on D2 I don`t know who did what, but I sure wish they would fix it like ASAP!
-
Hey guys, I was able to fix it for PC using a wired connection. The problem is definitely Spectrum DNS. You need to go to the "Network Connections" screen in windows, right click your adapter and click properties. Highlight the checked line that says Internet Protocol Version 4, click properties. Go down to the bottom and change your local PC DNS to use Google DNS. 8.8.8.8 8.8.4.4 - alternative. Restart your PC after and the game should start up fine.
-
Edited by CHbball20: 6/6/2023 1:32:09 AMYou all aren't alone. I have been experiencing the same issue, in FL, on Spectrum. I linked the thread I commented on below. https://www.bungie.net/en/Forums/Post/262938387?sort=0&page=0 It has been happening constantly over the last few days, with brief breaks where I can play. I have yet to see any Bungie support staff acknowledge the issue and state that they are looking into it, all I have seen is them state that it is on our/our ISP's end. It is getting frustrating, especially since I have seen people write that their ISP says it is not their issue. Whoever's issue it may be, it needs to get fixed or at least addressed. I am disappointed that I cannot reliably play this game anymore due to factors outside of my control and no one seems to be attempting to fix it.
-
Edited by hexad: 6/5/2023 12:37:50 PMI am having this issue as well. Did anyone else notice a BattleEye error right before the first time it happened? I have since tried to uninstall/install BattleEye and destiny 2 and have had no luck. My network driver is up to date as well and still all I get is error code Centipede. EDIT: Worth noting as well that I am East Coast and on Spectrum internet.
-
Edited by xMiss Medic: 6/5/2023 4:42:25 PMI keep getting this aswell. I’ve done everything you can think of. I’ve hard reset numerous of times. I’ve cleared my MAC address. I’ve forgot my internet and reconnected it. I’ve reset my internet numerous of times and last resort I uninstalled and reinstalled. I have NO issues with any of my other online multiplayer games. Has anyone figured this out? I am in FL and on spectrum internet and on console.
-
I think the problem is on Bungie's side because until just a day ago i had strong connection on first try and now it seems like im getting swarmed by centipedes!
-
I found out through down detector that here in FL it looks like its a local server, and to use a VPN as a workaround. Good luck
-
Same Here. For no apparent reason, I cannot log into the game because of non-stop "Centipede" error codes. I have NAT on open I've uninstalled and reinstalled the entire game. I've rebooted Xbox and cleared the cache. I've reset the router. For all other games, I have no problems, this is only a Bungie issue. Waiting impatiently for a fix.
-
Edit: now I keep getting marionberry
-
Same -- when I use my phone's hotspot to login first then swap to my regular wifi it works just fine, but otherwise absolutely nothing I can do nonstop centipede. bungie needs to look asap.
-
I am having the same issue. verified all my files, restarted everything. I can log in to other online games no problem from steam so its definitely Destiny.
-
Got mine to work. I tried the flushing dns, ipconfig release/renew and that didn't help. Then I opened network connections, disabled my ethernet network, reenabled and it worked.
-
Same how did you fix it