83 replies to this topic

[Mike Forst]

I am researching datacenters in the APAC/Oceanic region. I could use some help from the players in that region to help me compare the latency and connection quality to some providers in the region. It would also be helpful to gather some data from players on the West coast of the United States and Canada. If you are interested in helping me, I need you to do the following:

• ping and traceroute (MTR preferable if you know how) to the following IP addresses: 103.9.100.1, 203.175.175.203
  
• your rough geographic location
  
• your internet service provider

I understand you may not wish to share this information publicly for all to see on this forum. If you are concerned about that, please feel free to PM me the information instead.

[Rashkae]

Geographic location: Singapore
ISP: ViewQwest

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=2ms TTL=60
Reply from 103.9.100.1: bytes=32 time=2ms TTL=60
Reply from 103.9.100.1: bytes=32 time=2ms TTL=60
Reply from 103.9.100.1: bytes=32 time=2ms TTL=60

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

tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 2 ms 2 ms 2 ms tl1.sg.vodien.com [103.9.100.1]





ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=1ms TTL=58
Reply from 203.175.175.203: bytes=32 time=1ms TTL=58
Reply from 203.175.175.203: bytes=32 time=1ms TTL=58
Reply from 203.175.175.203: bytes=32 time=1ms TTL=58

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

tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 1 ms 1 ms 1 ms dns.sg.gs [203.175.175.203]

[Shae Starfyre]

North Eastern, PA; USA
Verizon; DSL (Up 0.83mb/Down 8.51mb)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
tracert 103.9.100.1
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms VERIZONDRIVE [192.168.1.1]
2 142 ms 24 ms 25 ms 10.29.43.1
3 30 ms 26 ms 27 ms G0-0-4-5.SCTNPA-LCR-22.verizon-gni.net [100.41.2
23.224]
4 * * * Request timed out.
5 35 ms 37 ms 35 ms 0.ae8.BR2.NYC4.ALTER.NET [140.222.229.77]
6 36 ms 36 ms 37 ms 204.255.168.174
7 296 ms 296 ms 297 ms if-5-5.tcore1.NYY-New-York.as6453.net [216.6.90.
5]
8 281 ms 281 ms 280 ms if-1-2.tcore1.PDI-Palo-Alto.as6453.net [66.198.1
27.5]
9 279 ms 279 ms 280 ms if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.1
27.2]
10 281 ms 282 ms 280 ms if-9-2.tcore1.TV2-Tokyo.as6453.net [180.87.180.1
8]
11 283 ms 286 ms 282 ms if-2-2.tcore2.TV2-Tokyo.as6453.net [180.87.180.2
]
12 281 ms 280 ms 280 ms if-6-2.tcore1.SVW-Singapore.as6453.net [180.87.1
2.109]
13 279 ms 280 ms 279 ms if-2-2.tcore2.SVW-Singapore.as6453.net [180.87.1
2.2]
14 284 ms 284 ms 284 ms if-20-2.tcore1.SVQ-Singapore.as6453.net [180.87.
96.21]
15 287 ms 287 ms 287 ms 180.87.96.2
16 287 ms 287 ms 287 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
17 288 ms 287 ms 287 ms tl1.sg.vodien.com [103.9.100.1]
Trace complete.
ping 103.9.100.1
Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=287ms TTL=57
Reply from 103.9.100.1: bytes=32 time=288ms TTL=57
Reply from 103.9.100.1: bytes=32 time=289ms TTL=57
Reply from 103.9.100.1: bytes=32 time=288ms TTL=57
Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 287ms, Maximum = 289ms, Average = 288ms
tracert 203.175.175.203
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms VERIZONDRIVE [192.168.1.1]
2 25 ms 26 ms 25 ms 10.29.43.1
3 29 ms 33 ms 27 ms G0-0-4-5.SCTNPA-LCR-22.verizon-gni.net [100.41.2
23.224]
4 * * * Request timed out.
5 46 ms 35 ms 35 ms 0.ae8.BR2.NYC4.ALTER.NET [140.222.229.77]
6 36 ms 35 ms 35 ms 204.255.168.174
7 36 ms 35 ms 36 ms 63.243.128.122
8 40 ms 40 ms 40 ms 66.110.96.34
9 85 ms 49 ms 50 ms core-1.v30.nyc1.sg.gs [124.6.44.21]
10 122 ms 122 ms 124 ms core-1.v55.lax1.sg.gs [103.14.244.104]
11 267 ms 308 ms 271 ms core-1.v54.hk1.sg.gs [103.14.244.102]
12 289 ms 288 ms 289 ms core-1.v52.sg3.sg.gs [103.14.244.98]
13 284 ms 283 ms 284 ms core-1.v41.sg1.sg.gs [203.175.175.129]
14 295 ms 287 ms 296 ms dns.sg.gs [203.175.175.203]
Trace complete.
ping 203.175.175.203
Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=285ms TTL=53
Reply from 203.175.175.203: bytes=32 time=285ms TTL=53
Reply from 203.175.175.203: bytes=32 time=288ms TTL=53
Reply from 203.175.175.203: bytes=32 time=297ms TTL=53
Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 285ms, Maximum = 297ms, Average = 288ms

[Jay Z]

