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 '60.28.14.220'


     1 fe0-1-0-202-100M.ar1.cle1.gblx.net (64.214.8.97) 0.659 ms 0.457 ms
     2 te2-1-10g.ar5.NYC1.gblx.net (67.17.108.242) 12.115 ms 12.094 ms
     3 sprint-1.ar3.NYC1.gblx.net (208.51.134.26) 12.201 ms 11.952 ms
     4 sl-bb23-pen-12-0.sprintlink.net (144.232.20.95) 18.839 ms 19.184 ms
     5 sl-bb24-pen-9-0.sprintlink.net (144.232.16.66) 18.712 ms 18.799 ms
     6 sl-bb25-pen-14-0.sprintlink.net (144.232.16.78) 19.035 ms 18.960 ms
     7 sl-crs1-stk-0-4-0-3.sprintlink.net (144.232.18.151) 71.130 ms 71.223 ms
     8 sl-bb20-sj-2-0.sprintlink.net (144.232.18.150) 70.224 ms 70.285 ms
     9 sl-st20-sj-0-0.sprintlink.net (144.232.18.106) 70.546 ms 70.716 ms
     10 sl-china6-2-0.sprintlink.net (144.223.242.70) 231.253 ms 231.374 ms
     11 219.158.25.53 (219.158.25.53) 231.496 ms 232.918 ms
     12 219.158.4.158 (219.158.4.158) 258.244 ms 258.133 ms
     13 219.158.7.253 (219.158.7.253) 272.378 ms 272.298 ms
     14 219.158.7.254 (219.158.7.254) 283.208 ms 283.245 ms
     15 202.99.66.170 (202.99.66.170) 283.342 ms 283.232 ms
     16 60.28.31.126 (60.28.31.126) 283.435 ms 283.337 ms
     17 60.28.31.106 (60.28.31.106) 283.832 ms 283.768 ms
     18 60.28.253.254 (60.28.253.254) 284.183 ms 321.929 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.