I've been encountering persistent [b]COCONUT[/b] and [b]CENTIPEDE[/b] error codes on PlayStation 5 that began about a week after MoT was released. I have checked my hardware and contacted my ISP regarding this issue. When trying to enter the game after launching (specifically after the screen with "Press X to play") I get the [b] CENTIPEDE [/b] error. When trying to launch activities with other players launching takes a long time and a [b]COCONUT[/b] error pops after a black screen forcing a relaunch of the activity. I'm using a Cat7 F/FTP wired Ethernet connection, and in the hopes of fixing things I've set up a manual Static IPv4 address on the PS5, placed the console's static IP into a dedicated DMZ slot on the Zyxel home router (Model: VMG8623-T50B). I disabled standard UPnP and UPnP NAT-T to prevent local port-negotiation conflicts. I also used secure third-party DNS (Cloudflare 1.1.1.1) and disabled IPv6 on my router to force IPv4 routing. Additionally I contacted my ISP (Nova, Greece) and migrated my line off CGNAT. The line now holds a dedicated, unshared Public IPv4 address (the console connection test shows NAT Type 2). I also run different tests with the different connections [b]Test A: Mobile Phone on Home Wi-Fi.[/b] Base ping 32ms. Latency during upload stays flat at 46.3ms with low jitter. This makes me believe that the physical VDSL line from my ISP is healthy and stable. [i]For the next ones I managed to also access the cloudflare speed test from the PS5 browser.[/i] [b]Test B: PS5 Console on Wireless Wi-Fi.[/b] Switching the PS5 to wireless successfully bypasses the initial boot-up CENTIPEDE error. But I still get the COCONUT error when trying to launch activities with other players. The cloudflare test using the PS5 hidden web browser shows, latency: 27,0ms (download 33ms, upload 114ms), jitter: 8,11ms (download 6,58ms, upload 45,2ms), unfortunately packet loss cannot be tested. [b]Test C: Mobile Data Hotspot (Vodafone Hellenic).[/b] Connecting the PS5 wirelessly to a 4G/5G cellular hotspot completely bypasses both error codes. Booting into orbit is without issues, and launching any activities is without any errors. Sometimes I get "contacting Destiny servers" but I'm guessing that's entirely because of the somewhat poor hotspot signal (also my phone overheats). The cloudflare test shows, latency: 52,0ms (download 65,5ms, upload 59ms), jitter: 7,84ms (download 17,8ms, upload 91,2ms). [b]Test D: Wired Connection (with public Static IPv4, DMZ, Cloudflare DNS, no UPNP, out of CGNAT). [/b] I still get error codes but they are fewer, only one CENTIPEDE after the "Press X" screen and only one COCONUT when trying to launch activities, on the second try the activity loads (most of the time). Latency 40,5ms (download 25ms, upload 115ms), jitter 24,4ms (download 10,5ms, upload 43,2ms). I've contacted my ISP and mentioned the high latency on upload but they said that they don't see anything out of the ordinary. I have also ordered a GL.iNet GL-SFT1200 router with cake SQM hoping that will fix things. (Final note: I've never before had serious issues like this, sure some errors here and there but nothing that didn't allow me to play on such a scale)