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
Trying trace from node 'Cleveland, OH, US' to '207.68.183.32'
1 fe0-1-0-202-100M.ar1.cle1.gblx.net (64.214.8.97) 0.657 ms 0.495 ms
2 so1-0-0-2488M.ar4.SEA1.gblx.net (67.17.71.210) 75.493 ms 74.653 ms
3 MSN-Hot-Mail-2.ge-4-0-0.br2.SEA1.gblx.net (64.208.170.206) 106.401n-2.ar4.SEA1.gblx.net ms 64.215.195.86 ms
4 ge-1-3-0-57.wst-64cb-1b.ntwk.msn.net (207.46.36.249) 76.472 ms 74.496 ms
5 ge-6-1-0-0.tuk-64cb-1b.ntwk.msn.net (207.46.35.33) 78.648 ms 71.424 ms
6 ten2-4.tuk-76c-1b.ntwk.msn.net (207.46.44.54) 246.245 ms 75.232 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.