{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/20/2026 12:40:44 AM
2
Recurring "Currant" and "Centipede" errors network verified clean, no fix found Message:
I've been experiencing recurring disconnects in Destiny 2 for weeks now, with two different error codes: Currant and Centipede. Both kick me to the Director or crash me right before/during activities.
I've done extensive network troubleshooting before posting this:
UPnP enabled and working correctly (properly mapping Teredo and Demonware ports)
Tested DMZ pointed directly at my PC
Continuous ping during play sessions (to 8.8.8.8 and to www.bungie.net): 0% packet loss, stable latency
WinMTR run twice while playing, including at the exact moment of the error: 0% real packet loss across all hops to destination (some intermediate hops don't respond to ICMP, but that's normal and doesn't affect the hops after them)
Connection is Wi-Fi (no ethernet option available to me right now)
Router: Huawei HG8145V5
Despite my connection testing clean across the board in all these tests, both errors keep happening consistently. I'd like to know if there's something specific to my account, region, or servers that could be causing this, since I've ruled out everything under my control.
Platform: PC
Region: Mexico
Bungie Name: Sabrina Carpenter#5126
-
5 回覆Ok so this is an issue since marathon came out for some people. There's been loads of posts here about it and the typical answer is a bot saying how we should check the networking guide etc.... It's been an issue affecting mostly players in Eastern Europe. Italy Greece and Turkey has loads of players with this problem. Some say changing ISP fixes the issue , some say using a VPN fixes the issue but we haven't had a clear answer to this. I made a post about this last week and not even the bot responded to check the network troubleshooting guide. I'm not sure if the remaining Devs are aware of this and I don't have high hopes of this getting fixed any time soon. I recently found out when you are in a fireteam and you are the leader and you get the error code when trying to queue anything but Trials , your teammates get suspended for matches that never started.
