8 11 ms 11 ms 10 ms mmo-cr3.mmo-cr2.bahnhof.net [46.59.112.6]
9 24 ms 24 ms 24 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
10 24 ms 24 ms 24 ms ae1-br01-eqfr5.blizzardonline.net [137.221.80.33]
11 33 ms 33 ms 33 ms et-0-0-2-br01-eqpa4.blizzardonline.net [137.221.65.26]
12 33 ms 33 ms 33 ms be1-pe01-eqpa4.blizzardonline.net [137.221.77.67]
13 33 ms 33 ms 33 ms 185.60.114.159
This is the final stretch of my route, for comparison with someone not having issues while playing on the same servers. Notice the different path taken inside of the datacenter. The host that is the common factor between almost everyone having this issue is nowhere to be seen in my route, and I never get routed back to the same subnet, which is the case for the ones having issues.
Delmoryth, with all respect, yes there are a lot of people who has issues due to their ISPs, not to mention shoddy home wireless networks, but there is a malfunctioning device, or a mistake in a routing table, on the 137.221.78.0/24 network in the data center. That subnet stands out like firework in all of these threads, and that part of the route makes absolutely no sense.
This issue has been around for atleast half a year, and there is no way noone at Blizzard knows about it.
Edit: When testing another EU server instance, I manage to hit the same subnet. One hop.
9 24 ms 24 ms 24 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
10 24 ms 24 ms 24 ms ae1-br01-eqfr5.blizzardonline.net [137.221.80.33]
11 29 ms 29 ms 29 ms et-0-0-2-br01-eqam1.blizzardonline.net [137.221.65.29]
12 29 ms 29 ms 29 ms et-0-0-31-pe01-eqam1.blizzardonline.net [137.221.78.67]
13 30 ms 30 ms 30 ms 185.60.112.157
I fail to see why the packets from the clients having issues should ever have to double back, and that’s where the huge increase can be seen. Not sure if the problem only exists in the Amsterdam data center, or if that’s just coincidence.