@Project Atom - first of all, there's no need for you to be so aggressive without properly discussing this issue with me. You're out of line for making such statements. Second, I understand the point that Mister Exotic made last night regarding Bungie's history to not act on issues like these. This is my first time posting on the forums yet I understand the uphill battle this could be to bring the issue to light. To be clear, there were no apparent network issues nor were we disconnected from Destiny 2. We were not taken back to the start screen before character selection, ergo, nobody in our fireteam was disconnected. We were simply given the error and then returned to orbit, still together as a fireteam. Therefore I believe this issue could be investigated further on behalf of Bungie as to why they discounted our flawless card with a loss when they failed to initialize our next and final match. They could have simply returned us to orbit without marking us for a loss, if anything. If they know they're having stability issues with their servers (this has been a known fact for years, since Destiny 1, due to their complex server setup), then automatically defaulting to a loss for any immediate disconnect is poor policy and design. The issue we experienced was beyond our control and was a result of Bungie's failure to initialize the match. This is how you have constructive debates about topics. Please, in the future, avoid undeserved personal attacks of character without properly discussing said topics. Thank you Bungie for skimming the forums and looking into this further.

hope they can help you out dude that blows. :(

Unfortunately, Bungie treats all disconnects as a loss on your card. I also got disconnected from a Competitive Match with error code weasel. Before weasel, I got guitared out of a raid.