Hello, The error code Beaver is still an issue with Destiny 1. Loading into match-made SIVA Crisis Heroic Strikes, Patrol Zones (encountering random players during both strikes that travel through patrol zones, and during traditional Patrol free roam), Archon's Forge (with up to 5 players present at a single time), The Reef Social Space, The Iron Temple Social Space, and Crucible "Doubles" 2v2 mode all work perfectly fine. Despite my personal success with matchmaking and maintaining a consistent and solid internet connection, with other players present, I cannot consistently load to the Tower social space. Ever since, around the time that DIM went down for a notable chunk of time for Legacy Destiny, there have been quite a few other reported problems of players encountering the error code Beaver. At some point the tower also had a brief period of holiday decorum (Dawning) outside of a scheduled event. Primarily this error code is occuring when attempting to load into the Tower, which is where most friends I have are reporting the problem. There are a few posts ranging from the past few months all the way to a few years back in regards to error code Beaver. The only fix I have had successfully work is to move to a mobile hot spot, and force myself into a STRICT NAT TYPE. By doing so, the game seems to force myself to load into my own instance of the tower, and that is the only way I have consistently loaded to the tower and maintained that connection. If anyone else is running into this problem please help raise this thread up, because it doesn't seem to be exclusively a player sided issue.