Looking for someone to look at my tracert and tell me what the issue is

Griffsbrown

Honorable
May 10, 2013
96
0
10,630
So here is me running a tracert to google.com a few times:
I ran it three times http://puu.sh/hRXyQ.png
I have time warner cable if it makes any difference. I also recently started using a tp-link wireless card but switched back to ethernet because I thought the wireless card was the issue but it is clearly not because I get the same ping spikes and issues on both ethernet and wireless.

I sort of forgot to mention the actual issue in case anyone knows what it might be. latency just kind of goes all over the place. My ping in League of Legends will be a healthy 100 (in league is the norm) then all of the sudden it's 400 and I can't move and my friends in teamspeak can't hear me and everything goes crazy then like 30 seconds later it's fixed. Then it does it again like 1 to 5 minutes later. Even when I am getting 400+ ping spikes it is still going for around 25 to 60 constantly. I was told to run a tracert to try to find out the issue but I have no idea how to read one of these so I am turning to you guys for some help.
 
Solution
Your tracert shows IPv6 addresses, and there is a (good) chance your game server is IPv4 only. Turn off IPv6 in your router (DNS Server), you should get something like
C:\Users\Me>tracert www.google.com

Tracing route to www.google.com [64.233.178.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms <your router name> [192.168.0.1]
2 11 ms 8 ms 11 ms <your external IP address, e.g. 20.30.40.50>
3 9 ms 8 ms 8 ms <more hops>
16 54 ms 54 ms 59 ms www.google.com 64.233.178.147
tracert basically tells you the ping time to every network hop between you and the destination. For an intermittent problem like yours, you:

1) Need to be running it to the LoL game server you're having problems with, not google.com. It's highly unlikely your network packets travel the same route to the game server as to Google, and tracert will miss the problem if it's happening near the game server.

2) Need to be running tracert when the problem occurs. The three you've posted show no problems. When you get one which shows a problem, it'll have a similar ping time to what you're seeing in game (400 ms if I understand your post right).

Once you get a tracert which shows the problem, you can localize where the problem is occurring. Because the ping times are for each network hop, the ping time will suddenly become very large at the problem hop. If the number gets large near the top, then the problem is probably with your home network or your ISP. If the number gets large near the bottom, then the problem is closer to the game server.

If the problem is with your ISP, giving them a copy of the tracert will help them locate and fix the problem. It basically tells them which switch or router at their end is having problems. Usually it's because traffic exceeds a piece of network hardware's capacity, and it starts dropping packets. Or a misconfigured piece of equipment sending packets where they shouldn't be going.
 
Your tracert shows IPv6 addresses, and there is a (good) chance your game server is IPv4 only. Turn off IPv6 in your router (DNS Server), you should get something like
C:\Users\Me>tracert www.google.com

Tracing route to www.google.com [64.233.178.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms <your router name> [192.168.0.1]
2 11 ms 8 ms 11 ms <your external IP address, e.g. 20.30.40.50>
3 9 ms 8 ms 8 ms <more hops>
16 54 ms 54 ms 59 ms www.google.com 64.233.178.147
 
Solution