Location: Townsville, North Queensland, 'straya
ISP: Telstra (for now)

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Jay Z>tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms telstra.gateway [10.0.0.138]
2 40 ms 19 ms 19 ms 58.162.26.1
3 19 ms 18 ms 19 ms 144.130.212.209
4 21 ms 22 ms 22 ms bundle-ether5.woo-core1.brisbane.telstra.net [20
3.50.11.136]
5 33 ms 33 ms 32 ms bundle-ether11.chw-core10.sydney.telstra.net [20
3.50.11.70]
6 47 ms 46 ms 47 ms bundle-ether8.exi-core10.melbourne.telstra.net [
203.50.11.125]
7 61 ms 61 ms 59 ms bundle-ether5.way-core4.adelaide.telstra.net [20
3.50.11.92]
8 94 ms 94 ms 91 ms bundle-ether5.pie-core1.perth.telstra.net [203.5
0.11.17]
9 90 ms 90 ms 90 ms 203.50.9.2
10 140 ms 142 ms 142 ms 202.84.143.181
11 142 ms 142 ms 140 ms 202.84.243.82
12 139 ms 139 ms 140 ms 203.116.5.157
13 141 ms 139 ms 140 ms 203.118.15.186
14 140 ms 140 ms 139 ms an-ats-int11.starhub.net.sg [203.118.15.110]
15 141 ms 140 ms 140 ms sh2.eqx1.sg.vodien.com [203.116.246.18]
16 142 ms 141 ms 141 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

C:\Users\Jay Z>ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=141ms TTL=48
Reply from 103.9.100.1: bytes=32 time=141ms TTL=48
Reply from 103.9.100.1: bytes=32 time=141ms TTL=48
Reply from 103.9.100.1: bytes=32 time=141ms TTL=48

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

C:\Users\Jay Z>tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms telstra.gateway [10.0.0.138]
2 19 ms 18 ms 18 ms 58.162.26.1
3 19 ms 18 ms 19 ms 144.130.212.209
4 21 ms 18 ms 19 ms bundle-ether5.woo-core1.brisbane.telstra.net [20
3.50.11.136]
5 31 ms 33 ms 33 ms bundle-ether11.chw-core10.sydney.telstra.net [20
3.50.11.70]
6 45 ms 47 ms 45 ms bundle-ether8.exi-core10.melbourne.telstra.net [
203.50.11.125]
7 62 ms 62 ms 62 ms bundle-ether5.way-core4.adelaide.telstra.net [20
3.50.11.92]
8 91 ms 90 ms 90 ms bundle-ether5.pie-core1.perth.telstra.net [203.5
0.11.17]
9 90 ms 90 ms 90 ms tengige0-0-1-0.pthp-core01.perth.net.reach.com [
203.50.13.250]
10 141 ms 141 ms 142 ms 202.84.143.2
11 142 ms 143 ms 145 ms 202.84.243.82
12 140 ms 140 ms 140 ms 203.116.5.157
13 140 ms 140 ms 140 ms 203.118.15.186
14 140 ms 140 ms 140 ms an-ats-loc11.starhub.net.sg [203.118.15.238]
15 140 ms 140 ms 140 ms starhub-sg.sg.gs [203.116.39.138]
16 143 ms 141 ms 141 ms core-1.v31.sg1.sg.gs [203.175.175.21]
17 140 ms 140 ms 140 ms dns.sg.gs [203.175.175.203]

Trace complete.

C:\Users\Jay Z>ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=140ms TTL=47
Reply from 203.175.175.203: bytes=32 time=140ms TTL=47
Reply from 203.175.175.203: bytes=32 time=140ms TTL=47
Reply from 203.175.175.203: bytes=32 time=140ms TTL=47

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

-----------------------------------------------------------------------
So ~140ms for me. Pretty much current Euro ping.

[jay35]

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.

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.

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

[Elizander]

Philippines (Luzon). Smart Prepaid Mobile Internet (taken during off-peak hours)

Edited by Elizander, 18 June 2015 - 12:07 PM.

[Kageru Ikazuchi]

Location: Near Tokyo, ISP: J:Com

Wall of useful stuff in spoiler ...

Spoiler

C:\Windows\system32>ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=91ms TTL=53
Request timed out.
Reply from 103.9.100.1: bytes=32 time=94ms TTL=53
Reply from 103.9.100.1: bytes=32 time=93ms TTL=53

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 94ms, Average = 92ms

C:\Windows\system32>ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=84ms TTL=48
Reply from 203.175.175.203: bytes=32 time=107ms TTL=48
Reply from 203.175.175.203: bytes=32 time=102ms TTL=48
Reply from 203.175.175.203: bytes=32 time=111ms TTL=48

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 111ms, Average = 101ms

C:\Windows\system32>tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 1 ms <1 ms 2 ms 192.168.1.1
2 15 ms 11 ms 15 ms 61-23-116-1.rev.home.ne.jp [61.23.116.1]
3 21 ms 9 ms 13 ms 10.202.115.3
4 24 ms 18 ms 13 ms 10.1.0.45
5 33 ms 17 ms 14 ms 203-165-18-245.rev.home.ne.jp [203.165.18.245]
6 18 ms 18 ms 18 ms c1-t0-0-0-1.ot-dc.zaq.ad.jp [203.165.18.246]
7 22 ms 18 ms 18 ms gw1-t0-4-0-0.ot-dc.zaq.ad.jp [61.26.74.90]
8 17 ms 18 ms 20 ms Te2-4.gw2.nrt2.asianetcom.net [203.192.150.237]
9 20 ms 16 ms 14 ms gi15-0-0.cr2.nrt1.asianetcom.net [202.147.0.82]
10 104 ms 101 ms 100 ms gi1-0-0.gw5.sin1.asianetcom.net [61.14.157.110]
11 100 ms 100 ms 98 ms ip-202-147-32-139.asianetcom.net [202.147.32.139]
12 98 ms 99 ms 97 ms 203.118.15.241
13 96 ms 98 ms 100 ms 203.118.2.30
14 98 ms 101 ms 100 ms an-atl-loc11.starhub.net.sg [203.118.15.178]
15 98 ms 97 ms 96 ms sh1.eqx1.sg.vodien.com [203.116.246.30]
16 148 ms 93 ms 93 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

