Pinging servers are fine but in game latency high

  • I am kind of getting sick of this to be honest. Everyone always tells me to run a ping test to europe servers. Being in South Africa, our pings are expected to be around 220 to 280, which is completely manageable. So here you can see I ping the Europe servers and all is honky dory from what I can tell with a constant 200+ms ping time:

    Pinging 185.60.112.157 with 32 bytes of data:
    Reply from 185.60.112.157: bytes=32 time=214ms TTL=235
    Reply from 185.60.112.157: bytes=32 time=218ms TTL=235
    Reply from 185.60.112.157: bytes=32 time=214ms TTL=235
    Reply from 185.60.112.157: bytes=32 time=214ms TTL=235

    Pinging 185.60.112.158 with 32 bytes of data:
    Reply from 185.60.112.158: bytes=32 time=222ms TTL=235
    Reply from 185.60.112.158: bytes=32 time=219ms TTL=235
    Reply from 185.60.112.158: bytes=32 time=220ms TTL=235
    Reply from 185.60.112.158: bytes=32 time=220ms TTL=235


    So then can I ask WHY THE HELL in the last few months I have been playing D3 I keep getting above 400-1000ms latency most of the damned time? And it is ONLY D3 that does this. Heroes of the Storm I get a constant 220, Overwatch a constant 219-225, and when I played it Wow was always on 220 even when downloading.

    It is ONLY Diablo 3 that keeps doing this ever since I bought the original game before the expansion, but back then it wasn't so bad. It's gotten worse as time went by. I have formatted my PCs, switched ISPs, swapped out network cards, tried wifi, tried mobile data, tinkered with network settings, reinstalled multiple versions of Win 7, 8 and 10, redownloaded the game you name it. Even got an entire new computer. IT IS ALWAYS THE SAME!

    I have browsed these forums and others as well for possible solutions. And none of them worked.

    And after 4 years of this I am sick and tired! I shall not be buying the Necromancer pack until I have some damned answers. And if my case is a lost cause, then I demand a refund for the game and expansion I purchased in full as I deem the product useless and broken. Might buy the console version instead because there I won't have any "trust" issues with Blizzard to be constantly online all the damn time. But what do we know in Africa? You got our money already right? So f*** us then. Maybe open a server in Africa so we won't have these issues, but "f*** them we got their money" amiright?

    I can't run higher level greater rifts because of this. One moment everything is standing in place the next I am dead. Trying to run a thorns crusader is nearly impossible because of all the rubberbanding. And AGAIN: THIS IS ONLY DIABLO 3 THAT DOES THIS!?!?!?!?!?!? Why are the other games having NO problems whatsoever?

    Here is my path ping for whatever it's worth. Don't think it will help at all as I have seen other users do the same and get no answers from you people.

    Tracing route to 185.60.112.157 over a maximum of 30 hops

    1 2 ms 2 ms 2 ms 192.168.1.254
    2 * * * Request timed out.
    3 36 ms 35 ms 36 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
    4 38 ms 36 ms 37 ms 169-1-5-250.ip.afrihost.co.za [169.1.5.250]
    5 148 ms 161 ms 147 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
    6 101 ms 98 ms 96 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
    7 38 ms 37 ms 36 ms 41.169.57.216
    8 * 141 ms 141 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
    9 221 ms 232 ms 216 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
    10 207 ms 207 ms 207 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.97]
    11 307 ms 305 ms 327 ms if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
    12 * 313 ms 317 ms if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
    13 310 ms 309 ms 309 ms if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
    14 295 ms 311 ms 305 ms if-ae-2-2.tcore1.WYN-Marseille.as6453.net [80.231.217.1]
    15 310 ms 295 ms 291 ms if-ae-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
    16 207 ms 208 ms 208 ms if-ae-11-2.tcore1.PVU-Paris.as6453.net [80.231.153.49]
    17 311 ms 311 ms 343 ms 80.231.153.66
    18 * * * Request timed out.
    19 310 ms 315 ms 314 ms BLIZZARD-EN.ear2.Paris1.Level3.net [212.73.205.158]
    20 301 ms 292 ms 290 ms 37.244.9.33
    21 * * * Request timed out.
    22 309 ms 319 ms 321 ms 185.60.112.157

    Trace complete.


    And I have tried programs like wtfast and even they can't completely fix the issue, making my pings range from 250 when quiet to jumping to 400 when things get busy. Also, why do I have to pay ANOTHER service for better pings when it is the freaking job of the company who makes the games' jobs to be certain that it does play smooth?
  • Hey, Raionhato!

    <code>5 148 ms 161 ms 147 ms jhb-net1.ip.adsl.co.za [169.1.5.52] </code>

    It appears you are getting way higher than normal ms rates on a Afrihost node before your connection leaves South Africa.

    <code>8 * 141 ms 141 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]</code>

    You are also seeing dropped pings on a LIR backbone connection in South Africa.

    It just gets much worse from there, well before it reaches our servers. This appears to be a local connection or ISP issue. If you are on a wireless connection, I would first start by trying a wired Ethernet connection to see if that helps at all.

    I would also recommend trying the Connection Troubleshooting article steps before contacting your ISP (Afrihost) to let them know about these routing nodes. Just help narrow down any other possible causes for this poor of a connection when routed to our servers.
  • The information provided is a fact. It is not an opinion. The answer is you have a bad connection to our servers. The route you are taking to get to the server you ran the trace route to is not a solid connection. It appears to be your ISP having issues on certain nodes. I see you have been on the exact same connection for over a year.

    I completely understand that it is frustrating, but that is the answer we can give you. If it was our servers, every single other player would have the exact same issue you are experiencing. This is not the case. The best option would be to contact your Internet Service Provider.