Global Crossing
IP Network Performance
Looking Glass Utilities - Router to Host Traceroute
Allows a user to view all router hops encountered in the path between a Global Crossing node and a specified URL address

Choose a source:
 
 
Specify a destination host
( ie. www.globalcrossing.com )




Trying trace from node 'Cleveland, OH, US' to '209.131.36.158'


     1 fe0-1-0-202-100M.ar1.cle1.gblx.net (64.214.8.97) 0.645 ms 0.471 ms
     2 TE9-1-10G.ar2.DCA3.gblx.net (67.17.108.17) 17.267 ms 17.479 ms
     3 yahoo-6.ar2.DCA3.gblx.net (64.215.195.110) 17.421 ms 17.331 ms
     4 so-0-0-0.pat2.pao.yahoo.com (216.115.101.130) 68.795 ms 68.169 ms
     5 g-0-0-0-p141.msr1.sp1.yahoo.com (216.115.107.51) 68.811 ms g-1-0-0-p151.msr2.sp1.yahoo.com ms
     6 te-8-1.bas-a1.sp1.yahoo.com (209.131.32.17) 68.831 ms te-9-1.bas-a1.sp1.yahoo.com ms
     7 * (*) * ms * ms
     8 * (*) * ms * ms
     9 * (*) * ms * ms
     10 * (*) * ms * ms
     11 * (*) * ms * ms
     12 * (*) * ms * ms
     13 * (*) * ms * ms
     14 * (*) * ms * ms
     15 * (*) * ms * ms
     16 * (*) * ms * ms
     17 * (*) * ms * ms
     18 * (*) * ms * ms
     19 * (*) * ms * ms
     20 * (*) * ms * ms
     21 * (*) * ms * ms
     22 * (*) * ms * ms
     23 * (*) * ms * ms
     24 * (*) * ms * ms
     25 * (*) * ms * ms
     26 * (*) * ms * ms
     27 * (*) * ms * ms
     28 * (*) * ms * ms
     29 * (*) * ms * ms
     30 * (*) * ms * ms

Command completed

If a returned message contains or is completely composed of ***, this is probably the result of a filtering device (i.e. firewall) encountered along the path being traced. The same explanation would apply for no output in the case of a ping query.