Search code examples
timeoutpingrouterlaglatency

Ping timeout on tracert second node

I have been having occasional lag spikes while playing online realtime games (LoL for example). I ran a tracert to LoL's servers (216.52.241.254):

C:\Windows\system32>tracert -d 216.52.241.254

Tracing route to 216.52.241.254 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    29 ms    29 ms    26 ms  68.84.4.1
  3    10 ms     8 ms    10 ms  68.85.80.165
  4     9 ms    11 ms    70 ms  68.85.130.85
  5    14 ms    15 ms    15 ms  68.86.90.85
  6    12 ms    12 ms    11 ms  68.86.82.222
  7    13 ms    13 ms    12 ms  66.208.229.142
  8    48 ms    13 ms    13 ms  154.54.6.170
  9    26 ms    25 ms    26 ms  154.54.31.97
 10    44 ms    45 ms    46 ms  154.54.29.222
 11    75 ms    74 ms    73 ms  154.54.7.158
 12    76 ms    75 ms    75 ms  154.54.47.170
 13    76 ms    76 ms    75 ms  154.24.22.122
 14    77 ms    74 ms    74 ms  38.104.77.122
 15    74 ms    74 ms    75 ms  216.52.241.254

Trace complete.

and did a ping -t to the first few nodes to see if the problem showed up there. I let that run while I was playing, and checked on it whenever I had a lag spike or disconnect. The results for the first two nodes:

Localhost:

C:\Windows\system32>ping -t 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

...omitted...

Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
Control-C
^C

Second node:

C:\Windows\system32>ping -t 68.84.4.1

Pinging 68.84.4.1 with 32 bytes of data:

...omitted...

Reply from 68.84.4.1: bytes=32 time=8ms TTL=254
Reply from 68.84.4.1: bytes=32 time=14ms TTL=254
Reply from 68.84.4.1: bytes=32 time=12ms TTL=254
Reply from 68.84.4.1: bytes=32 time=10ms TTL=254
Reply from 68.84.4.1: bytes=32 time=15ms TTL=254
Reply from 68.84.4.1: bytes=32 time=10ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 68.84.4.1: bytes=32 time=11ms TTL=254
Reply from 68.84.4.1: bytes=32 time=11ms TTL=254
Reply from 68.84.4.1: bytes=32 time=10ms TTL=254
Reply from 68.84.4.1: bytes=32 time=8ms TTL=254
Reply from 68.84.4.1: bytes=32 time=10ms TTL=254
Reply from 68.84.4.1: bytes=32 time=9ms TTL=254
Reply from 68.84.4.1: bytes=32 time=14ms TTL=254
Reply from 68.84.4.1: bytes=32 time=10ms TTL=254
Reply from 68.84.4.1: bytes=32 time=15ms TTL=254
Request timed out.

Ping statistics for 68.84.4.1:
    Packets: Sent = 2911, Received = 2889, Lost = 22 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 2953ms, Average = 12ms
Control-C
^C

Each line of the results should roughly match the corresponding line in the other in terms of time of ping. Sometimes, I have multiple timeouts like above, while other times, it is only one or two lines with very high latency (>900ms). I also had results for a few more nodes, but those had the same behavior, so I figured the problem was in the second node.

I recently got a new router because Comcast cut off our internet, saying, "You have to upgrade your router. It's outdated and you're not taking advantage of the speedups we've been implementing in your area." I cannot recall if we had this lag spike problem before we got the new router because I spent most of my time at school.

My question is: Is this a problem with my router or with the house's connection to the rest of the internet?

EDIT: The problem seems to arise only when I am playing. I have been running a ping -t to 68.84.4.1 for the last hour while not playing, and have not seen it timeout a single time. The results are:

Ping statistics for 68.84.4.1:
    Packets: Sent = 3477, Received = 3476, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 88ms, Average = 10ms

Over the entire hour, the max latency was 88ms, and only 1 packet was lost.

Solution

  • There can be a number of reasons that cause games to lag on a machine besides the internet connection. Assuming that the problem lies in your connection

    The first point is most relevant to your question, rest are just suggestions

    1. Perform a "full" Speedtest: the data you provided only tells half of the story, do a proper speed test using some online service like Speedtest.net by Ookla. Network games have high bandwidth requirements so take a note of the (total) bandwidth that comes to your home. If no other devices and/or program is consuming your network bandwith, you shall have a similar value. you may also do a DNS speed test using Namebench

    2. Use a Wired Connection: A wireless connection will always add latency to bandwidth. Disconnect from the router and use a wired connection directly to the computer. Also, if others are using the router at the same time, it is possible that there are too many people grabbing for the same bandwidth. However if that is not possible make sure that the router is properly configured. It must be in the right position, at the right elevation, wireless channel etc for optimal performance. There are number of guides available online which you can follow. Also look out for any new wireless networks in your area that may interfere with your signal. Try a different router firmware, as some routers have broken firmware and don't perform well on excess load , give Gargoyle or OpenWRT a chance if you are desperate.

    3. Close down other applications that use the internet

    4. Optimize your game settings: All popular online games have network settings, its just a case of finding them. Search online for a guide to tweaking your game.

    5. Turn on Compound TCP, which increases the TCP window much quicker than the traditional TCP algorithms allow for. This means that when a sudden burst of larger packets comes in, or goes out, Windows adjusts its settings faster than normal to compensate for it, allow for faster data transfer on broadband connections and lower latency while gaming.

      netsh int tcp set global congestionprovider=ctcp

    6. Enable UPnP on your router: This will automatically route the correct data to the correct ports.

    7. Experiment at different days and time for lags

    8. Try a Speed optimizer like SG TCP Optimizer

    9. Lastly make sure that you have the latest Drivers installed and are using compatible hardware.