{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by alexmongu:
6/29/2026 2:57:20 PM
13
Persistent Centipede / Currant / Coconut errors on Destiny 2 (TIM FTTH Italy – possible routing issue)
Hello Bungie Support / Networking Team,
I am reporting persistent and reproducible connectivity issues affecting Destiny 2 for multiple users on TIM (Italy), which appear to be related to routing or connectivity between ISP networks and Destiny 2 servers.
For approximately the last 4 months, I have been experiencing frequent connection errors in Destiny 2:
Centipede – during login / initial connection to servers
Currant – during matchmaking / activity launch
Coconut – during loading into activities (after matchmaking succeeds)
The issue is inconsistent but frequent, occurring across all activities and game modes.
[b]Environment[/b]
Platform: PlayStation 5
Secondary platform tested: PC (same network)
Connection type: FTTH FiberCop (TIM Italy)
Router: TIM HUB PRO
IP: Public IPv4 assigned (not CGNAT)
Connection method: Ethernet (wired)
NAT type: Open
PPPoE: enabled on console (legacy configuration used since previous PlayStation generations)
DNS: default TIM / tested without improvement
Key observations
The issue occurs on both PS5 and PC using the same FTTH connection.
The issue is random and intermittent:
Several successful activity launches (e.g. 5 in a row)
Followed by multiple consecutive failures (e.g. 10–20 failed attempts)
The problem occurs at all hours of the day, including off-peak hours.
The issue affects all activity types, including solo activities.
When switching to a mobile hotspot connection, the issue disappears completely:
No Centipede errors
No Currant/Coconut errors
Activities load normally every time
The issue began around the time of the Marathon server test period, and multiple other users on TIM (Italy), including both FTTH and FTTC connections, report identical symptoms starting in the same timeframe.
What has already been tested
Restarting router and ONT
Changing DNS
Verifying NAT type (Open NAT confirmed)
Port forwarding / UPnP enabled
Testing on multiple devices (PS5 and PC)
Wired Ethernet connection
Reinstalling / clearing cache
Switching between wired and wireless
Using mobile hotspot (problem disappears completely)
Based on testing, the issue does not appear to be related to local network configuration or hardware.
The most likely cause appears to be:
Routing / peering instability between TIM (Italy) networks and Destiny 2 backend infrastructure or intermediate transit providers.
The fact that the issue disappears completely when using a mobile network strongly suggests a path-dependent connectivity problem rather than a client-side issue.
Could you please investigate whether:
There are known routing issues affecting TIM (Italy) users
Any recent changes in server infrastructure or matchmaking/instance routing could affect ISP-level connectivity
Any specific IP ranges or network paths might be experiencing instability or packet loss
If needed, I am available to provide further logs or testing results.
-
Same here, constant Currant and connecting to the server issues going on for weeks, Currant occuring almost half of the time when matchmaking. Location: Turkey / ISP: Turknet. PC using Steam. Open NAT, UPnP enabled.
-
1 ReplyHi there, Thanks for reaching out. These issues affecting some players with Italian ISPs have been flagged to the team, and we can confirm they're looking into the situation. We apologize for the inconvenience caused.
-
1 Reply[u][b]Additional observation[/b][/u]: Everyone in my regular fireteam uses different ISPs (Fastweb, Sky Wifi, Vodafone and WindTre) and none of them experience these issues. The only two players consistently affected are both using TIM (FTTH and FTTC).
-
have the exact same issue, it's been happening since marathon server testing, then got fixed last month but the June 9th update messed it up again, still haven't found a fix and it's getting annoying. Unfortunate
-
1 ReplyAdditional information after further testing: Another TIM Italy user (FTTC) tested Cloudflare WARP. Without WARP: frequent Centipede, Currant and Coconut errors. With WARP enabled: all three error codes disappeared. However, Destiny 2 reported Strict NAT and matchmaking only created empty instances (matchmade activities launched solo). This strongly suggests that changing the network path removes the connection errors, while WARP itself is not a viable permanent solution for Destiny 2 due to matchmaking restrictions. This seems to further support the hypothesis of a routing/peering issue rather than a local network configuration problem.
-
1 ReplyI have the same issue. Both PC and console connection issues, currant and coconuts. Occasionally "destiny servers not available" (also both platforms) and my wired local connection. Once I swap to my mobile hotspot, no issues. But... I have another account that works on the exact same connection and platform during that time with no issues. So it might be related to something on the account causing issues like ornaments/guns that could cause crashes in the past. I dont know why its related to the connection as well, but I literally could not play on my main getting error codes etc, but no issues on my alt.
-
same issue
-
Same issues, but I don't think anyone's left at Bungie who can even look at logs lol
-
Same issue on Xbox. The game is pretty much unplayable, I wish they'd at least acknowledge there's a problem on their end rather than hitting us with the same automated replies I've seen in other threads, including my own. Great effort on reporting it in such detail. Thanks man.
-
same issue here buddy. i cannot explain better than u thank friend for what you've did
-
Same here, probelms started with the june 9th update. Networking team please look at this, this is also a problem on Marathon.
-
same issue
-
1 ReplySame issues here since last update. Location: Malta Playing on PC NO changes in network performed pre update but constant Currant errors. Game is unplayable.
