Pinging servers are fine but in game latency high

Technical Support
It sounds trivial, but often just rebooting everything - router, modem, computer - can fix an issue.

The problem with lag is that it is an effect that can have many causes. Just because you are experiencing the same symptoms are someone else doesn't mean it has the same cause. 100 people can be seeing the same behavior in game, and for some it can be caused by a bad network card, some by a loose cable, some by a faulty switch at their ISP, some by old or faulty wifi drivers, some because of issues at a backbone peering-partner, and some because of performance issues.
Im also from South Africa, Cape Town more specifically. I have 100mbps uncapped fibre with 93mbps down on international link test with 48mpbs up. 5ms to our local ISP and 150ms to a london based server. Pinging the D3 EU servers i get between 153-160ms pings but just now while ingame i had 2930-3000+ ms response times. This does not happen often but when it does it can stay like that for 3-4 days. Although I am very patient with this, it tends to get annoying. I have been around from almost day 1 in D3 lifespan and this problem only started recently for me.
This is what i found on a tracert:
4 4 ms 3 ms 3 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 5 ms 3 ms 4 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 4 ms 4 ms 6 ms 41.193.120.37
7 146 ms 144 ms 144 ms vox-ldn-telecity-wacs.vox.co.za [196.41.24.174]
8 145 ms 143 ms 143 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.13]
9 * * * Request timed out.
10 148 ms 146 ms 147 ms 195.50.122.138
11 147 ms 146 ms 146 ms ae1-br01-eqld5.blizzardonline.net [137.221.79.33]
12 * * * Request timed out.
13 152 ms 152 ms 153 ms et-0-0-67-pe02-eqam1.blizzardonline.net [137.221.78.73]
14 151 ms 152 ms 152 ms 185.60.112.157

if my assumption is correct packet loss happens between 8 and 10 as well as 11 to 13.
the 195.50.xxx.xxx are registered here:
inetnum: 195.50.64.0 - 195.50.127.255
netname: UK-LVLT-970212
country: GB
while the 137.221.xxx.xxx are French based servers:
inetnum: 137.221.64.0 - 137.221.127.255
netname: US-BLIZZARD1-19900110
country: FR

The 185.60.xxx.xxx also French based. The packet losses happens there and not locally as suggested.
@NightRaven
I don't see any data packet loss in your log.
9 * * * Request timed out.
12 * * * Request timed out.
^^^ These are not data loss. These devices are configured to ignore test messages. This is a common practice for security reasons. I.e. we can't tell the healthiness of these devices. However, the following hops showed the pings were normal. So, we can say that these devices are in good condition.

Tracert test only sent 3 test messages per hop. The sampling size is very small and may not find the cause. You may try the WinMTR test instead. The procedure can be found in this technical article: https://us.battle.net/support/en/article/27780

Also, this thread is already 1 year old. Better to create a new topic for your own.
Locking this thread as it is an older thread. As Maskraider suggested, it's best to create a new and recent thread on this topic with a WinMTR test to check for further details going on with the connection.

Thank you!

Join the Conversation

Return to Forum