Up until four weeks ago I was able to play Destiny fine with my set up. Then something changed, either within my ISP or with how Xbox Live/Destiny establish connections. I started to receive endless cattle/pede/pillar errors, and then very occasionally I'd be able to make it to orbit, and then I'd get rabbit errors as I tried to start a mission (and then, very occasionally I'd be able to join a mission only to be booted with hare - this was especially likely if I were doing something silly on my sparrow at a zone transition, I think continuing the physics calculation was taxing). Play was impossible and I was very sad. This weekend I ran the multiplayer network diagnostic from my xbox one (I should have done this a long time ago). It told me that my console couldn't establish a valid toredo tunnel address, which stirred some memory and provided me with the clue as to the problem. I had been running a double NAT set up - my modem would NAT and then my Wireless Router would NAT again. Everything was connected to the wireless router whether wired or wireless - the network space between the router and modem was entirely unused other than the modem acting as the default gateway for the router. I switched my modem to bridge mode to remove the first NAT and my connection has been super solid and stable ever since - other than when everyone else has been having issues, of course. [b]TL;DR - If you have a double NAT/double firewall set up in your home network consider - putting the modem in bridge mode, disabling the internal firewall and NAT or connecting the modem to a LAN port rather than WAN port on your router/gateway. Obviously, make sure you know what you're doing so you don't just take out your home network due to misconfiguration. Also, use the multiplayer network diagnostic on xbone if you have a bone. [/b]