Posted 18 June 2015 - 11:20 AM

C:\>ping 103.9.100.1 -n 20 -l 256 Pinging 103.9.100.1 with 256 bytes of data: Reply from 103.9.100.1: bytes=256 time=191ms TTL=56 Reply from 103.9.100.1: bytes=256 time=192ms TTL=56 Reply from 103.9.100.1: bytes=256 time=199ms TTL=56 Reply from 103.9.100.1: bytes=256 time=197ms TTL=56 Reply from 103.9.100.1: bytes=256 time=195ms TTL=56 Reply from 103.9.100.1: bytes=256 time=194ms TTL=56 Reply from 103.9.100.1: bytes=256 time=193ms TTL=56 Reply from 103.9.100.1: bytes=256 time=196ms TTL=56 Reply from 103.9.100.1: bytes=256 time=194ms TTL=56 Reply from 103.9.100.1: bytes=256 time=197ms TTL=56 Reply from 103.9.100.1: bytes=256 time=207ms TTL=56 Reply from 103.9.100.1: bytes=256 time=205ms TTL=56 Reply from 103.9.100.1: bytes=256 time=194ms TTL=56 Reply from 103.9.100.1: bytes=256 time=192ms TTL=56 Reply from 103.9.100.1: bytes=256 time=191ms TTL=56 Reply from 103.9.100.1: bytes=256 time=199ms TTL=56 Reply from 103.9.100.1: bytes=256 time=197ms TTL=56 Reply from 103.9.100.1: bytes=256 time=195ms TTL=56 Reply from 103.9.100.1: bytes=256 time=193ms TTL=56 Reply from 103.9.100.1: bytes=256 time=191ms TTL=56 Ping statistics for 103.9.100.1: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 191ms, Maximum = 207ms, Average = 195ms C:\>ping 203.175.175.203 -n 20 -l 256 Pinging 203.175.175.203 with 256 bytes of data: Reply from 203.175.175.203: bytes=256 time=263ms TTL=52 Reply from 203.175.175.203: bytes=256 time=265ms TTL=52 Reply from 203.175.175.203: bytes=256 time=279ms TTL=52 Reply from 203.175.175.203: bytes=256 time=271ms TTL=52 Reply from 203.175.175.203: bytes=256 time=269ms TTL=52 Reply from 203.175.175.203: bytes=256 time=274ms TTL=52 Reply from 203.175.175.203: bytes=256 time=272ms TTL=52 Reply from 203.175.175.203: bytes=256 time=270ms TTL=52 Reply from 203.175.175.203: bytes=256 time=268ms TTL=52 Reply from 203.175.175.203: bytes=256 time=270ms TTL=52 Reply from 203.175.175.203: bytes=256 time=275ms TTL=52 Reply from 203.175.175.203: bytes=256 time=272ms TTL=52 Reply from 203.175.175.203: bytes=256 time=267ms TTL=52 Reply from 203.175.175.203: bytes=256 time=265ms TTL=52 Reply from 203.175.175.203: bytes=256 time=270ms TTL=52 Reply from 203.175.175.203: bytes=256 time=266ms TTL=52 Reply from 203.175.175.203: bytes=256 time=273ms TTL=52 Reply from 203.175.175.203: bytes=256 time=274ms TTL=52 Reply from 203.175.175.203: bytes=256 time=269ms TTL=52 Reply from 203.175.175.203: bytes=256 time=273ms TTL=52 Ping statistics for 203.175.175.203: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 263ms, Maximum = 279ms, Average = 270ms C:\Users\me>tracert 103.9.100.1 Tracing route to tl1.sg.vodien.com [103.9.100.1] over a maximum of 30 hops: 1 6 ms 9 ms 2 ms 192.168.x.x 2 19 ms 19 ms 18 ms x.x.x.x 3 17 ms 18 ms 19 ms x.x.x.x 4 34 ms 29 ms 49 ms x.x.x.x 5 37 ms 36 ms 31 ms x.la.cox.net [68.1.x.x] 6 36 ms 36 ms 31 ms 68.x.x.x 7 200 ms 198 ms 195 ms TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82] 8 198 ms 205 ms 192 ms TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82] 9 199 ms 199 ms 198 ms 63-218-213-182.static.pccwglobal.net [63.218.213.182] 10 195 ms 195 ms 196 ms 73.168.22.103.in-addr.arpa [103.22.168.73] 11 194 ms 198 ms 199 ms tl1.sg.vodien.com [103.9.100.1] Trace complete. C:\Users\me>tracert 203.175.175.203 Tracing route to dns.sg.gs [203.175.175.203] over a maximum of 30 hops: 1 3 ms 8 ms 9 ms 192.168.x.x 2 11 ms 19 ms 20 ms x.x.x.x 3 19 ms 18 ms 19 ms x.x.x.x 4 38 ms 23 ms 34 ms x.x.x.x 5 23 ms 28 ms 29 ms x.Level3.net [x.x.x.x] 6 27 ms 29 ms 28 ms x.LosAngeles6.Level3.net [4.69.x.x] 7 39 ms 28 ms * x.LosAngeles6.Level3.net [4.69.x.x] 8 36 ms 30 ms 29 ms x.losangeles6.level3.net [4.68.x.x] 9 27 ms 24 ms 23 ms x.LVW-Los-Angeles.as6453.net [66.110.x.x] 10 31 ms 28 ms 39 ms 63.x.x.x 11 197 ms 41 ms 36 ms core-1.v30.lax1.sg.gs [124.6.40.21] 12 189 ms 179 ms 238 ms core-1.v54.hk1.sg.gs [103.14.244.102] 13 279 ms 278 ms 278 ms core-1.v52.sg3.sg.gs [103.14.244.98] 14 270 ms 269 ms 265 ms core-1.v41.sg1.sg.gs [203.175.175.129] 15 274 ms 268 ms 278 ms dns.sg.gs [203.175.175.203] Trace complete.

I will try to remember to do it again tonight during primetime Pacific Time, which is when it would really matter, rather than now in the middle of the day.Right now, the first IP has much better ping and less hops than the second one. Cox broadband, south western US, Pacific Timezone.

Edited by jay35, 18 June 2015 - 11:22 AM.