JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will be temporarily offline tomorrow for scheduled maintenance. Click here to view latest Destiny Server and Update Status.

Help - Destiny 2

Help us help you.
Edited by Nski: 7/5/2026 12:16:05 PM
1

Constant CENTIPEDE and COCONUT error codes in Destiny 2 (Cyprus)

Hi Bungie, I'm posting because I've been experiencing constant **Centipede** and **Coconut** error codes, and at this point I'm convinced this is not an issue with my local setup. Here's what's happening: * I'm on PS5 using a wired Ethernet connection. * My internet connection is stable with excellent speeds, 400MBps download and 25MBps upload speeds. * I have no packet loss. * My NAT Type is Type 2 (Normal for PlayStation). * I've replaced and tested my Ethernet cable. * I've gone through every troubleshooting step on the Bungie Help pages and many suggestions from the community. * I've also tested other online games like warframe, apex legends, fortnite and call of duty and non show any network issues or even lag. The issue first started around the **Marathon playtest period**. It was extremely bad for several months, then around **2 months ago** it completely disappeared. During that time I could play normally without disconnects. However, after the **June 9 update**, the problem returned full force. Current symptoms: * I get spammed Coconut before I can even fully load into an activity. * Playing with friends is impossible because I keep getting the fireteam error coded with coconut while matchmaking or loading in. * Even when playing solo, it can take 3–4 attempts just to enter a single activity from the amount of spam. * The errors happen across different activities, not just one playlist. I also noticed Bungie acknowledged that some Italian ISPs were experiencing routing/connectivity issues with Bungie servers. I'm located in Cyprus, and I'm wondering if there could be a similar routing issue affecting players here or elsewhere in the region. Since my local connection is stable and this problem seems to have changed based on Destiny updates rather than changes to my home network, I'm hoping Bungie can investigate whether there's a server-side or regional networking issue. Is anyone else from Cyprus or nearby countries experiencing the same Centipede/Coconut errors since the June 9 update? Any help or acknowledgement from Bungie would be greatly appreciated because the game is currently very difficult to play. Thank you.
English
#Help #Errorcodes

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I have the same problem, I'm in Greece, I have a 1gbps FTH connection and actually it all started on the 9th of June update. Matchmaking or going in the tower is almost impossible from constant currant errors. And I face the same error in ps5/pc/Xbox series x.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    1 Reply
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon