Tests

Traceroute.pl  stops after 4 hops

Below is an example:

Traceroute,pl form

Traceroute.pl from browser, stops after 4 hops

Raw traceroute from command line

Pingserver working



After a lot of testing changing the number of queries per hop (-q), the timeout on queries (-w), the first hop to start at (-f), the maximum number of hops (-m) and turning off name resolution, this was found to be due to name resolution, i.e. using the -n option to turn off name resolution it went much faster and completed 30 hops. The name resolution was slow since one of the name servers was down causing timeouts. After disabling the use of the non working name server the execution was about 60 times faster. Results from the testing are shown in the spreadsheet here .