Hi, thanks for the detailed report. Since this started after the update and you’re seeing Canary, Centipede, and Cabbage while also being unable to join fireteams, matchmake, or see other players in public spaces, this does not look like a simple Open NAT issue. Those error codes point more toward a connection-path problem between the game and Destiny services than a basic local setup problem. Centipede means the game connected to Destiny servers and then lost that connection, Cabbage is tied to problems reaching Bungie’s bubble hosts, and Canary maps internally to loss of ethernet link. The fact that you’re based in Ireland is also relevant. Bungie’s Cabbage guidance notes that if this type of issue becomes widespread, it can point to an ISP problem in a specific region or an issue with one of Bungie’s data center ISPs, not just something wrong with one player’s console or home network. If you can, it would help to add your ISP name, whether you’re on wired or Wi‑Fi, and whether testing with a mobile hotspot changes anything. That should make it easier to tell whether this is a regional/ISP routing issue introduced after the update rather than a local configuration problem.