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+ 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.