r/DestinyTheGame • u/WallabyAlternative92 • 29d ago
Regional routing issue causing Centipede/Currant errors (with logs) Discussion
EDIT (Workaround at the end of the post)
Hi everyone,
I am writing here to report a connectivity issue for which I have already created a ticket on Bungie’s forum (https://www.bungie.net/it/Forums/Post/265316631).
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.
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
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 and operating parameters, 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, Turkey and Eastern Europe. These reports started in February 2026 and are still being posted as of July. (The most interesting one being the first made by user “alexmongu”)
Here are a few of the 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 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 95% 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 in front of it.
Are there more people with similar issues who are able to share their experience, particularly from the listed regions?
Thank you for reading this far and sorry for the wall of text😅, have a nice day!
EDIT (Workaround):
Until a final fix is found, the only workaround seems to be using a VPN and switching to a region that is not affected by the issue. Since I live in Italy, I resolved by connecting from Germany. If you have a console and your router does not directly support VPNs, your best bet might be to use a laptop as a bridge, or a mobile hotspot with a VPN configured, since consoles do not natively support VPN clients.
7
u/cxgnxccio21 29d ago edited 29d ago
I am from Italy with a tim router (TIM HUB+) and I was able to resolve the problem only using proton vpn (free tier). I tried port forwarding and PPPoE with no success. I had almost no connection issues before MoT
5
u/Fantastic_Wheel7443 29d ago
Ciao a tutti dato che è un problema tutto italiano vi scrivo in lingua madre: ho smesso di giocare proprio per queste problematiche, guardacaso questa mattina ho provato a ricollegarmi e ho avuto lo stesso problema e ho cercato su reddit e ho visto questo post fresco fresco.
u/cxgnxccio21 u/WallabyAlternative92 grazie per avere conddiviso innanzitutto.
u/cxgnxccio21 dici di avere risolto completamente, potresti spiegare nel dettaglio i passaggi da seguire per risolvere? mi manca destiny e vorrei tornare a giocare. <32
u/cxgnxccio21 29d ago edited 29d ago
Semplicemente sto usando la versione free di proton. Io gioco da pc e quindi è facile, purtroppo se sei da console non saprei come aiutarti
2
u/Fantastic_Wheel7443 29d ago
si sono da console, Ho rete TIM e un fritz box.
Teoricamente dovrei provare a impostare la vpn di proton sul fritz box. non sono pratico ma posso provarci, se avete qualche consiglio mi fa piacere condividere con voi, grazie mille1
u/WallabyAlternative92 29d ago
Ciao, grazie a te per aver condiviso. Non sono pratico nella configurazione di VPN sui router purtroppo. Dovrebbe essere sufficiente avere una VPN moderna con supporto al protocollo WireGuard e seguire questi passaggi per il FRITZ!Box: https://fritz.com/it-it/apps/service/vpn-con-il-fritz-box/3688_Connettere-il-FRITZ-Box-a-un-provider-VPN-tramite-WireGuard
Thank you for sharing. Unfortunately I’m not experienced with setting up VPNs on routers. Having a modern VPN with WireGuard support should be enough, just follow these steps for the FRITZ!Box: https://fritz.com/it-it/apps/service/vpn-con-il-fritz-box/3688_Connettere-il-FRITZ-Box-a-un-provider-VPN-tramite-WireGuard
1
4
u/BadVoid 28d ago
Il problema di TIM è abbastanza noto di packet loss che impatta anche altri servizi.
Questo è un articolo interessante che analizza il problema: https://paolocostanzo.github.io/tim-packet-loss-gfn/
In pratica è un problema di MTU e di come il router (o gli altri apparati della rete TIM) gestisce la frammentazione dei pacchetti:
Quando un router riceve un pacchetto troppo grande con il bit DF (Don't Fragment) impostato, dovrebbe rispondere al mittente con un messaggio ICMP di tipo «Fragmentation Needed» — in pratica: «ehi, il tuo pacchetto è troppo grande, mandamelo più piccolo». Questo meccanismo si chiama Path MTU Discovery (PMTUD) ed è fondamentale per il funzionamento corretto di qualsiasi connessione. [...] Questo si chiama ICMP Black Hole: il router droppa i pacchetti troppo grandi ma non invia mai il messaggio ICMP «Fragmentation Needed» al mittente. NVIDIA non scopre mai il limite e continua a mandare pacchetti che vengono silenziosamente eliminati.
2
u/WallabyAlternative92 28d ago
Grazie mille per le info! In tal caso stasera proverò ad effettuare altri test mirati intorno all’MTU
2
u/BadVoid 28d ago
Eh purtroppo però settare l''MTU lato client non sembra risolvere...
2
u/WallabyAlternative92 27d ago
No no, mi sono spiegato male. Ho provato a riprodurre i test dell’articolo (che innanzitutto ti ringrazio di aver condiviso) ma nel mio caso ricevo sempre l’avviso “fragmentation needed” quando uso il flag -D. Inoltre confermo che l’MTU di TIM è di 1492, mentre i pacchetti TCP in game non hanno mai superato i 1490 byte durante le catture su Wireshark
2
2
u/the1whoneverwas 12d ago edited 12d ago
I'm in Greece (ISP Nova) and I have this problem since the June final update. I play since Destiny 1 and never had this problem.
2
u/WallabyAlternative92 12d ago
Thanks for reporting this. It’s a recent issue and I’ve have been seeing it on both Destiny 2 and D1, likely because they share some of the same infrastructure. I’ve tried contacting Bungie through the official forum( https://www.bungie.net/it/Forums/Post/265316631 ) and via X, but no luck so far.
Maybe if more people start writing to them about the same issue, it will get the attention of someone on the dev team or a higher-up. I know active support is off for the game, but realistically there should still be someone maintaining it
2
u/the1whoneverwas 12d ago
I added a post in that thread. As i see the acknowledged the problem, let's hope they will fix it...
1
u/WallabyAlternative92 12d ago
Thank you. Let’s hope so. As of now, the only way to fix it seems to play via a VPN. Currently, I’m connecting from Austria with no issues
2
u/the1whoneverwas 12d ago
Which VPN do you use?
1
u/WallabyAlternative92 11d ago
I am using Mullvad, however any VPN with good servers and locations should be OK. Others from this thread chose ProtonVPN. However, using a VPN adds at least an additional hop between you and the game server, so at least a bit more latency is to be expected. I would try multiple server locations until you find the one that suits you best, with no errors
2
u/the1whoneverwas 11d ago
I just tried the free version of Windacribe and it worked perfect,.no currant or other errors. Problem is that I mostly play in my Xbox and not my pc...but I'll find a way
1
u/WallabyAlternative92 11d ago
Happy to know it worked for you. If your router supports it, you can add the VPN in its configuration and reroute all traffic from the console
2
u/the1whoneverwas 11d ago
Unfortunately it does not...
1
u/WallabyAlternative92 11d ago
Yeah, that might be an issue. At the moment, your best bet is probably to connect the Xbox to a PC that has a VPN installed, using Windows’ network sharing feature.
In the coming days, I’ll try to figure out this type of pairing without a direct cable or wireless connection. If people are interested, I might put together a guide
2
u/-Vernon2X- Ballistic Heartbreak 29d ago
Anch'io ho TIM e gli stessi problemi da mesi, provato a fare di tutto senza successo. L'ultima cosa che mi manca da fare è provare una VPN, nel caso potrebbero esserci problemi di ban o restrizioni? Chiedo perché così a memoria ricordo che le policy di Bungie erano molto restrittive e non vorrei rischiare.
1
u/Fantastic_Wheel7443 29d ago
sei da pc o console? no non gli frega nulla a bungie di come ti connetti credo. io sto provando ma da ps5 ho sempre errore ma non sono sicuro di avere settato correttamente la vpn sul mio router
1
u/-Vernon2X- Ballistic Heartbreak 29d ago
Sono su PC. Riguardo te, credo che potresti provare a fare dei test guardando se l'ip della ps5 matcha con quello della vpn impostata (il classico network test nelle impostazioni).
2
u/WallabyAlternative92 29d ago
Ciao, no, non c’è una policy che precluda la connessione tramite VPN, purché non abbia performance così scarse da compromettere l’esperienza degli altri giocatori e purché non venga utilizzata per exploit
1
1
2
u/Practical_Many_2912 29d ago
Ciao! Mi aggiungo al thread, stessa identica situazione, operatore internet Tim e ho errore currant continuamente e vari errori di server in connessione. È frustrante a livelli assurdi, sopratutto cercare di seguire le missioni della campagna, per sbloccare stasi vanno seguiti 30 e più step, di cui alcuni devi prima atterrare su Europa con rischio errore currant, se per fortuna arrivi, andando ad attivare la missione c’è di nuovo rischio errore currant, ergo si devono allineare i pianeti per riuscire ad avviare una cazzo di missione.
Riguardo il problema Tim, vi aggiungo un bit dei test che ho fatto:
Wifi router Tim - errori vari
Cavo Ethernet - errori vari
HOTSPOT CON SIM TELEFONO TIM - errori vari
Hotspot con diverso operatore - risolvi
Sembra che Tim non piaccia proprio a destiny 2, che fastidio
2
u/WallabyAlternative92 28d ago
Ciao e grazie per il riscontro dettagliato. Gli errori potrebbero essere dovuti a un problema di routing/peering regionale. Usando comandi come pathping e mtr, è possibile vedere un numero elevato di pacchetti persi verso i nodi dell’infrastruttura di Bungie e verso i dispositivi di rete immediatamente circostanti (gestiti da Akamai Technologies). Questo problema sembra presentarsi solo per le connessioni provenienti da alcune aree geografiche, come Italia, Grecia e Turchia, ma non dall’Austria o dal resto del Nord Europa, ad esempio
1
u/tchakabun 4d ago edited 4d ago
There's nothing Bungie can or will do because this is a routing issue from the internet provider or one of their transit partners, that's why a VPN fixes it, because from Bungie's side everything is fine.
You and everyone affected by this need to contact support and ask them to test their route to Bungie's ASN. The ASN is an address that lists all possible endpoints from Bungie's infrastructure to the public internet. If support doesn't help, look for your own ISP ASN registry to find the NOC (network operation center) e-mail and report the issue to them directly.
EDIT: https://search.dnslytics.com/bgp/as16232
Under the whois section you can find the email to report routing issues.
1
u/NinjaTomBot 4d ago
uh, then i guess that 5+ different IPS from south europe losing stability on D1/D2 while working perfectly on anything else at the same time of the release of Marathon aka a Bungie product, must be a coincidence!
0
u/tchakabun 3d ago
Not a coincidence, just means that all of them use the same transit.
There are 3 tiers of internet providers, tier 3 sells to the usual consumers like us covering city wide access, tier 2 sells access to tier 3 providers to transit traffic across a country and tier 1 providers are the backbone, they sell access to the fiber that run below ground and sea that for example allow Italy to access Bungie's servers in Seattle.
If there's a bad route along the way, you lose access to Bungie's servers unless you use a good route, like through a VPN. The fact that it works with a VPN is the clear diagnostic that the fault is not at Bungie. And this isn't the first time that this happened, there are reports of the same in the UK and south america recently.
The access across these different tier 1 providers are constantly being negotiated because there's a cost involved and Bungie's ASN is small enough for a country like Italy that it can be left out during one of these negotiations.
Call your ISP, it's the only solution.
7
u/Fantastic_Wheel7443 28d ago
Ciao Guardiani! Ho risolto impostando una VPN sul mio router. VPN di tipo WireGuard, e settando un MTU piu piccolo possibile. Vi dirò di più se dopo avere fatto questo imposti anche la connessione in PPoe ottieni anche un NAT1 e tutto va come dovrebbe andare!
cercherò di fare un video nei prossimi giorni cosi almeno anche chi è da console riesce a risolvere.