Hi Bungie Support,I have been experiencing persistent CURRANT error codes specifically during matchmaking for the past 3 months. The game disconnects me before or during loading into matched activities.Important Timeframe Note: This issue started occurring consistently right after the Marathon Server Slam open playtest back in late February. It seems that modifications made to the global network infrastructure or matchmaking routing around that event triggered this conflict with my ISP.I have already gone through the entire Advanced Network Troubleshooting Guide and applied every local fix possible:Platform: Xbox Series X/S (Wired via Ethernet)ISP / Country: TIM (Telecom Italia) / ItalyRouter Configs Tried: Assigned Static IP to Xbox, enabled DMZ for the console, verified UPnP is active, and manually forwarded all required Destiny 2 ports.ISP Features Disabled: "TIM Safe Web" (ISP-level firewall) has been completely deactivated.Network Status: NAT is strictly OPEN, and I have no packet loss or latency issues in any other multiplayer game.Since this has been happening for 3 months and all local hardware and firewall blocks have been ruled out, this points heavily to an upstream routing or peering issue between TIM Italy and Bungie's matchmaking servers that correlates with the backend changes deployed for Marathon.Could you please look into this or pass this information to the networking team?Thank you.