Community Forum

weird hop in tracert

Frequent Visitor

weird hop in tracert

My latency has almost tripled since last week to my server in NYC and I see a hop that was not there before this latency increase

Notice hop #5, it routes me from MA at 9ms to IL at 37ms and then back to NY where my ping stays high. 

I used to have 20-22ms latency to this server.

Any ideas on how to get this route fixed? I contacted comcast rep and they were not much help.

 

Tracing route to NYC.MADHOUSESERVERS.COM [70.42.74.100]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 7 ms 9 ms 9 ms 96.120.69.17
3 16 ms 14 ms 8 ms GE-1-44-ur01.lowell.ma.boston.comcast.net [68.87.155.185]
4 9 ms 9 ms 9 ms be-321-ar01.woburn.ma.boston.comcast.net [96.108.68.21]
5 38 ms 37 ms 37 ms be-7015-cr02.350ec7
ermak.il.ibone.comcast.net [68.86.91.5]
6 58 ms 58 ms 57 ms be-10305-cr02.newyork.ny.ibone.comcast.net [68.86.85.201]
7 55 ms 57 ms 57 ms be-10381-pe02.111eighthave.ny.ibone.comcast.net [68.86.86.250]
8 57 ms 62 ms 57 ms 96-87-8-82-static.hfc.comcastbusiness.net [96.87.8.82]
9 60 ms 56 ms 56 ms border2-po2-bbnet2.nyj004.pnap.net [216.52.95.110]
10 56 ms 57 ms 57 ms inap-b2e2.e6.router.nyc.nfoservers.com [70.42.74.253]
11 57 ms 56 ms 57 ms NYC.MADHOUSESERVERS.COM [70.42.74.100]

Trace complete.

 

Next here is a tracert to my Ashburn, VA server, notice how hop 5 is not to IL but is a hop in MA as it should be. And hop 4 is the same as tracert above, weird.

 

Tracing route to ash.madhouseservers.com [198.7.63.132]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 10.0.0.1
2 8 ms 9 ms 8 ms 96.120.69.17
3 8 ms 9 ms 6 ms ge-1-44-ur02.lowell.ma.boston.comcast.net [68.87.155.189]
4 11 ms 10 ms 11 ms be-321-ar01.woburn.ma.boston.comcast.net [96.108.68.217]
5 9 ms 11 ms 9 ms be-1002-pe02.onesummer.ma.ibone.comcast.net [68.86.90.85]
6 9 ms 10 ms 9 ms 96-87-9-86-static.hfc.comcastbusiness.net [96.87.9.86]
7 40 ms 40 ms 41 ms xe-3-1-4.cr0-was1.ip4.gtt.net [213.254.214.214]
8 42 ms 42 ms 41 ms ip4.gtt.net [69.174.3.38]
9 42 ms 41 ms 42 ms po-3.ce02.wdc-01.us.leaseweb.net [108.59.15.103]
10 42 ms 40 ms 44 ms hosted.by.leaseweb.com [108.59.15.22]
11 40 ms 45 ms 41 ms 198.7.63.132

Trace complete.

Diamond Problem Solver

Re: weird hop in tracert

Did you use the exact same domain name in both of those traces ? I ask because they resolved to different numerical IP addresses and different routing which can't be directly compared. This is not to say that you are not perceiving a problem of some sort.