Good afternoon, for the last couple of days I’ve been experiencing very big problems in the game, a very high ping.
traceroute 185.60.112.157
6 50 ms 41 ms * amsterdam-nik-b1-xe0-0-2-vlan3831.fiord. net
7 42 ms 41 ms 47 ms 80.249.208.83
8 * * * Request timed out.
9 * * * Request timed out.
10 41 ms * 41 ms et-0-0-1-pe03-eqam3.as57976. net
11 134 ms * * 185.60.112.157
12 * * 39 ms 185.60.112.157
Specifically, node ae1-br04-eqam3.as57976. net shows latency spikes up to 439 ms. My local connection and provider’s nodes are stable (1-40 ms).
2 Likes
blizzard just likes money, they stopped caring about the quality of the service long time ago
Some feedback with regards to this on my end.
I managed to speak to a tech at my ISP, initially they said there was no problem on their end, and 3rd party issues are out of their hands, as in when they hand off the local to the international 3rd party network carrier. Turns out they did find a fault on the 3rd party network, flagged it and escalated it to them, and after logging on at 7.30pm tonight its been stable till now, did some dungeons to be sure, and all seems well.
I’ll monitor it this weekend to be sure, but so far so good.
To the OP - Try contacting your ISP and ask them to check the 3rd party network for overloaded nodes or a potential fault. It may not lie directly with your ISP, but let them know and they may be able to contact their 3rd carrier and check things out. Maybe search which networks your ISP uses to connect you to Blizzard, so you have a better idea and can chat to them about flagging any potential faults.
Id suggest using WinMRT to check the hops instead of a tracert. It actively pings the connections until you stop it. Ideally run it for a bout 10 mins when the game is running and
you can check your windows resource monitor for the specific IP address to use in WinMRT.
Generally hops 11 & 12 are false positives and can be ignored. Only concerning if the rest of the hops are high too, but if it drops back down to normal ping after a high one there is nothing to worry about. However if the rest are all high, then there is a bottle neck on that node and it needs to be addressed.