C:\Windows\system32>tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 20 ms 11 ms 61-23-116-1.rev.home.ne.jp [61.23.116.1]
3 17 ms 20 ms 14 ms 10.202.99.3
4 18 ms 22 ms 18 ms 10.1.0.45
5 20 ms 22 ms 18 ms 203-165-18-137.rev.home.ne.jp [203.165.18.137]
6 16 ms 23 ms 37 ms c1-t0-4-0-3.ot-dc.zaq.ad.jp [203.165.18.138]
7 22 ms 19 ms 17 ms gw2-t0-5-0-0.ot-dc.zaq.ad.jp [61.26.74.162]
8 15 ms 17 ms 18 ms 210.138.70.37
9 18 ms 20 ms 18 ms tky009bf00.IIJ.Net [58.138.82.97]
10 15 ms 19 ms 17 ms tky001ix11.IIJ.Net [58.138.83.110]
11 18 ms 18 ms 18 ms 210.173.174.65
12 17 ms 19 ms 20 ms ae-13.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.3.240]
13 88 ms 82 ms 82 ms ae-3.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.35]
14 84 ms 85 ms 83 ms xe-4-1-0.r00.sngpsi03.sg.bb.gin.ntt.net [129.250.6.123]
15 92 ms 85 ms 82 ms ntt-sg.sg.gs [116.51.23.66]
16 87 ms 83 ms 83 ms core-2.v32.sg1.sg.gs [203.175.175.30]
17 85 ms 83 ms 108 ms dns.sg.gs [203.175.175.203]

Trace complete.

C:\Windows\system32>

[Wild_Alaskan]

Juneau, Alaska - Alaska Communications Services

C:\Users\Will>tracert 103.9.100.1
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
  1	<1 ms	<1 ms	<1 ms  192.168.1.1
  2	12 ms	11 ms	12 ms  br1.stl.acsalaska.net [209.193.63.235]
  3	12 ms	11 ms	12 ms  ae8-2000-mx1.stl.acsalaska.net [63.140.116.226]
  4	41 ms	42 ms	43 ms  xe-2-1-0-r2.sea.acsalaska.net [63.140.116.130]
  5	41 ms	42 ms	41 ms  xe-8-2-2.edge1.Seattle3.Level3.net [4.59.232.61]
  6	46 ms	41 ms	 *	 ae-2-52.edge2.Seattle1.Level3.net [4.69.147.168]
  7	42 ms	42 ms	43 ms  PCCW-GLOBAL.edge2.Seattle1.Level3.net [4.31.99.2
6]
  8   231 ms   230 ms   230 ms  TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82]
  9   231 ms   230 ms   230 ms  TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82]
10   224 ms   224 ms   225 ms  63-218-213-182.static.pccwglobal.net [63.218.213
.182]
11   224 ms   224 ms   223 ms  73.168.22.103.in-addr.arpa [103.22.168.73]
12   221 ms   221 ms   221 ms  tl1.sg.vodien.com [103.9.100.1]
Trace complete.
C:\Users\Will>ping 103.9.100.1
Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=220ms TTL=51
Reply from 103.9.100.1: bytes=32 time=221ms TTL=51
Reply from 103.9.100.1: bytes=32 time=222ms TTL=51
Reply from 103.9.100.1: bytes=32 time=220ms TTL=51
Ping statistics for 103.9.100.1:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 220ms, Maximum = 222ms, Average = 220ms
C:\Users\Will>tracert 203.175.175.203
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
  1	<1 ms	<1 ms	<1 ms  192.168.1.1
  2	11 ms	12 ms	12 ms  br1.stl.acsalaska.net [209.193.63.235]
  3	12 ms	20 ms	12 ms  ae8-2000-mx1.stl.acsalaska.net [63.140.116.226]
  4	44 ms	44 ms	44 ms  xe-2-1-0-r2.sea.acsalaska.net [63.140.116.130]
  5	45 ms	48 ms	44 ms  xe-1-0-0-r2.pdx.acsalaska.net [63.140.116.123]
  6	45 ms	44 ms	46 ms  10ge1-2.core1.pdx1.he.net [65.19.191.97]
  7	66 ms	60 ms	64 ms  10ge12-7.core1.pao1.he.net [184.105.222.25]
  8	61 ms	72 ms	60 ms  10ge3-1.core1.sjc2.he.net [72.52.92.70]
  9	85 ms	80 ms   123 ms  10ge13-3.core1.lax2.he.net [184.105.213.5]
10	69 ms	69 ms   159 ms  any2ix.coresite.com [206.72.211.16]
11	81 ms	81 ms   103 ms  core-1.v30.lax1.sg.gs [124.6.40.21]
12   222 ms   225 ms   221 ms  core-1.v54.hk1.sg.gs [103.14.244.102]
13   306 ms   306 ms   307 ms  core-1.v53.sg3.sg.gs [103.14.244.100]
14   306 ms   307 ms   306 ms  core-2.v41.sg1.sg.gs [203.175.175.130]
15   306 ms   306 ms   306 ms  dns.sg.gs [203.175.175.203]
Trace complete.
C:\Users\Will>ping 203.175.175.203
Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=305ms TTL=49
Reply from 203.175.175.203: bytes=32 time=306ms TTL=49
Reply from 203.175.175.203: bytes=32 time=307ms TTL=49
Reply from 203.175.175.203: bytes=32 time=306ms TTL=49
Ping statistics for 203.175.175.203:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 305ms, Maximum = 307ms, Average = 306ms

