Despite its many years in the market, Destiny 2 isn’t immune to some system errors that become a hindrance for many players, such as the Code Centipede one. While some errors occur due to some player actions, a faulty file, or other things, this one pertains to connectivity and is usually not that hard to solve. If you’re one of the unlucky Guardians who are struggling with this, we have a few tips that will help you get back into the action.
[Updated on July 15, 2025: Added other possible fixes to this error for The Edge of Fate expansion.]
Fixing Error Code Centipede in Destiny 2
According to the official website, Error Code Centipede in Destiny 2 pertains to a loss of connection to the game’s servers. Furthermore, it seems that this is one of the least intrusive and annoying errors out there, and most of the time, the issue gets solved on its own. If it doesn’t, here are a few workarounds you can try.
Switching to a Wired Connection
The first possible fix is quite easy. As many of us know, a wired connection is much better than gaming on Wi-Fi. If you’re using the latter, chances are your connection loss occurred because of that. If so, switch to a wired connection and try logging into the game again.
Change Your IPv4 Properties
This next solution is a recent one, and the credit goes to user JetPilot0721 on the r/DestinyTechSupport subreddit. Even if it’s one year old, it’s still a solution that has helped many, at least when the issue comes from the players’ end and not from the game’s server. To attempt to fix the Error Code Centipede in Destiny 2, you can do the following:
- Press Alt+R to open Windows’ command function.
- Type in “ncpa.cpl”
- Once you’re at the Network Connections screen, select your active internet connection, be it Wi-Fi or wired.
- Right-click on it and open the Properties tab.
- Select the “Internet Protocol Version 4” option and head to Properties again.
- Leave the above window open, and then hit Alt+R again and type cmd.
- When the command window opens, type “ipconfig/all” and hit enter.
- From the new window, you’ll need to grab your address, subnet mask, and default gateway information.
- Return to the Internet Protocol Version 4 tab that you left open and click on “Use the following IP address.” You’ll need to input your address, subnet mask, and default gateway here.
The user who found this solution also mentions that they added Google’s Public DNS server to the options in the Inter Protocol Version 4 Properties window. Input 8.8.8.8 in the first field and 8.8.8.4 in the second field. Once that’s done, you should be able to jump back into the game.
Other Workarounds
Bungie also says that changing your NAT to Type 1 or Open might work. Doing so isn’t recommended, though, since it might expose your network to vulnerabilities, so we don’t think it is a good idea. Instead, you can check to see if there are any pending updates on the game or if Destiny 2 is experiencing any server issues that might prompt the Error Code Centipede to appear. If the above things do not help you, it is likely an issue on Bungie’s end, and things might get fixed soon enough.
