I already reported this error codes in the past and now at least I saw under other people posts that Bungie's team is investigating, instead of just putting the copy/pasted answer "the problem it's on your end" with a link to the "fix your internet" page. I post today cause, even if my internet and equipment are perfectly fine according to the ISP, this problem reached a point that the error codes are so often that the game is literally unplayable in any of his aspects (pve/pvp), but since people are looking into it, there is still hope... so, better leave the little info I have on it. First times I saw this mass of error codes appear was during the Marathon beta test week-end. Mind this, I'm not here to point fingers to Marathon, it's just to put a timeline to the problem. For the whole duration of the 3 days of the beta testing, no matter at what time I tried or for how many attempt, the aswer was always the same: Centipede error and back to main screen. After that, I would encounter the Centipede error code on log in only at times and the error code Coconut started to make it's sporadic appearance, but all was back to mostly normal. Then.. Marathon launched and same thing happened, for 3 days I couldn't even log into the game (Centipede error over and over), but after 3 days it stabilized and I could at least log back in and play... that's when error code Coconut started appearing with more frequency, at first it was 1 error code every 5/6 games and then it started scaling up to 1 error every 2 games. I put major hopes in your "last fix" when you launched the Monument of Triumph, but instead stuff got even worse to the point of having to spend nearly every time 5+ minutes to log into the game cause of the Centipede error and after that... 2/3 error codes every 1 or 2 games played. From what I saw, the "Coconut" error code happens "after" the matchmaking, while you are being connected to your lobby. This literally caused me to be unable to play Trials or Comp, cause every time the error code hits it's counted as a "game left" with the insult to injury of a broken card and warning... then a suspension. But sadly it doesn't stop there; because of you, your fireteam suffers the same fate of broken cards, points lost and suspensions for no reason and.... why people would at that point play with you? Some friends (the few still brave enough) tried to play Iron Banner with me... after 4 Coconuts in a row we spent 5 minutes chilling off our unjust suspension and I went back playing solo. Now after the crazy increase of error codes I can't even play any PvE activity that requires a team but doesn't have in game matchmaking, cause people on LFG don't have the material patiece, will or duty to re-launch the activity for you 5 times till the Coconut error gives up and your fireteam gets successfully landed. The only option is ask your "friends" but those willing to battle an error code for you are less and less. Joining them after they landed is not a fix cause the game instead of "coconut" simply answers "rabbit" for 4/5 times till at the last try you can finally join. Well, I think above is a full accurate recounting of my D2 experience in the past months; hope that it helps; for now, I'm off to sail my ship in another game for a couple of weeks. Hopefully when I decide to come back maybe there is gonna be a fix for this and I can finally play with other people and maybe try get some trials/comp loot that has been totally denied to me even if I paid the content.