[SneakyNZ]

Location: New Zealand (Auckland)
ISP: Bigpipe (Fiber 200/200Mbps)

Basically shaved off 40ms (103.9.100.1) on and 10ms (203.175.175.203) off my average latency on the American servers (200-210ms). Still not great for competitive with the Aussie crowd, you'd want less than 50ms not 160ms.

I've also saved the results to google drive for easier reading given it jumbled it up below:
https://drive.google...iew?usp=sharing

103.9.100.1 MTR
 
|------------------------------------------------------------------------------------------|
|									  WinMTR statistics								   |
|					   Host			  -						 %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| g1-3-3-548.akcr10.global-gateway.net.nz -	0 |  100 |  100 |	0  |	1  |	9  |	0  |
|		 ae6-10.akbr7.global-gateway.net.nz -	2 |   97  |   96  |	1  |	1  |	1  |	1  |
|		 xe7-0-2.sgbr3.global-gateway.net.nz -   0 |  100 |  100 |   25 |   25 |   26 |   25 |
|	  ae2-10.sgbr4.global-gateway.net.nz -	   0 |  100 |  100 |   25 |   25 |   31 |   25 |
|	 ae-3.a04.sydnau03.au.ra.gin.ntt.net -		0 |  100 |  100 |   26 |   26 |   28 |   26 |
|	 ae-3.r05.sydnau01.au.bb.gin.ntt.net -		0 |  100 |  100 |   25 |   26 |   43 |   26 |
|	 ae-8.r20.tokyjp05.jp.bb.gin.ntt.net -		   0 |  100 |  100 |  137 |  139 |  152 |  138 |
|	ae-15.r01.tokyjp01.jp.bb.gin.ntt.net -		  0 |  100 |  100 |  138 |  138 |  139 |  138 |
|						  61.213.145.202 -				  0 |  100 |  100 |  164 |  165 |  171 |  164 |
|						  203.118.15.186 -				  0 |  100 |  100 |  255 |  255 |  257 |  256 |
|			 an-ats-int11.starhub.net.sg -			 0 |  100 |  100 |  287 |  288 |  289 |  288 |
|				  sh2.eqx1.sg.vodien.com -			0 |  100 |  100 |  290 |  290 |  303 |  290 |
|					   tl1.sg.vodien.com -				  0 |  100 |  100 |  164 |  165 |  178 |  165 |
 

203.175.175.203 MTR
|------------------------------------------------------------------------------------------|
|									  WinMTR statistics								   |
|					   Host			  -						 %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| g1-3-3-548.akcr10.global-gateway.net.nz -	0 |  101 |  101 |	0  |	0 |	7 |	1 |
|	  ae6-10.akbr7.global-gateway.net.nz -	   0 |  101 |  101 |	1  |	1 |	1 |	1 |
|	 xe7-0-2.sgbr3.global-gateway.net.nz -	   0 |  101 |  101 |   25 |   25  |   35  |   25  |
|	  ae2-10.sgbr4.global-gateway.net.nz -	   0 |  101 |  101 |   25 |   25  |   26  |   25  |
|	 ae-3.a04.sydnau03.au.ra.gin.ntt.net -		0 |  101 |  101 |   26 |   26  |   28  |   26  |
|	 ae-3.r05.sydnau01.au.bb.gin.ntt.net -		0 |  101 |  101 |   25 |   26  |   49  |   26  |
|	 ae-8.r20.tokyjp05.jp.bb.gin.ntt.net -		   0 |  101 |  101 |  137 |  138 |  146 |  138 |
|	ae-19.r24.tokyjp05.jp.bb.gin.ntt.net -		  0 |  101 |  101 |  137 |  143 |  197 |  168 |
|	 ae-3.r21.sngpsi05.sg.bb.gin.ntt.net -		 0 |  101 |  101 |  203 |  209 |  256 |  204 |
| xe-4-1-0.r00.sngpsi03.sg.bb.gin.ntt.net -	   0 |  101 |  101 |  203 |  204 |  240 |  203 |
|							ntt-sg.sg.gs -					   0 |  101 |  101 |  203 |  205 |  276 |  205 |
|					core-1.v31.sg1.sg.gs -				0 |  101 |  101 |  190 |  190 |  195 |  193 |
|							   dns.sg.gs -					   0 |  101 |  101 |  188 |  189 |  193 |  192 |

Edited by SneakyNZ, 18 June 2015 - 01:40 PM.

[Pjwned]

Location: San Diego county
ISP: Cox Communications

ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=183ms TTL=55
Reply from 103.9.100.1: bytes=32 time=190ms TTL=55
Reply from 103.9.100.1: bytes=32 time=183ms TTL=55
Reply from 103.9.100.1: bytes=32 time=189ms TTL=55

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 190ms, Average = 186ms

tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 8 ms 7 ms 10.175.0.1
3 9 ms 9 ms 13 ms vistcmtk04-gex030000.sd.sd.cox.net [68.6.12.38]

4 14 ms 11 ms 22 ms elcnsysc01-tec192.sd.sd.cox.net [68.6.8.210]
5 22 ms 16 ms 17 ms langbprj01-ae2.0.rd.la.cox.net [68.1.0.136]
6 18 ms 18 ms 15 ms 68.105.30.159
7 239 ms 180 ms 180 ms TenGE8-5.br02.sin02.pccwbtn.net [63.218.228.154]

8 179 ms 178 ms 183 ms TenGE8-5.br02.sin02.pccwbtn.net [63.218.228.154]

