Tracing from my PC

Tracing from my own computer to the Curtin server (in Perth? because technically, it could be anywhere in the world), I can see 192.168.2.1 which is my wireless router, but everything else is way over my head..

C:\Users\Nagamori>tracert 134.7.179.53

Tracing route to 134.7.179.53 over a maximum of 30 hops

1 2 ms 2 ms 1 ms 192.168.2.1
2 10 ms 9 ms 9 ms 10.62.0.1
3 11 ms 9 ms 13 ms riv4-ge1-1.gw.optusnet.com.au [198.142.160.125]
4 83 ms 76 ms 89 ms mas3-ge11-0-0-821.gw.optusnet.com.au [211.29.156.11]
5 24 ms 33 ms 24 ms sun1-ge12-0-0-811.gw.optusnet.com.au [211.29.155.13]
6 23 ms 23 ms 23 ms sun4-unk8-1.gw.optusnet.com.au [198.142.160.226]
7 112 ms 77 ms 24 ms 61.88.144.161
8 86 ms 73 ms 93 ms 61.88.226.115
9 198 ms 181 ms 137 ms AARNET.o6ssc76fe.optus.net.au [61.88.166.134]
10 71 ms 69 ms 71 ms ge-1-0-3.bb1.b.per.aarnet.net.au [202.158.198.6]
11 252 ms 210 ms 219 ms gigabitethernet0.er1.curtin.cpe.aarnet.net.au [202.158.198.178]
12 69 ms 69 ms 73 ms gw1.er1.curtin.cpe.aarnet.net.au [202.158.198.186]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 73 ms 71 ms 71 ms 134.7.179.53

Trace complete.

C:\Users\Nagamori>ping centralops.net

Pinging centralops.net [70.84.211.98] with 32 bytes of data:
Reply from 70.84.211.98: bytes=32 time=319ms TTL=112
Reply from 70.84.211.98: bytes=32 time=466ms TTL=112
Reply from 70.84.211.98: bytes=32 time=682ms TTL=112
Reply from 70.84.211.98: bytes=32 time=419ms TTL=112

Ping statistics for 70.84.211.98:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 319ms, Maximum = 682ms, Average = 471ms

C:\Users\Nagamori>ping curtin.edu.au

Pinging curtin.edu.au [134.7.179.53] with 32 bytes of data:
Reply from 134.7.179.53: bytes=32 time=796ms TTL=114
Reply from 134.7.179.53: bytes=32 time=773ms TTL=114
Reply from 134.7.179.53: bytes=32 time=756ms TTL=114
Reply from 134.7.179.53: bytes=32 time=573ms TTL=114

Ping statistics for 134.7.179.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 573ms, Maximum = 796ms, Average = 724ms

C:\Users\Nagamori>ping curtin.edu.au

Pinging curtin.edu.au [134.7.179.53] with 32 bytes of data:
Reply from 134.7.179.53: bytes=32 time=604ms TTL=114
Reply from 134.7.179.53: bytes=32 time=434ms TTL=114
Reply from 134.7.179.53: bytes=32 time=551ms TTL=114
Reply from 134.7.179.53: bytes=32 time=326ms TTL=114

Ping statistics for 134.7.179.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 326ms, Maximum = 604ms, Average = 478ms

C:\Users\Nagamori>ping centralops.net

Pinging centralops.net [70.84.211.98] with 32 bytes of data:
Reply from 70.84.211.98: bytes=32 time=870ms TTL=112
Reply from 70.84.211.98: bytes=32 time=791ms TTL=112
Reply from 70.84.211.98: bytes=32 time=795ms TTL=112
Reply from 70.84.211.98: bytes=32 time=806ms TTL=112

Ping statistics for 70.84.211.98:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 791ms, Maximum = 870ms, Average = 815ms

C:\Users\Nagamori>ping centralops.net

Pinging centralops.net [70.84.211.98] with 32 bytes of data:
Reply from 70.84.211.98: bytes=32 time=232ms TTL=112
Reply from 70.84.211.98: bytes=32 time=216ms TTL=112
Reply from 70.84.211.98: bytes=32 time=215ms TTL=112
Reply from 70.84.211.98: bytes=32 time=214ms TTL=112

Ping statistics for 70.84.211.98:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 214ms, Maximum = 232ms, Average = 219ms

C:\Users\Nagamori>ping centralops.net

Pinging centralops.net [70.84.211.98] with 32 bytes of data:
Reply from 70.84.211.98: bytes=32 time=254ms TTL=112
Reply from 70.84.211.98: bytes=32 time=227ms TTL=112
Reply from 70.84.211.98: bytes=32 time=214ms TTL=112
Reply from 70.84.211.98: bytes=32 time=215ms TTL=112

Ping statistics for 70.84.211.98:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 214ms, Maximum = 254ms, Average = 227ms

C:\Users\Nagamori>ping curtin.edu.au

Pinging curtin.edu.au [134.7.179.53] with 32 bytes of data:
Reply from 134.7.179.53: bytes=32 time=73ms TTL=114
Reply from 134.7.179.53: bytes=32 time=134ms TTL=114
Reply from 134.7.179.53: bytes=32 time=142ms TTL=114
Reply from 134.7.179.53: bytes=32 time=71ms TTL=114

Ping statistics for 134.7.179.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 142ms, Average = 105ms

C:\Users\Nagamori>ping curtin.edu.au

Pinging curtin.edu.au [134.7.179.53] with 32 bytes of data:
Reply from 134.7.179.53: bytes=32 time=70ms TTL=114
Reply from 134.7.179.53: bytes=32 time=76ms TTL=114
Reply from 134.7.179.53: bytes=32 time=75ms TTL=114
Reply from 134.7.179.53: bytes=32 time=72ms TTL=114

Ping statistics for 134.7.179.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 76ms, Average = 73ms

C:\Users\Nagamori>ping centralops.net

Pinging centralops.net [70.84.211.98] with 32 bytes of data:
Reply from 70.84.211.98: bytes=32 time=216ms TTL=112
Reply from 70.84.211.98: bytes=32 time=284ms TTL=112
Reply from 70.84.211.98: bytes=32 time=218ms TTL=112
Reply from 70.84.211.98: bytes=32 time=214ms TTL=112

Ping statistics for 70.84.211.98:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 214ms, Maximum = 284ms, Average = 233ms

Funnily enough, the first few pings to Central Ops were 471ms and to Curtin it was 724ms and I was thinking that the Curtin server is in Australia, so it should definitely be faster from here(Sydney) to Perth, than it is from Sydney to Texas.

After a few pings, a faster route is found and Curtin settles to 73ms and Central Ops to 233ms.