I think I've determined the reason for all these error codes: Destiny's netcode is *very* unforgiving of host disconnections. I have been toying around with my networking all day, and have realized that my ISP is dropping all my packets for about 5 seconds every now and again. When this happens, all my network traffic outbound is shut down, but internal network connectivity is just fine. I understand the reason is not on Bungie's end for the disconnections, however the issue lies in the fact that I believe Destiny's netcode is dropping you if you cannot reach its servers within a couple of seconds (maybe 2-3). This is kinda a small window, as many games I play allow for time outs of up to 20 seconds. If my hypothesis is correct, Bungie just needs to allow the disconnection timer to be a bit longer to prevent a lot of the connection drops that I have been experiencing. The connection drops I've monitored can be seen as all my ICMP traffic to MS server (134.170.179.80) will drop for about 7 ICMP counts, then resume as normal. I have not been able to complete a strike mission because of all these drops, and I feel that the multiplayer netcode is being a lot more forgiving than the single-player netcode right now. Hopefully this helps some of you find out what's going on. I'm glad to see that Bungie updated the verbiage for their "Bee" error code. Suffice to say, the problem still exists, but at least now they are formally acknowledging the reason for the error. I sincerely hope that they are able to address the timeout drops and increase the length with which your console drops your connection due to an inability to connect to their servers. While I understand that it may be a technological impossibility to reduce the timer, I do hope that that is not the case and this can be resolved in a future update. -------------EDIT 9/14/2014------------- This one is a doozy and a bit unrelated to the content I posted before but it chronicles my ordeals in finding out how I determined it was an ISP issue, how I fixed it, and how I hope it will fix everything going forward (for me): So I noticed after just having an endless ICMP session with an IP I control outside of my network that my connection was dropping every 10 minutes on the dot. I would have a CentOS VM just constantly pinging that server and would check it whenever I noticed my entire internet connection dropping. The way that pinging tends to work is that it sends a packet out every second or so, which it how I calculated my packet drop time (5-6 seconds). Someone in this post (another forum) suggested to try a static IP, but they were thinking of a static IP for the console, not necessarily for my entire internet connection. I have the DHCP lease for my devices at a sufficient length that it should not be an issue for any one device to lose connection for any (noticeable) period of time. However, it got me thinking, what if I set a static IP as the IP that my ISP assigns to me. Typically, IPs are given to you via DHCP *unless* your ISP assigns you a static IP, or if you opt in for one. While digging through my router configuration gathering up my current IP and gateway (which was a .33 fortunately which TREMENDOUSLY helped in figuring out the netmask) I noticed something odd. My ISP's DHCP lease time was 20 minutes. That is short; incredible short. And also helpful to know. Due to the way that DHCP works, devices will send a packet to their DHCP server around the halfway mark (50%) of their lease time to determine the next Configuration to use. The halfway mark of 20 minutes is.... 10 minutes..... That's when I put 2 and 2 together and realized that maybe my ISP is having DHCP a issues when it comes to my particular network. So I set a static IP for my public IP (I would not recommend doing this unless you are allocated one by your ISP) and, lo and behold, no more drops every ten minutes. I called my ISP this morning (very small ISP and the owner is basically a network engineer that picked up the phone). He confirmed the DHCP issue and said it was due to network upgrades they are performing. He chided me a bit when I told him I set a static IP, and said he would set a DHCP reservation for my IP to see if that helps. I'm not 100% sure it will, as I believe my router still has to send out a DHCP request at the halfway mark to verify which IP/Configuration to use, but here's to hoping. Anyway, that's how I fixed my issue with my ISP. To anyone who wants to determine where they might be experiencing issues, you can try running a "tracert 134.170.179.80" within a command prompt, and looking to see if some packets are being dropped wholesale or partially at a particular router. If they are being dropped at a router outside of you ISPs network, find out what it is and contact your ISP about it. I'm sure with some digging I can find the IP that the XBOX One is connecting to for Destiny's Servers, but I would rather not post that if I found it.