| Packet loss to some IP addressesHaving a weird issue. I have been getting bad trace routes to a couple IP addresses. Here's a log:
C:\Users\Jcink>tracert 24.11.185.132
Tracing route to c-24-11-185-132.hsd1.mi.comcast.net [24.11.185.132]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 4 ms 4 ms 4 ms L300.NWRKNJ-VFTTP-90.verizon-gni.net [96.242.25.
1]
3 6 ms 7 ms 19 ms G0-13-1-2.NWRKNJ-LCR-21.verizon-gni.net [130.81.
109.104]
4 * * * Request timed out.
5 28 ms 12 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.17.6]
6 12 ms 16 ms 17 ms Vlan590.icore1.NTO-NewYork.as6453.net [209.58.26
.93]
7 11 ms 12 ms 12 ms Vlan546.icore1.NTO-NewYork.as6453.net [209.58.26
.58]
8 17 ms 11 ms 14 ms pos-1-8-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.86.45]
9 19 ms 17 ms 22 ms pos-0-9-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.87.61]
10 44 ms 47 ms 47 ms pos-0-15-0-0-ar01.taylor.mi.michigan.comcast.net
[68.86.90.106]
11 49 ms 52 ms 49 ms te-7-3-ur01.holt.mi.michigan.comcast.net [69.139
.254.126]
12 58 ms 59 ms 69 ms 68.85.48.82
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17C:\Users\Jcink>tracert 76.17.161.58
Tracing route to c-76-17-161-58.hsd1.mn.comcast.net [76.17.161.58]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 4 ms 4 ms 4 ms L300.NWRKNJ-VFTTP-90.verizon-gni.net [96.242.25.
1]
3 6 ms 9 ms 7 ms G0-14-0-4.NWRKNJ-LCR-21.verizon-gni.net [130.81.
187.152]
4 * * * Request timed out.
5 12 ms 14 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.17.6]
6 11 ms 14 ms 17 ms Vlan590.icore1.NTO-NewYork.as6453.net [209.58.26
.93]
7 11 ms 12 ms 14 ms Vlan578.icore1.NTO-NewYork.as6453.net [209.58.26
.118]
8 13 ms 12 ms 12 ms pos-1-12-0-0-cr01.newyork.ny.ibone.comcast.net [
68.86.86.193]
9 40 ms 39 ms 38 ms pos-0-11-0-0-cr01.350ecermak.il.ibone.comcast.ne
t [68.86.88.174]
10 45 ms 47 ms 44 ms pos-0-15-0-0-ar01.roseville.mn.minn.comcast.net
[68.86.94.82]
11 66 ms 67 ms 67 ms te-0-0-0-4-ar01.crosstown.mn.minn.comcast.net [6
8.87.174.193]
12 67 ms 67 ms 67 ms te-8-4-ur01.minnetonka.mn.minn.comcast.net [69.1
39.176.10]
13 67 ms 67 ms 67 ms te-2-1-ur02.minnetonka.mn.minn.comcast.net [69.1
39.176.14]
14 66 ms 67 ms 67 ms te-8-4-ur01.stlouispark.mn.minn.comcast.net [69.
139.176.18]
15 67 ms 67 ms 67 ms 68.85.165.42
16 * * * Request timed out.
It always seems like the problem is somewhere with the 4th hop. I don't have this problem with any other IP addresses that I know of.
Here's a normal trace, things are fine consistently when I run this:
C:\Users\Jcink>tracert youtube.com
Tracing route to youtube.com [74.125.226.234]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 4 ms 4 ms L300.NWRKNJ-VFTTP-90.verizon-gni.net [96.242.25.
1]
3 6 ms 6 ms 7 ms G0-14-0-4.NWRKNJ-LCR-21.verizon-gni.net [130.81.
187.152]
4 8 ms 7 ms 7 ms 130.81.199.14
5 8 ms 7 ms 7 ms 0.so-7-0-0.XL3.EWR6.ALTER.NET [152.63.19.177]
6 11 ms 12 ms 12 ms 0.xe-2-1-0.XT1.NYC4.ALTER.NET [152.63.18.58]
7 8 ms 9 ms 9 ms TenGigE0-6-1-0.GW8.NYC4.ALTER.NET [152.63.21.113
]
8 20 ms 9 ms 9 ms google-gw.customer.alter.net [152.179.72.62]
9 39 ms 52 ms 14 ms 216.239.43.114
10 10 ms 9 ms 9 ms 72.14.239.252
11 10 ms 12 ms 12 ms lga15s29-in-f10.1e100.net [74.125.226.234]
Trace complete.
Anyone else having the same problems with these? How can I get this issue fixed? This is a business account with a static IP that I've had for years now. |
|
 More FiberPremium,MVM
join:2005-09-26
West Chester, PA
kudos:28 | said by Jcink:It always seems like the problem is somewhere with the 4th hop. If the 4th router is configured not to respond to pings, it will appear as a timeout.
That does not mean that is where the problem is. Your ping times to the 5th router are normal (12ms), so there is nothing wrong with the 4th router.
--
There are 10 kinds of people in the world; those who understand binary and those who don't.
|
|
| reply to Jcink
I just thought maybe it could have something to do with it along the line, but you're right.
It's interesting, these are both comcast users and it seems like after the 68.85. range there's problems with completing a connection. The trace can never complete. Maybe the issue actually needs to be directed to Comcast? |
|
 Zero
join:2009-07-01
Collegeville, PA | I just tried doing traceroutes and pings to your two IPs and I'm getting the same results on FiOS. As stated above by More Fiber  the 4th hop issue is harmless, it appears to just be a new router Verizon installed and forgot to configure to respond to ICMP.
I also did these same traceroutes and pings on a local Comcast account to see if the results were different and they weren't (except for the 4th hop obviously). So whatever your issue is it appears to exist on Comcast's side close to your static IPs. |
|