9 189 ms 190 ms 189 ms 63-218-213-182.static.pccwglobal.net [63.218.213
.182]
10 181 ms 181 ms 195 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
11 180 ms 181 ms 181 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.


ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=281ms TTL=52
Reply from 203.175.175.203: bytes=32 time=281ms TTL=52
Reply from 203.175.175.203: bytes=32 time=283ms TTL=52
Reply from 203.175.175.203: bytes=32 time=283ms TTL=52

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 281ms, Maximum = 283ms, Average = 282ms

tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 10 ms 9 ms 10.175.0.1
3 8 ms 11 ms 14 ms ip68-101-128-210.sd.sd.cox.net [68.101.128.210]

4 13 ms 16 ms 12 ms elcnsysc01-tec192.sd.sd.cox.net [68.6.8.210]
5 38 ms 38 ms 47 ms sanjbprj01-ae0.0.rd.sj.cox.net [68.1.5.184]
6 48 ms 63 ms 40 ms xe-8-2-2.edge1.SanJose3.Level3.net [4.53.209.81]

7 * 39 ms 47 ms ae-2-70.edge2.SanJose3.Level3.net [4.69.152.81]

8 39 ms 46 ms 38 ms ix-11-0.tcore2.SQN-San-Jose.as6453.net [209.58.1
16.109]
9 44 ms 52 ms 47 ms if-1-2.tcore1.SQN-San-Jose.as6453.net [63.243.20
5.1]
10 53 ms 48 ms 56 ms if-13-2.tcore2.LVW-Los-Angeles.as6453.net [63.24
3.205.66]
11 51 ms 63 ms 76 ms if-2-2.tcore1.LVW-Los-Angeles.as6453.net [66.110
.59.1]
12 34 ms 53 ms 36 ms 63.243.197.2
13 79 ms 48 ms 48 ms core-1.v30.lax1.sg.gs [124.6.40.21]
14 184 ms 181 ms 181 ms core-1.v54.hk1.sg.gs [103.14.244.102]
15 286 ms 282 ms 282 ms core-1.v52.sg3.sg.gs [103.14.244.98]
16 286 ms 303 ms 309 ms core-2.v41.sg1.sg.gs [203.175.175.130]
17 296 ms 287 ms 290 ms dns.sg.gs [203.175.175.203]

Trace complete.

[Vinhasa]

Mike Forst, on 18 June 2015 - 09:57 AM, said:

I am researching datacenters in the APAC/Oceanic region. I could use some help from the players in that region to help me compare the latency and connection quality to some providers in the region. It would also be helpful to gather some data from players on the West coast of the United States and Canada. If you are interested in helping me, I need you to do the following:

• ping and traceroute (MTR preferable if you know how) to the following IP addresses: 103.9.100.1, 203.175.175.203
  
• your rough geographic location
  
• your internet service provider

I understand you may not wish to share this information publicly for all to see on this forum. If you are concerned about that, please feel free to PM me the information instead.

From San Francisco, CA by way of Monkey Brains ISP:

ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=191ms TTL=53
Reply from 103.9.100.1: bytes=32 time=188ms TTL=53
Reply from 103.9.100.1: bytes=32 time=185ms TTL=53
Reply from 103.9.100.1: bytes=32 time=186ms TTL=53

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 191ms, Average = 187ms

ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=267ms TTL=49
Reply from 203.175.175.203: bytes=32 time=264ms TTL=49
Reply from 203.175.175.203: bytes=32 time=271ms TTL=49
Reply from 203.175.175.203: bytes=32 time=262ms TTL=49

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 262ms, Maximum = 271ms, Average = 266ms

tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 11 ms 11 ms gw-gtth300a.static.monkeybrains.net [104.193.168.65]
3 11 ms 11 ms 11 ms lemon.lemon-mosca-10GB.core.monkeybrains.net [208.69.43.185]
4 12 ms 11 ms 11 ms cr1-200p-a-be100.bb.spectrumnet.us [208.76.187.13]
5 11 ms 11 ms 11 ms cr1-9greatoaks-te-0-0-0-2.bb.spectrumnet.us [208.76.185.20]
6 * * * Request timed out.
7 185 ms 187 ms 186 ms TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82]
8 186 ms 187 ms 187 ms TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82]
9 187 ms 187 ms 187 ms 63-218-213-182.static.pccwglobal.net [63.218.213.182]
10 187 ms 187 ms 187 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
11 187 ms 187 ms 187 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 17 ms 11 ms 14 ms gw-gtth300a.static.monkeybrains.net [104.193.168.65]
3 18 ms 12 ms 11 ms lemon.lemon-mosca-10GB.core.monkeybrains.net [208.69.43.185]
4 11 ms 11 ms 11 ms te0-0-1-3.rcr12.b003070-1.sfo01.atlas.cogentco.com [38.99.221.29]
5 11 ms 11 ms 12 ms be2459.ccr22.sfo01.atlas.cogentco.com [154.54.28.77]
6 12 ms 11 ms 23 ms be2165.ccr22.sjc01.atlas.cogentco.com [154.54.28.66]
7 14 ms 16 ms 15 ms be2047.ccr21.sjc03.atlas.cogentco.com [154.54.5.114]
8 11 ms 11 ms 11 ms tata.sjc03.atlas.cogentco.com [154.54.12.142]
9 23 ms 23 ms 23 ms if-3-2.tcore2.LVW-Los-Angeles.as6453.net [63.243.205.14]
10 23 ms 23 ms 23 ms if-2-2.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.1]
11 28 ms 23 ms 27 ms 63.243.197.2
12 51 ms 67 ms 35 ms core-1.v30.lax1.sg.gs [124.6.40.21]
13 272 ms 176 ms 177 ms core-1.v54.hk1.sg.gs [103.14.244.102]
14 266 ms 267 ms 267 ms core-1.v52.sg3.sg.gs [103.14.244.98]
15 268 ms 267 ms 267 ms core-2.v41.sg1.sg.gs [203.175.175.130]
16 267 ms 264 ms 263 ms dns.sg.gs [203.175.175.203]

