Right after "server maintenance" on Tuesday, January 16, my screen is constantly spammed with the "Contacting Destiny 2 Servers" error code until finally the game boots me from the world and hits me with error code "bee", "weasel", "buffalo" or any other random name that has no SPECIFIC info on how to fix in the forums upon lookup. I understand the servers will possibly have increased traffic after they've been down for extended periods of time, in addition to the extra traffic from the faction rallies on this reset, but I don't think that's any excuse for the game being unplayable (due to network errors). The PC/Blizzard.net Destiny 2 community is so much smaller than that of it's console counterparts, AND even much smaller than it was on it's initial release. How is it possible the servers were prepared for those larger populations in the beginning of the games life, yet now that the servers support nearly a tenth of that population their unplayable? Even if this issue after the "January 16th-faction-rally-reset" dissipates because the problem is merely the servers being hit hard all at once, it won't be my only network related gripe with the game. [b]This specific issue was just the final straw that broke the camels back for me, and inspired me to write this post.[/b] [b]--------------------------------------------------Personal Experience------------------------------------------------[/b] Lately (before this incident, of course) my fireteam and I have been plagued with, seemingly, raid-specific network errors. I say "raid-specific" because I can grind in the EDZ for 6 hours straight with maybe one or two "buffalo" or "weasel" error codes, but when I try to play the Leviathan raid I see many more error codes, freezing on loading screens, "contacting Destiny 2 Servers" messages, and a new, more frustrating error "Anteater" error code. This specific "Anteater" error code is particularly annoying because the game will give me a black screen and the error code pop up, but I will still be able to hear the action of the raid going on in the background, as if my character was still there. After a few moments the black screen and error code will go away and my character will be right where he was in the raid before the black screen came up, only I'll be dead and deprived of all heavy ammo. In all cases of these terrible raid specific errors, the time it's taken to complete the raid has been substantially increased, and I'm sure you can imagine why! Many of the raid mechanics and encounters hinge on one player thoroughly completing their job (especially in prestige). When a specific player or multiple players experience network issues this often throughout the raid, hindering them from completing their job, the entire team and raid experience suffers! Once again I completely understand network errors happen in every game that supports online functions, however I've experienced way too many to not be extremely upset/irritated to the point of calling parts of this game unplayable. [b]--------------------------------------------------Final Notes------------------------------------------------[/b] I've not had any other network errors such as this in any other game I've played on PC before. During each instance of these errors I've checked to make sure that my network was fine, both through SPEEDTEST (dot) net and through other family members computers [b](I have gigabit speeds with 500-1000 mbps down and 30-100 up)[/b]. I've restarted my router more times than I ever have in the past with any game and also have the latest NVIDIA GeForce drivers installed on my computer. I've gone as far as to restart my computer mid raid in a last ditch effort to try and remedy issues, yet, unsurprisingly, that yielded no difference in network error amount. As I previously stated no other games I play have these issues (BDO, ESO, CSGO, Day Z, Arma 3, Squad, COD WWII, etc...) so I can say with 99% certainty that the issue is not client side. [b]All I'm looking for with this post is recognition from others that they have experienced similar problems. I'm open to methods and suggestions of fixing these issues. I wanted to make one of my worst issues with the game known because I enjoy playing the game when it doesn't have these issues. Maybe I'll get some sort of reassurance that these issues are being fixed too idk. [/b]