JavaScript is required to use Bungie.net

Help

Help us help you.
8/28/2016 4:08:07 PM
2

Weasel and Baboon error codes everyday since January 2016

I explained this in my video, if you just want to see my connection type skip to 8:07 in the video, otherwise, enjoy my ramblings. I've been playing Destiny since the first month and I didn't have any issues with connection until January of 2016. For whatever reason, something changed in January that is making it so that way I am getting consistently booted from the game every single day. I get around 8-25 error codes per day (most of them are weasels which send you back to the title screen) and there's no explanation. If you don't want to watch the video I made on it, here are my connection stats: Nat Type: 2 Connection Speed (Download): 67.9 mbps Connection Speed (Upload): 4.9 mbps These speeds are all on a wired connection, ethernet cable to be exact. I do NOT use wifi! Most of these speed tests are within this ballpark. Some times the download speed may be 59.8 and the upload could be 6.7, etc, the download is within the range of 40-80, and the upload is within the range of 4-8. It never deviates lower or higher than those numbers; just as a note, these numbers are MORE THAN ENOUGH to run any online game that has a patch server. If you are in doubt that my connection is good enough, then go look on the forums for the necessary connection speed to play Destiny. I've emailed Bungie about it on numerous occasions and on every occasion they have pretended that I am the problem. They keep insisting on referring me over to the FAQ to fix my connection when my connection is simply not the problem, so I don't expect much more than that for this thread but if we get enough people telling Bungie their servers are the problem they will have to listen. Thanks for reading!
English
#Help #Errorcodes

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • Baboon is a networking error code caused by packet loss. You can test for packet loss/jitter using pingtest.net or use command prompt from a pc. Common causes of packet loss are: using wifi, using cable splitters, loose connections/faulty cable wiring, exterior line filters, poor modem signal strength. Many causes can only be fixed by your ISP.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    5 Replies
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon