Dropped packet on second hop while doing Traceroute

[shaboobla09]

Hello everyone!

I hope I'm in the right thread, apologies if I'm not. I've been having slight problems with my connection while playing games online. The speed of the connection seems to be constant and stable (as far as I can tell), but I've having lag spikes (about 10 or say per hour), which makes the game somewhat unplayable at times. However, the connection never drops, which is strange. I'm playing the game on my xbox through an ethernet cable and not the wifi.

I've been running Traceroutes through the command prompt, and for the most part the connection looks healthy and gives me this. Bear in mind that I've ran these tests on my desktop computer, which is connected directly to the router through an ethernet cable:

Tracing route to e4073.dscb.akamaiedge.net [23.192.40.182]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 13 ms 11 ms modemcable001.57-131-66.mc.videotron.ca [66.131.57.1]
3 14 ms 14 ms 17 ms 216.113.122.165
4 25 ms 22 ms 23 ms 216.113.126.214
5 19 ms 23 ms 24 ms above.net [198.32.118.25]
6 27 ms 36 ms 35 ms ae10.cs1.lga5.us.zip.zayo.com [64.125.27.156]
7 22 ms 24 ms 20 ms ae15.er1.lga5.us.zip.zayo.com [64.125.29.221]
8 22 ms 29 ms 24 ms 208.185.22.10.IPYX-074089-910-ZYO.zip.zayo.com [208.185.22.10]
9 21 ms 20 ms 22 ms a23-192-40-182.deploy.static.akamaitechnologies.com [23.192.40.182]

But, a couple of my tests have given me this kind of result:

Tracing route to e4073.dscb.akamaiedge.net [23.192.40.182]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 11 ms * modemcable001.57-131-66.mc.videotron.ca [66.131.57.1]
3 14 ms 13 ms 13 ms 216.113.122.165
4 24 ms 27 ms 29 ms 216.113.126.214
5 20 ms 23 ms 22 ms above.net [198.32.118.25]
6 27 ms 28 ms 21 ms ae10.cs1.lga5.us.zip.zayo.com [64.125.27.156]
7 28 ms 24 ms 25 ms ae15.er1.lga5.us.zip.zayo.com [64.125.29.221]
8 29 ms 31 ms 23 ms 208.185.22.10.IPYX-074089-910-ZYO.zip.zayo.com [208.185.22.10]
9 20 ms 21 ms 23 ms a23-192-40-182.deploy.static.akamaitechnologies.com [23.192.40.182]

Does the asterisk on the second hop mean that a packet was lost? There's been other times where I've had an asterisk on the first column and the second as well.The highest ping I've seen was around 50 while doing my tests. And from what I understand, the second hop is the connection to my ISP.

Any help is appreciated.

Thanks!

 

[bill001g]

The only way to really test this is to leave multiple cmd windows open running constant ping to each hop and when the problem happens quickly switch over and see where the problem is happening. Intermittent issues are very hard to troubleshoot.

A packet here and there means nothing. The device in the path may be to busy passing real user data to bother with responding to your ping or tracert. This is also why you may see device in the path that have very high ping times but thing past it have lower. That technically can't happen if there was a actual delay in the path. It is some strangeness with the way the device is processing the data.

What you will generally see is a problem say at hop 3 and that problem continue to the end of the trace with each node in the path seeing loss or getting higher latency spikes.

You really need to hope that the problem is in the first few hips of your trace....what can you do its not like you can call zayo if you see a problem in their network.

 

[shaboobla09]

The only way to really test this is to leave multiple cmd windows open running constant ping to each hop and when the problem happens quickly switch over and see where the problem is happening. Intermittent issues are very hard to troubleshoot.

A packet here and there means nothing. The device in the path may be to busy passing real user data to bother with responding to your ping or tracert. This is also why you may see device in the path that have very high ping times but thing past it have lower. That technically can't happen if there was a actual delay in the path. It is some strangeness with the way the device is processing the data.

What you will generally see is a problem say at hop 3 and that problem continue to the end of the trace with each node in the path seeing loss or getting higher latency spikes.

You really need to hope that the problem is in the first few hips of your trace....what can you do its not like you can call zayo if you see a problem in their network.

I see. Thank you so much for your response. Do you know if there's a way to continuously run a traceroute without having to manually start it every time?

 

[bill001g]

Do not use traceroute use actual ping commands. You can use pathping but that takes huge amounts of resources and and not be run constantly.

 

[shaboobla09]

Do not use traceroute use actual ping commands. You can use pathping but that takes huge amounts of resources and and not be run constantly.

I see. I will probably try that actually. Thank you so much for your help!