Problems with latency

Technical Support
1

Hey. I’m having a latency problems on Diablo 3 Hardcore EU servers. The in-game latency indicator shows 110-200 ms back and forth, while testing the provided IP’s with WinMTR at the same time shows maximum of 60-80 on the last hops.

How could that be and how i troubleshoot that further, cause it’s pretty unplayable when you suddenly start rubber-banding, or monsters don’t die and take damage and you suddenly get spikes of the damage to yourself.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus -    0 |   51 |   51 |    0 |    0 |    4 |    0 |
|                               10.72.0.2 -    0 |   51 |   51 |    3 |    3 |   14 |    3 |
|                         192.168.126.218 -    0 |   51 |   51 |    3 |    3 |   15 |    3 |
|                   No response from host -  100 |   10 |    0 |    0 |    0 |    0 |    0 |
|                           87.226.221.64 -    3 |   48 |   47 |    3 |    3 |   14 |    3 |
|                          188.128.126.65 -    0 |   51 |   51 |   42 |   43 |   66 |   42 |
|                           87.226.221.19 -    0 |   51 |   51 |   48 |   50 |   72 |   48 |
|              ae1-br01-eqfr5.as57976.net -    0 |   51 |   51 |   46 |   47 |  108 |   46 |
|         et-0-0-2-br01-eqam1.as57976.net -    0 |   51 |   51 |   47 |   55 |  154 |   76 |
|                           137.221.65.75 -   70 |   10 |    3 |    0 | 4494 | 4925 | 4379 |
|                           137.221.78.51 -    0 |   51 |   51 |   46 |   46 |   63 |   46 |
|                          185.60.112.157 -    0 |   51 |   51 |   47 |   47 |   49 |   47 |
|________________________________________________|______|______|______|______|______|______|



|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus -    0 |   70 |   70 |    0 |    0 |   12 |    0 |
|                               10.72.0.2 -    5 |   21 |   20 |    0 | 3226 | 4829 | 2603 |
|                         192.168.126.218 -    4 |   62 |   60 |    3 |    3 |   12 |   12 |
|                           77.37.250.227 -   87 |   15 |    2 |    0 |    3 |    3 |    3 |
|                          87.226.221.172 -    0 |   70 |   70 |    4 |    5 |   19 |    4 |
|                         188.128.126.105 -    0 |   70 |   70 |   42 |   43 |   59 |   42 |
|                           87.226.221.19 -    0 |   70 |   70 |   47 |   52 |  140 |   47 |
|              ae1-br01-eqfr5.as57976.net -    0 |   70 |   70 |   45 |   48 |  150 |   46 |
|         et-0-0-2-br01-eqam1.as57976.net -    0 |   70 |   70 |   46 |   56 |  128 |   46 |
|                           137.221.65.75 -    0 |   70 |   70 |   44 |  100 |  398 |  235 |
|                           137.221.78.49 -    0 |   70 |   70 |   45 |   45 |   54 |   46 |
|                          185.60.112.158 -    0 |   70 |   70 |   45 |   45 |   50 |   46 |
|________________________________________________|______|______|______|______|______|______|
3

It seems that you don’t get how traceroute works. You should look for the last hops % of packets. The first hop, which is my router indicates, that 51 packet was sent, and the last one has 51 received. Not all nodes are configured to answer to ping or give accurate packets %, for load reasons i guess. 4rth hop on the first traceroute has 100% packets lost, while ones that are lower have more received, which would make no sense if you think about it.

You can also notice, that 137.221.65.75 from the first trace has 70% packets lost, but on the second one it has none. And that’s Blizzard Entertainment Inc ip in Netherlands, Amsterdam. But, since the latter ones have all packets fine, in reality it has 0% lost, it just don’t report the right data (which this particular node may or may not report at all).

And i’ve got my answer for the problem while watching Wudijo yesterday, who are German streamer that got HC top1. And he had the same problems, rubber-banding and 600 ms ping.

Looks like that the test servers, provided by Blizzard, have nothing to do with their actual servers. And made only for the sole test purpose of testing your own ISP, not the actual problems at Blizzard servers itself.

4

I’m playing with 150-500 ms too. It’s jumping again and again…

Diablo 3 has been dead a long time, but with this patch, it seems like a lot of things have gotten worse. And yes, Blizzard again does not take its own game seriously and, as usual, does not consider its players.

For this reason, I don’t think it will be much different in diablo 4…

It is very foolish to make excuses for people’s computers or internet connections every time a problem arises, to pretend that it is all the fault of the customer. A true blizzard classic.

1 Like