http://www.bungie.net/en/Forum/Post/69265642/0/0 My problem is mentioned in the link above, as well as the workaround for "marionberry" which is a temporary fix and really not acceptable ! But better than nothing I guess. In short. Xbox 360 Home Network Tried all Methods you offer to Troubleshoot in #marrionberry Still Happens on Wired connection as well btw... I'v had this Issue since the beta (marrionberry) i have posted here back then as well link : http://www.bungie.net/en/Forum/Post/66833572/0/0/1 So as some one here already stated, We had those Errors back in beta (that is the purpose of the beta isn't it ? ;) (looks like some one didn't finish hes Homework / "Network" ;) Big F if i was to Grade it... ;) Bungie its time to step up and ACKNOWLEDGE That this is a problem with your Servers Not our connection/hardware or anything else you might come up with ! (didn't see here on the forums no one complaining about and error called "Chooks" ;) So to conclude Bungie ITS YOU ITS NOT US ! We cant #Helpyoutohelpus , Its a one sided Problem on your side ! (Ahhhm Servers/Net-code , W/E it is its Yours to FIX) So its time to announce on the Main/home Page of your site An Acknowledgment. (See How Rockstar Handled her self With the lunch of GTA V Online.) what are you doing to fix it ? and regular updates with progress ! We your loyal fans and customers are eager for Information any thing official from you will go a long way IMHO just my 2 Cents ;)