JavaScript is required to use Bungie.net

Help - Destiny 2

Help us help you.
10/12/2026 11:23:52 AM
1

Destiny 2 – CENTIPEDE / WEASEL / COCONUT – TIM Italia – impossibile giocare

**Title: Destiny 2 – CENTIPEDE / WEASEL / COCONUT errors – TIM Italy** Hello, I am experiencing persistent connection problems with Destiny 2 on PC (Steam) that are preventing me from playing normally. The most important detail is that **I was able to play Destiny 2 without any problems until about one month ago**, using the same PC, the same Internet connection and the same router. Since then, I have started experiencing repeated disconnections and different networking errors, mainly: - CENTIPEDE - WEASEL - COCONUT Sometimes I cannot even reach the character selection screen. In other cases, I manage to enter the game and play for a few minutes before being disconnected. ### My setup - Windows 11 - Destiny 2 via Steam - Wired Ethernet connection (not Wi-Fi) - ISP: TIM Italy - Router: TIM H388X - Local PC IPv4: 192.168.1.8 ### Troubleshooting already performed I have already tried several troubleshooting steps: - Restarted both the PC and the router - Checked the Ethernet connection - Checked Windows Firewall - Tested connectivity with `ping 1.1.1.1` – 0% packet loss - Tested `ping bungie.net` – 0% packet loss - Ran `tracert bungie.net` – no obvious connectivity problems - Tried different DNS servers, including Google DNS (8.8.8.8) - Flushed the DNS cache - Checked Windows network configuration - Checked Steam network connections/ports - Enabled UPnP on the TIM router - Restarted the PC after enabling UPnP Interestingly, after enabling UPnP, Destiny 2 initially worked and I was able to play, but after a few minutes I was disconnected with WEASEL/COCONUT, and subsequently started receiving CENTIPEDE again. I also tested Windows TCP Auto-Tuning. With: `netsh int tcp set global autotuninglevel=disabled` I was able to play for approximately five minutes during one test. With Auto-Tuning set to "normal", I often cannot even reach the character selection screen before receiving CENTIPEDE. However, this has not permanently solved the problem. ### Additional information My general Internet connection appears to be working normally. Other Internet services and applications work correctly. The fact that Destiny 2 worked normally until approximately one month ago is what makes me suspect that this could potentially be related to routing, ISP connectivity, or a recent change affecting the connection between TIM Italy and Destiny 2 services. I have also seen reports from other Destiny 2 players in Italy experiencing similar CENTIPEDE/WEASEL/COCONUT errors while using TIM, although I cannot confirm whether the issues are related. Could you please let me know if there are any known connectivity or routing issues affecting TIM Italy, or if there are any additional specific network tests you would like me to perform? I would prefer not to keep changing router or Windows networking settings randomly without knowing which part of the connection is actually causing the problem. Thank you for your help.
English
#Help #pcsupport

Posting in language:

 

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

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