[quote]This has happened NUMEROUS times to me in the past, and just happened again - I was queuing into a comp match, when as soon as we started loading in, my team all got the same error code and were returned to orbit and our match was counted as a loss. We tried again, and guess what? THE SAME THING HAPPENED. And this time, not only did it count as a loss, but we all got SUSPENDED FROM COMP! Bungie, this was no doubt a result of your terrible servers, so why in the hell do we have to pay for your crappy servers? At bare MINIMUM, when a player and/or team gets booted out of a comp match or while loading in, don't count it as a loss against us. We didn't leave. You're awful servers kicked us. On top of that, don't freakin SUSPEND us for things that are out of our control! I am sick and tired of your god awful servers, and even more sick and tired of you guys not addressing it! Ignoring these problems don't fix them! Try this for me (anyone at Bungie who sees this): Try completing a total of 10 comp matches in a row, without you, someone on your team, or someone on the other team, getting disconnected. I think you'll find the results sad. Maybe then you'll realize what a problem it is. The server instability is making your game so unenjoyable. Before you start praising yourselves for what an awesome job you guys are doing for the stuff in the future, how about you fix the problems in the game that are occurring right now!? End result, I am so irritated that me and my team are the ones who have to pay for your servers being a hot pile of crap. Edit: The suspension lasted 30 mins, so after it lifted, we hopped back in, spanked a few teams, and everything looked normal. But wouldn't you know it, it HAPPENED AGAIN. All three of us got error code "elderberry" and got suspended from comp, now for 2 hours! WTF Bungie. I'm at a loss of words[/quote] “Exactly “ I know the feeling it had happened to me also.