Network Setup Platform: PC Secondary platform tested: PS4 Slim (same network) Connection type: FTTH Gigabit FiberCop (TIM Italy) Router: TIM HUB PRO IP: Public IPv4 assigned (no CGNAT) Connection method: Ethernet, directly wired into the modem NAT type: Open, with DMZ and UPnP PPPoE: tried enabling it on PC (no improvement) DNS: default TIM / Cloudflare 1.1.1.1 / Google 8.8.8.8 (no improvements) Firewall: Defender, turned off during tests Antivirus: Malwarebytes, turned off during tests VPN: none at first, used only for testing Hello Team, Since around February, I've been getting constant Centipede errors during login, and various Currant errors when trying to join activities, along with occasional "Unable to contact Bungie servers" and Weasel errors. Once inside activities, the game mostly works flawlessly, with very few kicks back to orbit. In-game NAT is constantly reported as Open. I have no issues with any other online software or games, and I typically get very low ping (under 25ms) with a fast connection, no packet loss, and no jitter. In addition to the setup listed above, I disconnected all other devices from the modem, reset the modem multiple times, verified the condition of the fiber optic cable connection, replaced network cables, and contacted my ISP, who confirmed there were no issues between my network and theirs. I disabled all firewalls and tested with my PC in DMZ, with no improvement. I tested a PS4 Slim on the same network and the issue was present there as well. I also set up a PPPoE connection with my ISP, again with no improvement. After these tests, I found very similar reports from Italy and other Mediterranean countries such as Greece and Turkey. These reports started in February 2026 and are still being posted as of July. Here are a few of the most complete ones I found on the Bungie forums and Steam: Similar reports from Italy: https://www.bungie.net/it/Forums/Post/265295877?sort=0&page=0 https://www.bungie.net/af/Forums/Post/265301822?sort=0&page=0 https://steamcommunity.com/app/1085660/discussions/0/562534348863162492/ Eastern Europe and Italy: https://www.bungie.net/it/Forums/Post/265311449?sort=0&page=0 After reviewing these reports, and seeing that the situation hadn't improved with the latest June update, I tested my connection to the game servers using Wireshark and several network diagnostic commands, including mtr from a Linux distro installed via WSL. I've compiled a folder of categorized results from all my tests, with timestamps, which I'd be happy to share with Bungie support. In these tests, I noticed that the Centipede and Currant errors are generated after four failed attempts by my client to re-establish a connection with the server, and after a definitive server hangup during a TCP handshake; occurring during login and matchmaking, respectively. I tested the same IPs on the same game ports using mtr and pathping, and found that the affected Bungie IPs and often the hops near them, show 50% (sometimes over 60%) packet loss, with ping spiking as high as 9 seconds for some responses. After noticing this, I configured Mullvad VPN on my system and tested connections through Milan (I live in Tuscany), Vienna, London, Istanbul, and Athens. Both Vienna and London showed a healthy connection, with 0% packet loss and very low ping; I was finally able to play flawlessly. This was not the case for Italy, Turkey, and Greece; the same regions many of the reports above come from, which showed up to 40% packet loss and pings of 4+ seconds even in the best-case scenarios. The most critical hops were consistently the destination Bungie server itself, and the last few hops, often operated by Akamai Technologies. (Full details are included in the logs) As mentioned above, I'd like to get in touch with Bungie networking team to share these logs privately. Thank you for your time, and for reading this far.