[u][b]I have a slightly longer thread at the link posted above with the details of my issue so please read that thread as well for more information.[/b][/u] I have been MOSTLY Bee/Fly free since Saturday and can honestly say, without a shadow of a doubt, it was [u][b]NOT[/b][/u] Bungie's fault. Comcast ended up having to replace the node (where the main fiber lines get converted to Coax) for the entire neighborhood to the tune of ~$250,000 in equipment and labor. Once that was done the only time I still get a Bee/Fly is when I am in a fireteam with a fireteam leader who has a "poor" connection to Destiny's servers and they get dc'd. While I do now believe that Bee/Fly is NOT a Bungie issue for the most part, I also believe there are some additional things they can do to help their customers, the entire Destiny gaming community, to have a better experience. 1. During "matchmaking" when guardians are being evaluated, the system should automatically switch the fireteam/strike team leader to the member with the best connection to their servers. I'm not aware of any benefit of being the fireteam leader, but if there is, the likelihood of not getting booted certainly outweighs whatever benefit that is. 2. Better troubleshooting instructions for Bee/Fly and other general networking errors. Frankly, the NAT instructions and port forwarding instructions are great, but for the people who are still getting constant issues, there are better steps to take, that can quickly determine whether there is anything that they can do as an end user, whether they need to get their ISP involved, or whether there is truly nothing they can do. 2a. Troubleshooting for CABLE INTERNET users should include the following FIRST steps before changing any settings in your modem or router: 2aa. Check the actual signal being received by your cable modem. If it is not within spec the customer will need to contact their ISP to have line testing done, possible new lines run, or in my case, maintenance work to their ISP's actual transfer hardware. (http://www.speedguide.net/faq/what-cable-modem-signal-levels-are-considered-good-78) While most ISP's consider -15 to +15 to be in the acceptable range, you really want to be between -7 to +7. My signal was +12 to +15 and after changing the node I am at +7 on all 16 channels.[u][b]To be clear, I am talking about the signal strength coming into your MODEM from your coaxial cable (likely your wall connection), not your WiFi signal from your router.[/b] [/u] 2ab. Use pingtest.net as a baseline to check for packet loss between you and MULTIPLE servers around the country. Even if you are getting a 0% packet loss you should still use your PC's operating system to check for packet loss as well. I am not sure what the application is called in windows, but in MacOS it is called network utilities. Send your ping test to a larger server like google.com or yahoo.com. Make sure you sent AT LEAST 300 ping samples in order to better assess packet loss. If you have a packet loss issue contact your ISP to discuss line/splitter maintenance options as there is likely nothing you can do to your personal modem/router to correct the issue. 2ac. If you have an older cable modem, consider upgrading your modem to a newer unit with a greater number of banded channels. While this won't increase your bandwith (unless you are on VERY fast internet and your current modem is obsolete) it can assist with channeling data through your system, especially if you use other internet connected devices on the same network. 2ad. Begin with the network troubleshooting steps provided by Bungie (http://www.bungie.net/en/Help/Article/11931). Best of luck to everyone!