I remember that horrible wombo combo

Ty much appreciated and im ps4 forgot to mention srry....

Baboon is related to packet loss, and Weasel tends to accompany it when that's happening. Don't use other online games as a comparison. Unlike most games, Destiny requires a [b]persistent premium connection[/b] [i](low latency & zero packet loss)[/i] to all players on the map as well as their data services; other games do not and will allow a certain amount of deviation. Destiny also functions via a P2P networking system. If you are on WiFi, I suggest the first thing you do is find a way to hard wire the console to your router and disable the console's WiFi service. Since your profile is not view-able, I can only offer some generic suggestions right now. Do all testing on your console (not a PC), since this is where we need to determine to outcome. Your game sees what the console sees, not what your PC sees; and not all devices will communicate equally depending on how the router is setup and performing. If you have XB1, you can run a detailed network report and get UL/DL, Latency, Packet Loss and NAT settings from it. I believe PS4 can get similar information, but it may not all be from one tool. Make sure your router is using UPnP Make sure your router is assigning a static/dedicated IP to your console. If you have more than one console of the same type, make sure they have unique names on your network ([i]done on the console itself[/i]) If your router has QoS abilities, I suggest turning it on and assigning the highest priority to your console, and medium or lower priorities to all other devices. If you change any configurations on the console or router, I suggest unplugging both for about 5 minutes so they erase all cached info regarding connections and game-play. The router doesn't take as long, but 5-10 min is recommended for consoles since they tend to have a slow discharge capacitor designed to help retain cached settings. After time has elapsed, plug in the router first and wait for it to fully boot up and operational. Depending on the type of router you have, this could take anywhere from 1-5 minutes. [[i]mine takes almost 5 minutes by the time it runs self diagnostics and tests all possible settings[/i]] After the router is fully booted, plug the console back in and try again - running tests first if you want. You can also request the ISP to run continuous testing on your line while you are playing Destiny to see if they notice any changes in connectivity.

What system are you on? Not sure about PS but on Xbox you can run a diagnostic test on your network. Run it and list the results, specifically latency and packet loss numbers are important. UP/down speeds only need to be just about 1 each way. Run the test several times to make sure you get consistent numbers. If you see any packet loss at all there is your problem. Are you wired or wired or wireless? While other games may be working ok and other services may be ok, Destiny require a very stable connection to run. Other thing are able to compensate for problems on the network but with Destiny it will cause errors and disconnects.. So if you have jitter, any packet loss or high latency you will have problems on Destiny.