This post is to help Bungie diagnosis and solve this issue, not to complain. My real frustrations will be very evident. This is a report on everything that has been attempted to eliminate this recurring issue. I will try to be as descriptive and succinct as possible. Thank you. Platform: PS5 All other PlayStation Network required games play fine. PS5 Network - Test Connection: Passed in all hardware testing scenarios listed below. Location: US, Pennsylvania Last played prior to errors: May 18, 2022 Started receiving errors: May 27, 2022 Error: weasel Playtime: Less then 1 hour before receiving the error, recurring. Errors have been consist every time played since May 27th. Where it has happened: - Orbit - Gambit - Strikes - Crucible - Story Missions - Tower - HELM - Enclave - Castellum - All Menus I’ve only played/visited those areas above since May 27th. Playing styles: - Solo - Cooperative - Matchmaking ISP: Comcast since 2013 Download: 1Gbps+ Upload: 50Mbps+ No Firewall All of the software procedures listed below were tested and did not resolve the issue, every avenue tested still failed with the weasel error. Deleted the entire game and reinstalled from the PS Store, PS5 version only. I do not use an external drive. Cleared console cache via Bungie's criteria. Restored Licenses on PS5. VPN and DNS tested with: - Express VPN (paid) VPN tested with: - SaferVPN (paid) DNSs tested with: - Google (free) - CloudFlare (free) - Strong DNS (paid) All of the hardware procedures listed below were tested and did not resolve the issue, every avenue tested still failed with the weasel error. - Rebooted Netgear router - Hardwired from Netgear router - Hardwired from Netgear modem - Secured WiFi via 2.4GHz and 5GHz - Another Router, TP-Link, hardwired and secured WiFi - Tethered to my iPhone T-Mobile hotspot using cellular data - Neighbor’s secure WiFi, ASUS router - xfinity unsecured WiFi Advanced Troubleshooting: UPnP & Port Forwarding findings - Port Forwarding of Bungie’s required ports - Port Triggering - UPnP enabled & disabled All above variations still resulted in the weasel error Hopefully, in being helpful, this information will reach the eyes of Bungie and it will help in finally rectifying this game-crippling recurring error. This error has made my favorite game, literally, unplayable. If anyone has any other suggestions, please share. Thank you.