[Updated] Destiny 2 Error code Centipede: Here's how to fix
New updates are being added at the bottom of this story…….
Original story (published on May 21, 2021) follows:
Bungie is not making it easy for the Destiny 2: New Light players as the game is always surrounded by bugs and issues.
Error code Beagle appeared recently that kept asking players on PlayStation 5 to reinstall the entire 75 GB pack after the hotfix update that aired recently.
As weird as it may sound, the company names these errors on actual worms. Players have so far witnessed Error code weasel, anteater, barracuda.
Well, here comes another one that has been affecting Destiny 2 players for quite some time now. It is the Error code Centipede that is doing the rounds now.
As per the reports, it appears when trying to log into a character, leading the game to crash soon after.
The error has been troubling players on all major platforms including the PlayStation 5. For some, it appears immediately after logging in, and for others, takes a couple of mins before crashing.
Perhaps, the company is already aware of the occurrence of this bug and there’s nothing they want to do to fix this.
The official website of Bungie mentions the Error code Centipede but only puts the blame on the internet with no other solution whatsoever.
Fixing Error code Centipede on Destiny 2
Being a common network error, this can be screened out by ensuring a stable network. Follow the preliminary steps
– If you are using WiFi, we recommend switching to a wired connection
– If your NAT is Strict or Type 3, we recommend getting your NAT into an Open or Type 1 state.
But it also notes that not every NAT issue can be resolved. For that, one will have to seek help from the internet service provider.
The game developers believe this to be something that goes on its own and depends on which area the game is being played in. The UK reported 25% of these error cases.
Other than this, the page says they are continuously monitoring the Centipede issue that has spoiled Destiny 2 for the folks and will address the issue soon.
That said, we will keep tracking this issue and update you guys as soon as we have a workaround or a permanent solution.
Update 1 (January 31)
Fortunately, Bungie has mitigated this issue, but it is not fully resolved and players may still get this error code until it is permanently fixed.
PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.