Ping timeout on tracert second node -

Ping timeout on tracert second node -

i have been having occasional lag spikes while playing online realtime games (lol example). ran tracert lol's servers (216.52.241.254):

c:\windows\system32>tracert -d 216.52.241.254 tracing route 216.52.241.254 on 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 ping -t first few nodes see if problem showed there. allow run while playing, , checked on whenever had lag spike or disconnect. results first 2 nodes:

localhost:

c:\windows\system32>ping -t 192.168.0.1 pinging 192.168.0.1 32 bytes of data: ...omitted... reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=2ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 reply 192.168.0.1: bytes=32 time=1ms ttl=64 ping statistics 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 32 bytes of data: ...omitted... reply 68.84.4.1: bytes=32 time=8ms ttl=254 reply 68.84.4.1: bytes=32 time=14ms ttl=254 reply 68.84.4.1: bytes=32 time=12ms ttl=254 reply 68.84.4.1: bytes=32 time=10ms ttl=254 reply 68.84.4.1: bytes=32 time=15ms ttl=254 reply 68.84.4.1: bytes=32 time=10ms ttl=254 request timed out. request timed out. request timed out. request timed out. reply 68.84.4.1: bytes=32 time=11ms ttl=254 reply 68.84.4.1: bytes=32 time=11ms ttl=254 reply 68.84.4.1: bytes=32 time=10ms ttl=254 reply 68.84.4.1: bytes=32 time=8ms ttl=254 reply 68.84.4.1: bytes=32 time=10ms ttl=254 reply 68.84.4.1: bytes=32 time=9ms ttl=254 reply 68.84.4.1: bytes=32 time=14ms ttl=254 reply 68.84.4.1: bytes=32 time=10ms ttl=254 reply 68.84.4.1: bytes=32 time=15ms ttl=254 request timed out. ping statistics 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 results should match corresponding line in other in terms of time of ping. sometimes, have multiple timeouts above, while other times, 1 or 2 lines high latency (>900ms). had results few more nodes, had same behavior, figured problem in sec node.

i got new router because comcast cutting off our internet, saying, "you have upgrade router. it's outdated , you're not taking advantage of speedups we've been implementing in area." cannot recall if had lag spike problem before got new router because spent of time @ school.

my question is: problem router or house's connection rest of internet?

edit: problem seems arise when playing. have been running ping -t 68.84.4.1 lastly hr while not playing, , have not seen timeout single time. results are:

ping statistics 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 entire hour, max latency 88ms, , 1 packet lost.

there can number of reasons cause games lag on machine besides net connection. assuming problem lies in connection

the first point relevant question, rest suggestions

perform "full" speedtest: info provided tells half of story, proper speed test using online service speedtest.net ookla. network games have high bandwidth requirements take note of (total) bandwidth comes home. if no other devices and/or programme consuming network bandwith, shall have similar value. may dns speed test using namebench

use wired connection: wireless connection add together latency bandwidth. disconnect router , utilize wired connection straight computer. also, if others using router @ same time, possible there many people grabbing same bandwidth. if not possible create sure router configured. must in right position, @ right elevation, wireless channel etc optimal performance. there number of guides available online can follow. out new wireless networks in area may interfere signal. try different router firmware, routers have broken firmware , don't perform on excess load , give gargoyle or openwrt chance if desperate.

close downwards other applications utilize internet

optimize game settings: popular online games have network settings, case of finding them. search online guide tweaking game.

turn on compound tcp, increases tcp window much quicker traditional tcp algorithms allow for. means when sudden burst of larger packets comes in, or goes out, windows adjusts settings faster normal compensate it, allow faster info transfer on broadband connections , lower latency while gaming.

netsh int tcp set global congestionprovider=ctcp

enable upnp on router: automatically route right info right ports.

experiment @ different days , time lags

try speed optimizer like sg tcp optimizer

lastly create sure have latest drivers installed , using compatible hardware.

timeout ping router lag latency