I’m done being polite, so I’ll be direct. For months, Destiny 2 has been unusable for me. [b]CENTIPEDE[/b], [b]CURRANT[/b], and an endless “[b]Contacting Destiny 2 servers[/b].” Some days I can’t even log in. The errors started around the time of the Marathon tests. Other Italian players on TIM report the same thing. Not everyone is affected, and most players on other ISPs are fine. My setup: TIM FTTH (up to 10 Gbps), TIM Hub Ultra (firmware AGLHX_1.4.0), Xbox wired directly via Ethernet. Everything else on this connection works: streaming, browsing, other games. What I’ve tried: router reboots, innumerable changes to router handing of data with changes to QoS and UPnP, checking the NAT status, changes to Xbox preferences, and tracking my public IP. When I got an address in the 9x.x range, Destiny ran fine for about 45 minutes. With 7x.x addresses it didn’t. That’s a handful of data points, not proof, but it looks like path or peering, not my console. Then something odd. Around September 26, everything suddenly worked, for me and for other TIM players in my clan. Nobody changed anything on our side. For almost two weeks I played normally. After a full FTTH outage on October 10, the errors came back. Here is where it gets absurd. This problem has been publicly documented on these forums for months, with threads from June to this week. And yet TIM’s technical support is apparently groping in the dark. They told me my line “looks regular,” gave no explanation, and repeated the same standard guidelines, which are useless and outdated. Honestly, what I can test and try myself, with the data I’ve collected and a good AI to help me read it, goes far beyond what their support can do. That should not be the situation. Bungie’s answers, meanwhile, point me to generic network guides. I’ve read them. I’ve done them. So here’s what I’m asking, plainly: Is there a known issue between Bungie’s infrastructure and TIM or other Italian ISPs? Can Bungie publish the IP ranges and ports used by game sessions, so we can run real tests and bring evidence to our ISP? If I need to change router, tell me, and I’ll do it. If I need to change provider, tell me, and I’ll do it. If the answer is that I can’t play for now, well, tell me that too. I’d rather hear it than keep losing weeks. I’ve spent my time, my patience, and a lot of enthusiasm on this. Has anyone on TIM fixed it, or found a provider where it works? Please share ISP, router, and what changed. UPDATE (evening of Oct 13) I ran two more tests, and the results complicate my earlier theory. Console on a TIM 5G iPhone hotspot. Same Xbox, same account. Destiny 2 was playable, with higher latency (expected on mobile) and a few CURRANT errors, but no login problems and no constant disconnections. Back on my TIM FTTH, about 1.5 hours later. I played a full session. It was clearly better than in recent weeks, but not fixed. CURRANT still appeared when trying to load into the Tower and some destinations, while other activities, including fireteam content, ran without problems. This is only about 1.5 hours of play, so I can’t draw a rule from it. Crowded instances might be more affected, but that’s a guess. IP range. My public IP was again in the 7x.x range, the one I earlier associated with failures. So the IP-range correlation I suggested is much weaker than I thought, and I no longer think the address alone is the deciding factor. What this suggests: the console and the account are fine, and something on my fixed line or its path to your servers behaves differently from the mobile path. I can’t say whether it’s TIM’s routing, the physical line, or something else. Two other facts: I opened a fault report with TIM on Oct 11. They said they had taken charge and expected a solution by Oct 13, but nobody called me. I don’t know whether they changed anything on the line, so the improvement may or may not be related. I still get short connection drops (a couple of seconds) outside the game too, for example during remote work, while the router shows everything as normal. They could explain some errors, but I haven’t confirmed it yet. I’m going to run a continuous ping from a wired device to log them with timestamps. Can anyone on TIM FTTH say whether they see the same pattern: partly working now, with errors mostly in busy areas? And could Bungie say whether any routing or peering changes happened between TIM and your servers in the last few days?