If the cause of the BEE error code listed on Bungie's help site is accurate, then it is out of Bungie's hands. Sort of. "BEE/FLY/LION errors can be caused by general disconnections between you and the various routes your traffic takes across the internet to get to Bungie. This includes packet loss or disconnections between your home network and Bungie (such as ISP saturation or general Internet congestion). It can even be caused by certain WiFi setups, faulty in-home wiring, or other issues that require on-site support or expert investigation." After receiving this error numerous times one evening for the first time ever, I starting running MTR (http://en.wikipedia.org/wiki/MTR_(software) to various destinations. University sites usually work best as they are more permissive and almost always have very high bandwidth. What I found was that some tier 1 providers (backhaul, not ISP) have congestion. NTT and GlobalCrossing being the worst. There is also nothing your ISP can do unless your ISP is also the Tier 1 (like Verizon, Sprint, ATT). What I found that Bungie can do something about is not use UDP. Where large TCP packets get dropped at 10%-50%, UDP packets going the same route at the same time get dropped 80%-100%. They do this because network people consider TCP more important than UDP. The purpose of UDP was when you didn't need guaranteed delivery and didn't care. Also, most movie streams are UDP and the device decoding the movie has the ability to buffer the stream for a time so its no big deal if data fails to go through for a minute or so. Tier 1 providers could give the gaming ports using UDP a higher priority, but they won't for several reasons. Primarily if they give any UDP port any kind of priority, then P2P sharing and others will simply use that port to get around their tiering arrangements. Yes they have them. Amazon pays Level3 a premium to make sure their outbound traffic does not get held up by some lowly individual's gaming traffic so my Xbox Destiny or Halo UDP packets sit in the L3 gateway waiting for the Amazon traffic to clear so the Amazon customers get their web pages without delay. The common wisdom is that UDP does not have the overhead of arrangement and delivery that TCP does so your data gets there faster and in a lot of cases this is true. But in the age of traffic modeling, competing cloud and streaming services, TCP wins the race and using mtr proves it. So if you live in the Seattle area and your upload traffic is heading south, then you are getting slammed by the Tier 1 providers giving preference to the traffic from Amazon, Expedia, Microsoft, Valve and others. Unless you have a service like FiOS which takes you to Atlanta before you get out on the Internet.