I have tried everything. Hard reset my router and xbone 10 times a piece TODAY. Manually forwarded all appropriate ports, tried dmz enabling. Set static ip address on the console. I have done everything I can to get this game working, and it still won't let me land in the f\+/=ing cosmodrome long enough to even start a patrol before I get kicked with a beetle/sheep/anteater/baboon error. I've had more errors pop up in the past HOUR than the entire previous YEAR. My ISP hasn't changed, my hardware hasn't either. The only change is, you guessed it, TTK. Bungie, you are not fixing this issue. You are giving your devoted players BS "answers" by saying it MUST be our fault. Excuse me but did a quarter of your players suddenly get crappy internet RIGHT when TTK dropped? Cut the crap and fix this damn issue. Please Guardians, I'm begging you, bump this thread so Bungie will stop bullshitting and just fix their servers already. Update 9/25/15 6:09 pm I have called my isp (unhelpful, none of them know anything) and they are getting good signals from me according to them. Spoken with xbox live support, they had me reset my Mac, forward all ports, and uninstall/reinstall the entire game and dlc. No avail. Attempted to contact Activision support, they directed me to this forum. Nat lists as open or at times moderate, which is not crazy cuz it's worked on moderate pre-ttk. Interestingly, when it lets me join a party and fireteam and I'm not the host, I get the "contacting destiny servers" message frequently but was not kicked to orbit after roughly 30 minutes of strikes. What does that mean? Seeing as my isp hasn't changed a thing, I'm thinking Bungie got super picky about people having perfect internet when TTK came out and increased the threshold of acceptability for latency and packet loss. For those of you who would say "see it IS your isp's fault", let me remind you my isp worked fine for this game before this last dlc. The only difference between now and then is the dlc itself. Edit 2: [b]FOR ANYONE WHO READS THIS. Bungie did reply to this thread, and offered no solution or admittance of guilt on their part. [/b]Don't let that little blue tag next to the title fool you into thinking it means they've fixed it or done their due diligence.