Tuesday, May 22, 2007 - 10:03 am, by: Peter Nitschke(Pen)
Some hops timing out is normal, as some routers don't respond to trace route. It's slow hops that we are looking for.
Example, this is a trace run from a Telstra server in Melbourne, which has a few non-responding hops, but there aren't any slow hops.
traceroute to www.soarercentral.com (203.56.204.10), 30 hops max, 40 byte packets 1 vlan250.lon-service6.Melbourne.telstra.net (203.50.2.177) 0.509 ms 0.291 ms 0.321 ms 2 GigabitEthernet11-0.lon-core3.Melbourne.telstra.net (203.50.80.1) 0.293 ms 0.296 ms 0.209 ms 3 TenGigE0-12-0-2.exi-core1.Melbourne.telstra.net (203.50.6.137) 3.092 ms 1.418 ms 2.331 ms 4 POS0-0-0-0.way-core4.Adelaide.telstra.net (203.50.6.190) 15.643 ms 15.446 ms 15.421 ms 5 GigabitEthernet0-1.way27.Adelaide.telstra.net (203.50.120.37) 12.805 ms 13.059 ms 12.971 ms 6 optus3.lnk.telstra.net (139.130.237.10) 13.652 ms 13.559 ms 13.084 ms 7 61.88.221.201 (61.88.221.201) 14.145 ms 13.865 ms 14.447 ms 8 61.88.221.201 (61.88.221.201) 13.655 ms 14.592 ms 14.551 ms 9 * * * 10 gi5-1.cor3.adl2.internode.on.net (203.16.212.155) 15.273 ms 15.611 ms 14.914 ms 11 fa0-0.rtr7.adl2.internode.on.net (203.16.215.87) 16.206 ms 15.911 ms 16.133 ms 12 * * * 13 web.ace.net.au (203.56.204.10) 37.076 ms 37.788 ms 36.423 ms