Following Bungie’s Advanced Troubleshooting guide, I set up manual port forwarding on my router for every recommended Xbox port: TCP 3074, and UDP 88, 500, 1200, 3074, 3544, 4500, each pointing to my Xbox’s static LAN IP. NAT type confirms as Open, so the forwarding itself is working correctly. I’ve also tried the UPnP route instead, and separately tried connecting through a VPN on my TIM connection. None of these approaches resolved anything Right now it takes me at least five attempts just to log into a mission, the Tower, or basically any activity, because of constant Currant and Centipede errors. Sometimes instead of that, I get flat out kicked with a Weasel error mid-activity. I have proof that this is not an isolated or hardware-specific issue: many other players on TIM (Italy) run into this same problem, regardless of router setup, extenders, or troubleshooting steps taken. This strongly indicates the issue sits on TIM’s network itself, not with any of the standard fixes Bungie recommends. This problem has been going on for a long time now without being properly addressed. Flagging this so it’s documented for other TIM users hitting the same wall after doing everything by the book, and to push toward this being recognized and escalated as a known ISP-level issue rather than something individual players can fix on their own.