As always, bee everywhere. Xbox One, DMZ, Open NAT, all suggested ports forwarded, on the least crowded channel, not on a campus, wireless internet, 0% packet loss. But it's my end. Yeah. Anyways, I'm doing testing, and will update this after more testing. Here are some tests and results. TEST: Wired vs. wireless RESULTS: Wired or wireless, still be. TEST: See how many games out of ten that I can get through in Iron Banner. RESULTS: One. And I lost. This is great for IB rep. TEST: PvP areas affected. RESULTS: Iron Banner, Control, Clash. TEST: PvE areas affected. RESULTS: Occasionally the Tower. VoG is affected heavily. TEST: Bandwidth? RESULTS: Disconnected everything but xbox from wifi. Bee. TEST: Account specific? RESULTS: Brother's account. Bee. TEST: ISP/router/modem specific? RESULTS: Neighbor with same ISP, router, and modem. No bee. TEST: Any signals it gives before occurring? RESULTS: None common enough to make me believe so. CURRENT FINDINGS: Bee is not cause by packet loss. Bee is not preceded by lag. Bee occurs wherever there is a team of 6 (includes Control, IB, Clash, VoG, and occasionally tower. team does NOT mean fire team). Bee is not specific to any ONE thing, be it ISP, router, or modem. Bee is not affected by wired vs wireless. Bee is not affected by bandwidth gain/loss. BUNGIE: Stop telling us that it is our internet. My findings prove that it is not. Don't tell me there is a 53% reduction in bee errors when all I see in these "forums" are more and more people coming with bee, and none saying "thanks for fixing bee, bungie". I love Destiny, I really do. But when you bring out the Iron Banner with only a 6v6 mode that those of us with bee CAN NOT PLAY, it is very frustrating to us. We know you're trying to fix the issue. I know centipede/zebra takes priority. But, please don't mock us with the Iron Banner. And please stop repeating the same old " it's you, not us; open your ports". We believe in you guys. Please help us. EVERYONE ELSE: Any suggestions for more tests I can do?