Trace complete.

[General Solo]

Location: Australia, Sydney
ISP: Optus

Edited by OZHomerOZ, 18 June 2015 - 02:15 PM.

[KODIAK-AU]

Im in Traralgon, Victoria, Australia. (roughly 1.5 hrs east of melbourne)
ISP: Telstra

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\REDACTED>tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 962 ms 4 ms 1 ms telstra.gateway [10.0.0.138]
2 * * * Request timed out.
3 27 ms 26 ms 26 ms 144.130.211.210
4 29 ms 28 ms 28 ms bundle-ether12.win-core10.melbourne.telstra.net
[203.50.11.111]
5 41 ms 38 ms 38 ms bundle-ether6.fli-core1.adelaide.telstra.net [20
3.50.11.90]
6 69 ms 72 ms 70 ms bundle-ether5.wel-core3.perth.telstra.net [203.5
0.11.19]
7 69 ms 74 ms 72 ms tengige0-8-0-5-1.pie-core1.perth.telstra.net [20
3.50.6.198]
8 67 ms 68 ms 68 ms tengige0-5-1-0.pthp-core01.perth.net.reach.com [
203.50.13.254]
9 120 ms 117 ms 118 ms 202.84.143.94
10 120 ms 119 ms 119 ms i-0-3-0-0.6ntp02.bi.telstraglobal.net [202.84.24
3.82]
11 117 ms 117 ms 117 ms 203.116.5.157
12 118 ms 117 ms 119 ms 203.118.15.186
13 117 ms 118 ms 118 ms an-ats-int11.starhub.net.sg [203.118.15.110]
14 117 ms 119 ms 118 ms sh2.eqx1.sg.vodien.com [203.116.246.18]
15 119 ms 119 ms 118 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

C:\Users\REDACTED>tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 248 ms 2 ms 2 ms telstra.gateway [10.0.0.138]
2 * * * Request timed out.
3 30 ms 28 ms 250 ms 144.130.211.210
4 29 ms 28 ms 29 ms bundle-ether12.win-core10.melbourne.telstra.net
[203.50.11.111]
5 39 ms 38 ms 36 ms bundle-ether6.fli-core1.adelaide.telstra.net [20
3.50.11.90]
6 69 ms 72 ms 69 ms bundle-ether5.wel-core3.perth.telstra.net [203.5
0.11.19]
7 69 ms 73 ms 70 ms tengige0-8-0-5-1.pie-core1.perth.telstra.net [20
3.50.6.198]
8 70 ms 67 ms 69 ms 203.50.9.2
9 123 ms 120 ms 120 ms 202.84.143.181
10 118 ms 119 ms 118 ms i-0-3-0-0.6ntp02.bi.telstraglobal.net [202.84.24
3.82]
11 117 ms 118 ms 116 ms 203.116.5.157
12 120 ms 118 ms 117 ms 203.118.15.186
13 116 ms 116 ms 118 ms an-ats-loc11.starhub.net.sg [203.118.15.238]
14 118 ms 118 ms 118 ms starhub-sg.sg.gs [203.116.39.138]
15 133 ms 118 ms 118 ms core-2.v32.sg1.sg.gs [203.175.175.30]
16 117 ms 117 ms 120 ms dns.sg.gs [203.175.175.203]

Trace complete.

Edited by Mike Forst, 18 June 2015 - 03:14 PM.
User had left their real name in their traceroute output

[Roadkill]

Sent mine by PM. Good luck, Mike!

[ArJuna]

Location: Perth, Australia
ISP: iiNet - ADSL2+M (No Interleaving)

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
  1	<1 ms	<1 ms	<1 ms  <sekret>
  2	 7 ms	 7 ms	 6 ms  lo0.bng2.per1.on.ii.net [150.101.32.86]
  3	 9 ms	 7 ms	 7 ms  ae7.cr1.per4.on.ii.net [150.101.33.122]
  4	 7 ms	 7 ms	 8 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  5	57 ms	58 ms	57 ms  pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
  6	58 ms	58 ms	57 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
  7	58 ms	58 ms	59 ms  tl1.sg.vodien.com [103.9.100.1]
Trace complete.
 
 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
  1	<1 ms	<1 ms	<1 ms  <sekret>
  2	 7 ms	 7 ms	 7 ms  lo0.bng2.per1.on.ii.net [150.101.32.86]
  3	 7 ms	 7 ms	 7 ms  ae7.cr1.per1.on.ii.net [150.101.33.120]
  4	54 ms	54 ms	54 ms  po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
  5	92 ms	57 ms	55 ms  eqix-sg.sg.gs [202.79.197.159]
  6	64 ms	58 ms	57 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
  7	60 ms	57 ms	57 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
  8	57 ms	55 ms	55 ms  dns.sg.gs [203.175.175.203]
Trace complete.

