{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/15/2019 9:36:48 PM
2
Repeated 'Weasel' Disconnects due to bad Routing
Hi,
for the last weeks I am getting disconnected from the game repeatedly (approx. every 60 Min.) due to what I assume is bad routing to the game-servers. My ISP is Vodafone Germany and I already reported the problem to them. Other users also confirmed the same problem in a thread I created on the ISP's forums. Vodafone support staff expectedly absolve themselves of any responsibility and asked to contact Bungie instead, which I hereby do.
To troubleshoot the problem I let PingPlotter run while playing the game. Every time I disconnect, one of the intermediate IPs - er1.ams1.nl.above.net - becomes unresponsive for about a minute. As soon as it sends ICMP responses again, I can log back into the game. I attached two plots showing the observed behavior.
Please help with this very frustrating issue.
Kind regards from Germany!
-
1 ReplyUnfortunately, there's not much Bungie can do about bad routing at the ISP level. What you're observing is indicative of a "connection bleed" that sometimes happens when a peering connection or specific hardware becomes over-saturated. (In simple words: when there are too many connections going through the same route, the ISP will cancel connections until it is stable again) Ultimately, it's the ISP that needs to fix congestion or publish alternate routes. It looks like that endpoint - er1.ams1.nl.above.net - is owned by Zayo. You should try doing the same monitoring when Destiny 2 is NOT running. If you see the same results in PingPlotter then it's definitely a general problem at the ISP level.
-
Third party ISP issue... could try reaching out to Zayo/above.net. Bungie and Vodaphone will just keep pointing elsewhere, because it is happening across a "middle man's" network--basically, not seeing a problem on their network segments, so they "can't do anything about it". Often times that is true because the language of the peering arrangement doesn't provide any leverage when there isn't sufficient bandwidth on the other side of the exchange point. Basically, they may need a new agreement... likely one that requires compensation for increasing bandwidth.
