JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Saint Ryken XIV: 12/2/2019 2:13:17 PM
4

[SEA] Compiled Information on those 5 minute disconnects

So I'm sure everyone who is browsing the networking tab on this website is probably wondering the same thing: what is going on with the servers? And whether or not it's actually my ISP screwing up. After looking around everywhere and gathering information, I've compiled some knowledge that might help us point to a clear culprit. So here's what I've got. After getting into Destiny 2, after about 5minutes or so, I'd get disconnected - the baboon error shows up. After several attemps of "Contacting Destiny 2 servers", I'd get booted out to the login screen with the weasel error. So far, this has been a consistent occurrence for me and my friends. What I've done to test if it works: Used a VPN (specifically Urban VPN): Disconnected (Baboon) Used Wifi from ISP 1: Disconnected (Baboon) Wired connection from ISP 2: Disconnected (Centipede) Used mobile hot spot: Connected (everything seemed just fine) From this, I can assume that our ISPs aren't the issue (2 different ISP yielding the same error can't be a coincidence). Having a wired or wifi connection also makes no difference, as my friend who only has a wired connection also got kicked out. Using a VPN yield mixed results. Sometimes, I'd be fine (in the mornings), but at night, I'd get kicked out just the same (maybe it's due to quality of VPN) The best results I had was using my mobile data hot spot. Consistently, I was able to log in without issue and experice everything just fine. Conclusion: It's likely a problem with our ISP's connection to Bungie that causing an error, rather than our connection to our ISP. While using a mobile hot stop allows me to play the game, I will mention that before the blackout back in late November, everything was just fine playing on Wifi. It seems that the recent fix had caused some unintended effects to radiate out to all of us. Hopefully this data has been helpful. If you have any experiences you'd like to add, please feel free to comment. The more data we have, the more solid a case we can build.
English
#Help #Networking

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
  • Edited by RAIST5150: 12/2/2019 4:20:33 PM
    It is likely a problem occuring at the peering level... the intermediate ISP(s) used between your ISP's network segments and Bungie's. Depending on exactly where it is breaking down, your ISP MAY be able to help smooth things out. They may need to analyze your packets as you are trying to play though. You can try forwarding them Bungie's ASN as well so they can do a dig on their BGP/IGP routing data: AS394073 The problem is likely tied to one company again... we see them crop up frequently with various services. The bulk of Bungie's outbound data is carried by Level3/Century Link. Level3 has always had recurring issues in certain regions (namely Atlanta for my ISP here in the Carolinas), and Century Link tends to have issues along the west coast, more regularly in California. Basically, got two strikes against us atm. Bungie used to send more traffic to Zayo back during D1's day. .. may be time for them to go back to that arrangement.

    Posting in language:

     

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

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