Tracing, the stuff you hear about in movies

Trace Route from local computer

the trace route was completed using the tracert command in the command prompt
Tracing route to systems.curtin.edu.au [134.7.179.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms 10.1.1.1
3 25 ms 24 ms 27 ms sun19.ba.optusnet.com.au [198.142.129.39]
4 25 ms 24 ms 24 ms sun4-vl420.gw.optusnet.com.au [211.31.131.2]
5 25 ms 25 ms 25 ms ge1-25.33vsc76me1.optus.net.au [61.88.144.161]
6 82 ms 82 ms 82 ms 61.88.226.113
7 82 ms 82 ms 82 ms AARNET.o6ssc76fe.optus.net.au [61.88.166.134]
8 83 ms 82 ms 83 ms ge-1-0-3.bb1.b.per.aarnet.net.au [202.158.198.6]

9 82 ms 81 ms 82 ms gigabitethernet0.er1.curtin.cpe.aarnet.net.au [2
02.158.198.178]
10 82 ms 83 ms 82 ms gw1.er1.curtin.cpe.aarnet.net.au [202.158.198.18
6]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 84 ms 85 ms 83 ms systems.curtin.edu.au [134.7.179.56]

Trace complete.
The number of hops was 2 less then the number of hops from the net tools site. The average hop time is much less with a maximum hop time being 85ms. And as you can see with the addresses all of them are end with the .au suffix meaning they are Australian servers. So as expected the trace route was quicker and less hops, and thus the ping was lower.