So I have been faithfully wrestling with Destiny in an attempt to play the game. I am having occasional success at having the game run perfectly followed by spasms of "centipede" errors even with a NAT as Open (NAT1), all ports forwarded for XBL and Destiny's LARGE ranges and now I am rewarded with intermittent connection and LOTS of "Canary" errors and occasionally a "Centipede" error. Now last night it ran very well after fighting with it for 6.5 hours. Today, during the morning, it was back to centipede hell and then after more gyrations and working more with my ISP I got the NAT to 1 instead of 3 and the XBO and all related ports placed in the DMZ and it finally worked well again this afternoon and evening. At 6 PM MST I quit and shutdown the XBO to make dinner and eat with my family. I am now back to intermittent"canary" errors and the odd "centipede" and moments of connectivity. The only other person on our network is my wife who is writing patient notes on our cloud based service which uses almost NO bandwidth. According to speedtest.net my current available speeds are 11.65 Mbps down / 2.86 Mbps up with my wife working - should not be any sort of a connection issue on my end. XBO shows full connection for multiplayer yet Destiny was saying that I was not connected to XBL while I clearly was. So I reboot the XBO and unplug the power brick. And.... "canary" and occasional "centipede" errors among moments of actually being connected and messing with my inventory only to be slammed by that damn annoying yellow "canary" error and the odd centipede. This is incredibly tiresome. I work for a living and run several businesses, have kids and am in school AGAIN for another degree so my play time is VERY limited ... and now I am having these constant hassles to play a simple game that should run as flawlessly as it did last night ALL THE TIME and not just when it feels like it. I am at a loss as to what to do next. Perhaps I will contact MicroSoft and see if they have any silver bullets...