And the work connection, also iiNet (Corp Fibre):

 
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
 
  1	 1 ms	 1 ms	 6 ms  <sekret>
  2	 1 ms	 1 ms	 1 ms  <sekret too>
  3	 1 ms	 1 ms	 1 ms  vl10.ext.isp-qv1-core1.iinet.net.au [203.215.5.1
1]
  4	 1 ms	<1 ms	 2 ms  po12.per-qv1-bdr1.on.ii.net [203.215.4.131]
  5	 1 ms	 1 ms	 1 ms  ae6-10.cr1.per4.on.ii.net [150.101.33.90]
  6	 2 ms	 3 ms	 3 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  7	49 ms	49 ms	49 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
  8	48 ms	48 ms	48 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
  9	50 ms	50 ms	50 ms  tl1.sg.vodien.com [103.9.100.1]
 
Trace complete.
 
 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  1	 1 ms	 1 ms	 1 ms  <sekret>
  2	 1 ms	 1 ms	 1 ms  <sekret too>
  3	 2 ms	35 ms	 3 ms  vl10.ext.isp-qv1-core1.iinet.net.au [203.215.5.1
1]
  4	84 ms	 1 ms	 1 ms  po12.per-qv1-bdr1.on.ii.net [203.215.4.131]
  5	 1 ms	 1 ms	 1 ms  ae6-10.cr1.per4.on.ii.net [150.101.33.90]
  6	 2 ms	 2 ms	 1 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  7	49 ms	49 ms	49 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
  8	48 ms	48 ms	55 ms  eqix-sg.sg.gs [202.79.197.159]
  9	64 ms	50 ms	51 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
10	50 ms	50 ms	50 ms  core-2.v41.sg1.sg.gs [203.175.175.130]
11	49 ms	49 ms	49 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.

Edited by ArJuna, 18 June 2015 - 05:49 PM.

[mr bear]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Owner>ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=5ms TTL=56
Reply from 103.9.100.1: bytes=32 time=5ms TTL=56
Reply from 103.9.100.1: bytes=32 time=6ms TTL=56
Reply from 103.9.100.1: bytes=32 time=6ms TTL=56

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

C:\Users\Owner>traceroute 103.9.100.1
'traceroute' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Owner>tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 4 ms 4 ms 4 ms 182.55.229.2
3 3 ms 3 ms 3 ms an-ts-br05.starhub.net.sg [183.90.44.33]
4 3 ms 3 ms 3 ms 183.90.44.177
5 4 ms 4 ms 3 ms an-atl-loc11.starhub.net.sg [203.118.15.174]
6 5 ms 5 ms 5 ms sh1.eqx1.sg.vodien.com [203.116.246.30]
7 6 ms 5 ms 5 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

C:\Users\Owner>ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=3ms TTL=58
Reply from 203.175.175.203: bytes=32 time=4ms TTL=58
Reply from 203.175.175.203: bytes=32 time=4ms TTL=58
Reply from 203.175.175.203: bytes=32 time=4ms TTL=58

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

C:\Users\Owner>tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 4 ms 5 ms 4 ms 182.55.229.2
3 3 ms 3 ms 3 ms an-ts-br05.starhub.net.sg [183.90.44.33]
4 3 ms 3 ms 3 ms 183.90.44.177
5 3 ms 3 ms 3 ms an-ats-loc11.starhub.net.sg [203.118.15.242]
6 4 ms 4 ms 4 ms starhub-sg.sg.gs [203.116.39.138]
7 5 ms 5 ms 5 ms core-1.v31.sg1.sg.gs [203.175.175.21]
8 4 ms 3 ms 3 ms dns.sg.gs [203.175.175.203]

Trace complete.

C:\Users\Owner>

Trace complete.

C:\Users\Owner>
Hope this helps.
Using Starhub for my ISP.
Based out of Singapore.

Edited by mr bear, 18 June 2015 - 03:41 PM.

[Goose]

Verizon; DC Area

|------------------------------------------------------------------------------------------|
|									  WinMTR statistics								   |
|					   Host			  -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|							 192.168.1.1 -	0 |   37 |   37 |	0 |	0 |	1 |	0 |
|	L100.WASHDC-VFTTP-69.verizon-gni.net -	0 |   37 |   37 |	5 |	6 |   14 |	7 |
|  G0-9-2-5.WASHDC-LCR-21.verizon-gni.net -	0 |   37 |   37 |	8 |	9 |   13 |	8 |
|				   No response from host -  100 |	7 |	0 |	0 |	0 |	0 |	0 |
|				0.ae3.BR2.IAD8.ALTER.NET -	0 |   37 |   37 |	7 |	8 |   23 |	8 |
|   ix-20-0.tcore2.AEQ-Ashburn.as6453.net -	0 |   37 |   37 |	8 |	9 |   21 |	9 |
|if-14-8.tcore2.LVW-Los-Angeles.as6453.net -	0 |   37 |   37 |  249 |  251 |  260 |  250 |
|  if-7-2.tcore2.SVW-Singapore.as6453.net -	4 |   33 |   32 |  241 |  243 |  250 |  246 |
| if-20-2.tcore1.SVQ-Singapore.as6453.net -	0 |   37 |   37 |  242 |  243 |  245 |  245 |
|							 180.87.96.2 -	0 |   37 |   37 |  242 |  244 |  257 |  245 |
|			  73.168.22.103.in-addr.arpa -	0 |   37 |   37 |  251 |  252 |  260 |  252 |
|					   tl1.sg.vodien.com -	0 |   37 |   37 |  242 |  243 |  253 |  245 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

