Last night I logged on and went straight to the Tower, as is customary. Went to grab bounties for the Iron Banner and was immediately met with "Attention : Contacting Destiny Servers" which resulted in another Weasel code and returned me back to the Title Screen. I reloaded my character and managed to get into an Iron Banner match and disconnected halfway through with two notifications, both of which were Baboon codes. The following match met its fate with a Fly code. After that I joined some friends to complete daily PVE bounties with the same result. However; once when I was in lobby with them something interesting happened. One of them said that it notified them that coms were disabled due to Nat issues right before I got a Weasel error. This is particularly interesting because, as mentioned above, have an open Nat with a static Ip address. My network is showing that it is "Behind a Cone Nat". My Xbox one is set as the primary Ip within the DMZ router settings, and all of my connections are solid after checking them and the settings for the fifth time. I even went as far as to drop the firewall to its lowest possible security settings which made no difference. So I quickly reverted that setting back to standard. Finally I was fed up, unplugged the router and Xbone and let them set for about an hour (which I have also done numerous times before). After firing everything back up, to my surprise, everything worked as normal. WTF???? I didn't do anything different from all of the other times I have gone through this troubleshooting process. Logged on this morning before work to check Xur's inventory, and even ran some Eris bounties with absolutely no inclination of an issue. I will update if anything changes. Lengthy write up I know. TL;DR tried basic troubleshooting methods, finally worked for a few hours which may or may not help in your case, hopefully it will. Best of luck.