Traceroute and Pinging made easy

I used Central Ops.net to get my tools for this exercise and found the traceroute tool worked easily and recorded 19 'hops', I used the 'Ping' tool on the same site to establish a time of 267 milliseconds to the Curtin server. On checking back to the "hops' cut and paste page, I noticed that the answer was also on the last line. I enjoyed this exercise and felt it gave me a greater understanding of these Internet tools.

Tracing route to curtin.edu.au [134.7.179.56]...
hop rtt rtt rtt ip address fully qualified domain name
1 4 1 0 70.84.211.97 61.d3.5446.static.theplanet.com
2 0 0 0 70.87.254.1 po101.dsr01.dllstx5.theplanet.com
3 0 0 0 70.85.127.105 po51.dsr01.dllstx3.theplanet.com
4 0 0 0 70.87.253.9 et3-1.ibr04.dllstx3.theplanet.com
5 * * *
6 41 41 47 72.52.92.57 10gigabitethernet1-2.core1.lax1.he.net
7 43 49 49 72.52.92.21 10gigabitethernet1-3.core1.pao1.he.net
8 41 41 41 72.52.92.70 10gigabitethernet4-1.core1.sjc2.he.net
9 44 43 43 216.218.192.234
10 161 161 161 202.147.0.58 gi1-0-0.cr2.nrt1.asianetcom.net
11 241 244 241 202.147.32.93 po5-0.gw3.sin1.asianetcom.net
12 266 266 266 202.147.33.174 aar-0002.gw3.sin1.asianetcom.net
13 266 265 266 202.158.194.145 so-3-2-0.bb1.a.per.aarnet.net.au
14 266 266 266 202.158.198.178 gigabitethernet0.er1.curtin.cpe.aarnet.net.au
15 266 266 266 202.158.198.186 gw1.er1.curtin.cpe.aarnet.net.au
16 * * *
17 * * *
18 * * *
19 267 267 267 134.7.179.56 systems.curtin.edu.au