I get Bee constantly and it's unlikely related to Bandwidth. Go read up on people having this same error on extremely robust connections. Bandwidth does not explain why I can load my connection and not force the error. I can run giant downloads or speed tests consuming almost 100 percent of my connection, and I can not force the Bee error. Perhaps bandwidth loss can cause it, but there also seems something more malicious going on with it in some cases. Bee always manifests about 80 percent of the way into a crucible match. Why is there no lag or bandwith problems for the first chunk of the fight? How can it strike if you're sitting alone somewhere with nothing around you at all while just 5 minutes ago you sat complete fine in the Tower? I have performed all types of portforwading. Open all the way around. Disable all router firewalls. Tried static IPs, DMZ, disable UPNP, and all other suggested solutions. The problem still remains. My internal Xbox bandwidth monitor always indicates plenty of available bandwidth while the crash happens -- yes I've loaded the game and then stared at the monitor to see its behavior while the crash happens. Not a sing other game on any of my other systems drops connections. None of my other games on my Destiny system drop connection. So what's the deal?

http://www.bungie.net/en/Help/Article/11791 Who is your isp? What other games do you play? What is your download and upload speed?

I have Frontier DSL. Rural gaming bro with just basic DSL. I'm in my thirities, and I've played a ton of online games on this same connection. On my Xbox 1 alone, I have Titanfall, CoD Ghosts, and Battlefield. These games never drop the connection. I have played several MMOs on this connection too. I have several other systems with online functionality that also work fine. The only game I ever had problems with was Armored Core IV a couple years ago. I can't upgrade becuase there is no other provider available. Regardless, my other games run fine with limited ping problems. The xbox one bandwidth monitor during peak loads of Destiny seems to run betweek 50 and 80 kb/s. I have plenty of available bandwidth beyond that. Regardless, there are plenty of people posting around here with way more beefy connections reporting very similar errors. So I'm not convinced all Bee errors are related to bandwidth or packet loss. And, ultimately , if it is bandwidth and packet loss, I would rather eat some lag than just a straight up boot. Like just now. I was doing the moon strike. No lag or problmes the entire fight. The exact moment the boss dies I get the bee. If lag caused that, how about buffering it instead of just instant booting? I was moving around in real time and damaging stuff in real time even as the boot occured. There were no "contacting destiny server" messages. Just a kick. That's pretty nuts.