High latency (trace included)

Anjunabeats-twisting-nether · August 21, 2019, 5:58am

Hi,

I’ve been playing at my home setup for last 2 years with 60-70ms ping but for last 2 weeks lowest ping I get is around 170.

I did one trace route from my home gaming pc and another trace route from my work gamingish pc to compare, they both have adsl connections. The ping at work pc is constantly around 70. Can you please tell me on which side the problem is located and how this can be solved?

Here are the trace results:
tracert-home-high

Tracing route to 185.60.112.157 over a maximum of 30 hops

  1    71 ms    <1 ms    <1 ms  192.168.1.1 
  2     7 ms     7 ms     6 ms  94.120.72.1 
  3     8 ms     8 ms     7 ms  192.168.242.17 
  4    10 ms     9 ms    10 ms  10.59.11.9 
  5    23 ms    22 ms    22 ms  10.38.218.81 
  6    21 ms    21 ms    21 ms  10.38.219.34 
  7    21 ms    21 ms    21 ms  10.36.6.2 
  8    62 ms    62 ms    62 ms  blizzard.milano58.mil.seabone.net [195.22.192.29] 
  9   168 ms   169 ms   168 ms  ae1-br01-eqml2.as57976.net [137.221.82.33] 
 10   169 ms   169 ms   169 ms  xe-0-0-1-1-br01-eqpa4.as57976.net [137.221.65.60] 
 11   169 ms   169 ms   168 ms  et-0-0-29-br02-eqpa4.as57976.net [137.221.65.35] 
 12     *        *        *     Request timed out.
 13   212 ms   169 ms   169 ms  et-0-0-67-pe02-eqam1.as57976.net [137.221.78.73] 
 14   169 ms   168 ms   168 ms  185.60.112.157 

Trace complete.

tracert-work-low

Tracing route to 185.60.112.157 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.2.1 
  2     8 ms     8 ms     8 ms  81.212.171.37.static.turktelekom.com.tr [81.212.171.37] 
  3     *       11 ms    10 ms  93.155.0.133 
  4     *       11 ms    13 ms  81.212.78.205.static.turktelekom.com.tr [81.212.78.205] 
  5    12 ms    10 ms    11 ms  00-gayrettepe-xrs-t2-1---00-zeytinburnu-t3-1.statik.turktelekom.com.tr [212.156.108.244] 
  6    65 ms    58 ms    58 ms  306-mil-col-1---35-izmir-xrs-t2-2.statik.turktelekom.com.tr [212.156.141.214] 
  7    77 ms    67 ms    67 ms  ae51.edge1.Milan1.Level3.net [213.249.105.169] 
  8    67 ms    67 ms    72 ms  ae-2-7.bear1.Milan2.Level3.net [4.69.211.21] 
  9    64 ms    63 ms    63 ms  BLIZZARD-EN.bear1.Milan2.Level3.net [213.242.65.246] 
 10    67 ms    67 ms    68 ms  ae1-br01-eqml2.as57976.net [137.221.82.33] 
 11    70 ms    69 ms    69 ms  xe-0-0-1-1-br01-eqpa4.as57976.net [137.221.65.60] 
 12    88 ms    68 ms     *     et-0-0-29-br02-eqpa4.as57976.net [137.221.65.35] 
 13    69 ms    69 ms     *     et-0-0-3-br02-eqam1.as57976.net [137.221.65.93] 
 14    87 ms    69 ms    80 ms  et-0-0-67-pe02-eqam1.as57976.net [137.221.78.73] 
 15     *       75 ms     *     137.221.66.47 
 16    68 ms    69 ms    69 ms  185.60.112.157 

Trace complete.

Anjunabeats-twisting-nether · August 24, 2019, 10:06am

Any official comment about where the problem lies? This pings sucks the joy out of game.

Disq-ravencrest · August 25, 2019, 9:48am

From what I can see, this is where it goes wrong:

8 62 ms 62 ms 62 ms blizzard.milano58.mil.seabone.net [195.22.192.29]

Your home trace and work trace differ obviously, but from this server onwards, it is the same:

10 67 ms 67 ms 68 ms ae1-br01-eqml2.as57976.net [137.221.82.33]

So it most likely is the blizzard.milano58.mil.seabone.net where I would look at. That is something though only Blizzard can see.

However, this interests me more:

1 71 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 6 ms 94.120.72.1
3 8 ms 8 ms 7 ms 192.168.242.17

Your home router first has a ping of 71 ms and then it goes to <1 <1. Furthermore, it goes from internal (correct) to external (correct) back to internal (???).

94.120.72.1 is from DOL AYDIN - VAE ADSL DYNAMIC. That’s fine and I confirmed as well 192.168.242.17 is a private internal address. So why is that? And why is your router reacting so slowly?

Can you do me a favour? Can you do two commands from CMD and give me the output?

ping 192.168.1.1 -n 50

ping 192.168.242.17 -n 50

With these two, I want to see if there is any interference going on. I am also still curious what this 192.168.242.17 is.

Anjunabeats-twisting-nether · August 25, 2019, 7:20pm

Hi,
Thanks a lot for detailed reply.

94.120.72.1 is labeled as Default Gateway on modem settings page.
192.168.242.17 is not shown on DHCP client list.
Here is the info you requested from command line:

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254
Reply from 192.168.1.1: bytes=32 time<1ms TTL=254

Ping statistics for 192.168.1.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.242.17 with 32 bytes of data:
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128
Reply from 192.168.242.17: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.242.17:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Elahri-silvermoon · August 25, 2019, 7:50pm

Probably isp infrastructure.

Disq-ravencrest · August 25, 2019, 7:56pm

Why is the gateway going to another internal IP? that makes no sense. That means the gateway goes to another gateway, potentially thus causing a switch loop.

It is strange that it always gives <1 ms for 192.168.1.1 while it gave 71 ms at one point. Maybe it is spiking? Have you tried updating the firmware of your router? Also check with your ISP what that weird tracing is.

Anjunabeats-twisting-nether · August 25, 2019, 9:22pm

Ping spike happens on Blizzard servers but I can’t get an official reply on this post. Is there any other place to get in contact with Blizz about this issue?

Disq-ravencrest · August 25, 2019, 10:27pm

You can contact support for it, but I would recommend to first check with your ISP why your routing is so weird. Ensuring that the routing is correct is a task for your ISP.