{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/1/2026 10:17:56 AM
3
Persistent centipede and coconut error codes / Cannot Connect on PS5 (Multiple Accounts & Networks Tested)
Hi everyone,
I’ve been getting Error Code CENTIPEDE immediately when launching Destiny 2 on my PS5 for the past ~2 weeks. This prevents me from logging in. Also, I'm getting error code Coconut most of the time when I attempt to play a crucible game alone/with friends from other countries, or even something more simple like loading into the tower.
Here’s everything I’ve tried so far:
Restart the game multiple times
Tested on different PSN accounts on the same console - same result
Tested on mobile hotspot instead of home network - same result
Wired Ethernet with stable speeds (20 Mbps upload / 440 Mbps download)
Deleted and redownloaded the game
Cleared PS5 system cache in Safe Mode
Rebuilt PS5 database
Restarted console and router multiple times
Checked NAT Type - Type 2
I've been playing with 20 Mbps upload / 440 Mbps download and NAT type 2 for over 4 years now and never before had an issue. The game was working perfectly as well till 2 weeks ago.
Despite all this, the error persists before login on every attempt. Other online games work perfectly, so it’s not my connection.
Has anyone else experienced this recently? Any suggestions, or can Bungie staff advise on fixing it?
Thank you!
-
[quote]Hi everyone, I’ve been getting Error Code CENTIPEDE immediately when launching Destiny 2 on my PS5 for the past ~2 weeks. This prevents me from logging in. Also, I'm getting error code Coconut most of the time when I attempt to play a crucible game alone/with friends from other countries, or even something more simple like loading into the tower. Here’s everything I’ve tried so far: Restart the game multiple times Tested on different PSN accounts on the same console - same result Tested on mobile hotspot instead of home network - same result Wired Ethernet with stable speeds (20 Mbps upload / 440 Mbps download) Deleted and redownloaded the game Cleared PS5 system cache in Safe Mode Rebuilt PS5 database Restarted console and router multiple times Checked NAT Type - Type 2 I've been playing with 20 Mbps upload / 440 Mbps download and NAT type 2 for over 4 years now and never before had an issue. The game was working perfectly as well till 2 weeks ago. Despite all this, the error persists before login on every attempt. Other online games work perfectly, so it’s not my connection. Has anyone else experienced this recently? Any suggestions, or can Bungie staff advise on fixing it? Thank you![/quote] I have the exact same situation, it's been two weeks from coconut error codes, and honestly the only workaround has been restarting the game
-
1 ReplyHi there, Thanks for reaching out. Centipede and Coconut errors are both 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. Additionally, per our [url=https://help.bungie.net/hc/en-us/articles/360048717512-Error-Code-CENTIPEDE]Centipede page[/url] and given the persistent nature of your issue, the cause may be a limitation from your network administrator, if one exists: [quote]Please note: Not all NAT Type problems can be solved. If you are on a university or corporate network, or if your ISP limits what type of traffic you can send/receive you may have a NAT problem that is out of your control. You may need to contact your network administrator or ISP to help resolve this issue.[/quote] For troubleshooting, 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. 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.
-
1 ReplyEdited by Crisidelm: 4/1/2026 11:11:29 AMI play on PC but I also get Centipede randomly launching the game, and then instead of Coconut I often get Currant error, even simply trying to fly to the Tower. Already posted twice about this... I am wired by the way. Already tried: clearing Steam download cache verify game files Stun Test is Open (using UPnP) changing DNS and clearing the DNScache resetting Winsock tested connection to CenturyLink servers in USA (Spokane, near Seattle, in particular) without any problem tested my connection for packet loss and jitter (with USA servers), which are 0 (the former) below 1ms (the latter) These problems started with the launch of Marathon Server Slam (I had NO errors before)...