|------------------------------------------------------------------------------------------|
|									  WinMTR statistics								   |
|					   Host			  -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|							 192.168.1.1 -	0 |   78 |   78 |	0 |	0 |   10 |	0 |
|	L100.WASHDC-VFTTP-69.verizon-gni.net -	0 |   78 |   78 |	5 |   11 |  142 |	7 |
|  G0-9-2-5.WASHDC-LCR-21.verizon-gni.net -	0 |   78 |   78 |	7 |	9 |   13 |	9 |
|				   No response from host -  100 |   16 |	0 |	0 |	0 |	0 |	0 |
|				0.ae3.BR2.IAD8.ALTER.NET -	0 |   78 |   78 |	8 |   11 |   63 |   19 |
|   ix-20-0.tcore2.AEQ-Ashburn.as6453.net -	0 |   78 |   78 |	8 |   10 |   40 |   10 |
|	 if-11-2.thar2.NJY-Newark.as6453.net -	0 |   78 |   78 |   12 |   14 |   18 |   15 |
| if-14-14.tcore2.NTO-New-York.as6453.net -	2 |   74 |   73 |   13 |   15 |   25 |   16 |
|							 66.110.96.5 -	0 |   78 |   78 |   12 |   15 |   25 |   15 |
|							66.110.96.34 -	0 |   78 |   78 |   12 |   18 |   65 |   14 |
|				   core-1.v30.nyc1.sg.gs -	0 |   78 |   78 |   17 |   48 |  185 |   29 |
|				   core-1.v55.lax1.sg.gs -	0 |   78 |   78 |   87 |  116 |  247 |   98 |
|					core-1.v54.hk1.sg.gs -	0 |   78 |   78 |  231 |  258 |  426 |  240 |
|					core-1.v52.sg3.sg.gs -	0 |   78 |   78 |  274 |  277 |  293 |  275 |
|					core-1.v41.sg1.sg.gs -	0 |   78 |   78 |  262 |  264 |  273 |  264 |
|							   dns.sg.gs -	0 |   78 |   78 |  259 |  266 |  281 |  259 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

There's no helping the formatting: Sorry …

[M a y h e m]

ISP : Telus
Loc : Vancouver BC





AV

[Escef]

I just tweeted the link out, and will mention it tomorrow morning on my livestream, my viewers tend to be Europeans and Aussies, hopefully some of them can help get you some data.

[obeythefist]

Location: Perth, Western Australia
ISP: TPG NBN Fibre 100/40
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| modem.rebellion.local - 0 | 59 | 59 | 0 | 0 | 1 | 0 |
| 10.20.22.109 - 0 | 59 | 59 | 2 | 2 | 4 | 3 |
| per-pow-stg-csw2-tg-2-4.tpgi.com.au - 0 | 59 | 59 | 57 | 62 | 178 | 57 |
| per-pow-stg-crt1-po-2.tpgi.com.au - 0 | 59 | 59 | 53 | 53 | 55 | 53 |
| syd-sot-ken-crt1-gi-0-2-5-3.tpgi.com.au - 0 | 59 | 59 | 50 | 52 | 65 | 53 |
| syd-sot-ken-int1-be-20.tpgi.com.au - 0 | 59 | 59 | 48 | 50 | 53 | 49 |
| ix-11-1-0-0.tcore2.tv2-tokyo.as6453.net - 0 | 59 | 59 | 252 | 254 | 293 | 252 |
| if-6-2.tcore1.svw-singapore.as6453.net - 0 | 59 | 59 | 336 | 336 | 341 | 336 |
| if-11-2.thar1.svq-singapore.as6453.net - 2 | 55 | 54 | 352 | 352 | 357 | 353 |
| if-7-2.tcore1.svq-singapore.as6453.net - 0 | 59 | 59 | 344 | 344 | 353 | 345 |
| 180.87.96.2 - 0 | 59 | 59 | 354 | 355 | 365 | 354 |
| 73.168.22.103.in-addr.arpa - 0 | 59 | 59 | 353 | 354 | 390 | 355 |
| tl1.sg.vodien.com - 0 | 59 | 59 | 337 | 338 | 351 | 337 |
|________________________________________________|______|______|______|______|______|______|


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| modem.rebellion.local - 0 | 24 | 24 | 0 | 0 | 0 | 0 |
| 10.20.22.109 - 0 | 24 | 24 | 2 | 2 | 4 | 2 |
| per-pow-stg-csw2-tg-2-4.tpgi.com.au - 0 | 24 | 24 | 54 | 54 | 55 | 55 |
| per-pow-stg-crt1-po-2.tpgi.com.au - 0 | 24 | 24 | 54 | 54 | 55 | 55 |
|syd-gls-har-crt1-tg-0-0-0-13.tpgi.com.au - 0 | 24 | 24 | 55 | 56 | 59 | 58 |
| syd-gls-har-int2-be-20.tpgi.com.au - 0 | 24 | 24 | 54 | 56 | 59 | 56 |
| sggs2-10G.hkix.net - 0 | 24 | 24 | 273 | 273 | 277 | 277 |
| core-1.v30.hk1.sg.gs - 0 | 24 | 24 | 280 | 304 | 402 | 305 |
| core-1.v52.sg3.sg.gs - 0 | 24 | 24 | 308 | 308 | 318 | 309 |
| core-2.v41.sg1.sg.gs - 0 | 24 | 24 | 310 | 311 | 314 | 312 |
| dns.sg.gs - 0 | 24 | 24 | 309 | 309 | 311 | 309 |
|________________________________________________|______|______|______|______|______|______|


Looks like TPG routes everyone in Perth through Sydney no matter how bad that makes the customer experience. One thing to note - TPG is acquiring iiNet (and thus Internode and WestNet), so iiNet Perth customers that currently demonstrate low pings should not have those results taken seriously as when TPG takes control it's likely they will be routed through the same pipes that TPG is using.