I'm still having massive bee and associated error problems. Xbox One Open Nat Ports forwarded Static IP Tried both DMZ and No DMZ Residential connection DSL Tried my normal DNS and Google DNS servers B rating on Pingtest This error happens all the time in PVP. Almost always towards the end of matches. There will be no lag beforehand and I'll be doing things like damage and point capturing in real time. No lag in fireteam chats or player character rubberbanding. PVE is somewhat less predicatable but the error still occurs. Like with PVP, there is no warning the error is coming. No rubberbanding, damage dealy, or lag in chat. Sometimes, in the tower, I'll see lag taking stuff apart or trading engrams, but very rarely. The drops will happen whether I'm completely alone somewhere in Mars or surrounded by lots of other people. Tech support seems to indicate a relationship with packet loss. I've caused intentional bandwidth load trying to reproduce or force the errors. I've run big downloads or speed tests on other systems on the network while playing Destiny. These tests rarely if ever force the error. Odd considering this should cause less than ideal network conditions and packet loss. Yet, I'll eat these errors in the middle of the night with nothing on the network. None of my other Xbox One games like Titanfall or BF or CoD drop like this. None of my many other systems have this problem. It's just this game. My DSL connection is basic -- I'm an adult in a rural place and there are no other options. However, this connection works with all my other things and Destiny is not using up all my bandwidth according to my monitors. I do take some solace in the fact that people with way more robust connections than me are having the exact same problem though. I've posted some in other topics, and I know you guys are working on it. But I felt it was time to make my own topic and hopefully get some insight.