83 replies to this topic

[General Solo]

I suggest using MTR as per Mike Forst's suggestion as it displays your connections ping over time (jitter).
(Jitter is a measure of the quality of your internet connection, important in real time applications.)

Not only will it help PGI to determine the best location for their oceanic data centre, it will also help you determine the quality of your connection to these ip's and thus mwo when the servers come online.

In other words it will help you determine what quality of connection your ISP will provide you to access these oceanic servers.

It might encourage your local ISP into action if word got around they suxed at gaming. Just a thought. I understand some ISP's don't care. But if we get some solid data people may change ISP's and then other ISP's might start to care. Kinda like whirlpool for mwo isp's.

And even if ISP's don't care, by checking this thread, maybe you will know which ones to avoid.

Edited by OZHomerOZ, 19 June 2015 - 02:59 AM.

[MayoRe]

Location : Malaysia
ISP : TIME

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=17ms TTL=53
Reply from 103.9.100.1: bytes=32 time=14ms TTL=53
Reply from 103.9.100.1: bytes=32 time=14ms TTL=53
Reply from 103.9.100.1: bytes=32 time=14ms 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 = 14ms, Maximum = 17ms, Average = 14ms

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=13ms TTL=54
Reply from 203.175.175.203: bytes=32 time=13ms TTL=54
Reply from 203.175.175.203: bytes=32 time=13ms TTL=54
Reply from 203.175.175.203: bytes=32 time=13ms TTL=54

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

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 2 ms 2 ms 2 ms DD-WRT [10.10.10.1]
2 2 ms 8 ms 3 ms 192.168.1.1
3 5 ms 5 ms 8 ms cgw-211-24-64-1.bbrtl.time.net.my [211.24.64.1]

4 5 ms 4 ms 5 ms xe-5-3-0-0.er-01-majjw.ni.time.net.my [223.28.2.
41]
5 19 ms 14 ms 19 ms xe-5-3-0-0.er-01-glsfb.ni.time.net.my [223.28.2.
37]
6 16 ms 14 ms 15 ms xe-0-1-0-1.cr-02-glsfb.ni.time.net.my [223.28.2.
9]
7 12 ms 12 ms 12 ms 223.28.26.82
8 13 ms 14 ms 13 ms starhub1.sgix.sg [103.16.102.71]
9 13 ms 13 ms 16 ms 203.118.15.229
10 17 ms 13 ms 13 ms an-ats-int11.starhub.net.sg [203.118.15.110]
11 15 ms 14 ms 14 ms sh2.eqx1.sg.vodien.com [203.116.246.18]
12 14 ms 14 ms 25 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 DD-WRT [10.10.10.1]
2 5 ms 2 ms 7 ms 192.168.1.1
3 9 ms 7 ms 11 ms cgw-211-24-64-1.bbrtl.time.net.my [211.24.64.1]

4 21 ms 5 ms 9 ms xe-5-3-0-0.er-01-majjw.ni.time.net.my [223.28.2.
41]
5 14 ms 14 ms 22 ms xe-5-3-0-0.er-01-glsfb.ni.time.net.my [223.28.2.
37]
6 21 ms 15 ms 14 ms xe-0-1-0-1.cr-02-glsfb.ni.time.net.my [223.28.2.
9]
7 13 ms 12 ms 13 ms 223.28.26.82
8 14 ms 17 ms 14 ms sgix.sg.gs [103.16.102.30]
9 15 ms 17 ms 15 ms core-2.v32.sg1.sg.gs [203.175.175.30]
10 17 ms 13 ms 12 ms dns.sg.gs [203.175.175.203]

Trace complete.

[Taj the White Tiger]

Heres my Ping from Melbourne on Telstra

[Past]

Ok here is my Internode ISP Results From Bunbury Western Australia:

C:\Users\User>ping 103.9.100.1
Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=87ms TTL=59
Reply from 103.9.100.1: bytes=32 time=83ms TTL=59
Reply from 103.9.100.1: bytes=32 time=83ms TTL=59
Reply from 103.9.100.1: bytes=32 time=83ms TTL=59
Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 87ms, Average = 84ms

C:\Users\User>ping 203.175.175.203
Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=80ms TTL=56
Reply from 203.175.175.203: bytes=32 time=81ms TTL=56
Reply from 203.175.175.203: bytes=32 time=80ms TTL=56
Reply from 203.175.175.203: bytes=32 time=83ms TTL=56
Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 83ms, Average = 81ms

traceroute to 103.9.100.1 (103.9.100.1), 30 hops max, 38 byte packets
1 lns20.per1.on.ii.net (150.101.0.206) 33.943 ms 32.261 ms 32.800 ms
2 xe-0-3-1.cr1.per2.on.iinet (150.101.34.129) 34.385 ms 34.958 ms 33.697 ms
3 ae0.cr1.per1.on.ii.net (150.101.34.171) 33.797 ms 32.381 ms 33.209 ms
4 po0-3-0.bdr1.sin1.on.ii.net (203.16.211.229) 79.828 ms pos1-2-0.bdr1.sin1.on.ii.net (150.101.33.68) 81.593 ms 86.536 ms
5 eie1.eqx1.sg.vodien.com (202.79.197.178) 96.290 ms 80.702 ms 82.243 ms
6 tl1.sg.vodien.com (103.9.100.1) 82.067 ms 80.684 ms 80.504 ms

traceroute to 203.175.175.203 (203.175.175.203), 30 hops max, 38 byte packets
1 lns20.per1.on.ii.net (150.101.0.206) 33.639 ms 32.271 ms 31.932 ms
2 xe-0-0-1.cr1.per1.on.ii.net (150.101.33.94) 32.709 ms 33.402 ms 32.927 ms
3 po0-3-0.bdr1.sin1.on.ii.net (203.16.211.229) 80.071 ms pos-0-3-1.bdr1.sin1.on.ii.net (150.101.33.176) 83.002 ms 79.206 ms
4 eqix-sg.sg.gs (202.79.197.159) 81.515 ms 79.735 ms 83.197 ms
5 core-1.v30.sg3.sg.gs (203.175.175.53) 85.461 ms 81.173 ms 84.219 ms
6 core-2.v41.sg1.sg.gs (203.175.175.130) 83.717 ms core-1.v41.sg1.sg.gs (203.175.175.129) 84.147 ms 87.360 ms
7 dns.sg.gs (203.175.175.203) 81.738 ms 82.940 ms 82.461 ms

[-Cal-]

Location: Canberra Australia,
ISP: TPG

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\**>ping 103.9.100.1
Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=295ms TTL=50
Reply from 103.9.100.1: bytes=32 time=299ms TTL=50
Reply from 103.9.100.1: bytes=32 time=302ms TTL=50
Reply from 103.9.100.1: bytes=32 time=303ms TTL=50
Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 295ms, Maximum = 303ms, Average = 299ms
C:\Users\**>tracert 103.9.100.1
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
1 2 ms 2 ms 1 ms 192.168.0.1
2 17 ms 19 ms 20 ms 10.20.22.233
3 18 ms 18 ms 16 ms cbr-apt-mar-csw1-te-1-5.tpgi.com.au [203.213.56.5]
4 235 ms 223 ms 223 ms ix-11-1-0-0.tcore2.TV2-Tokyo.as6453.net [116.0.88.21]
5 293 ms 293 ms * if-6-2.tcore1.SVW-Singapore.as6453.net [180.87.12.109]
6 294 ms 293 ms 293 ms if-2-2.tcore2.SVW-Singapore.as6453.net [180.87.12.2]
7 293 ms 293 ms 295 ms if-20-2.tcore1.SVQ-Singapore.as6453.net [180.87.96.21]
8 310 ms 295 ms * 180.87.96.2
9 291 ms 292 ms 293 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
10 295 ms 293 ms 294 ms tl1.sg.vodien.com [103.9.100.1]
Trace complete.
C:\Users\**>ping 203.175.175.203
Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=276ms TTL=54
Reply from 203.175.175.203: bytes=32 time=277ms TTL=54
Reply from 203.175.175.203: bytes=32 time=276ms TTL=54
Reply from 203.175.175.203: bytes=32 time=276ms TTL=54
Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 276ms, Maximum = 277ms, Average = 276ms
C:\Users\**>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 2 ms 192.168.0.1
2 18 ms 18 ms 17 ms 10.20.22.233
3 16 ms 20 ms 44 ms cbr-apt-mar-csw2-te-1-5.tpgi.com.au [203.213.56.9]
4 241 ms 246 ms 240 ms sggs2-10G.hkix.net [123.255.90.102]
5 257 ms 409 ms 253 ms core-1.v30.hk1.sg.gs [124.6.32.21]
6 279 ms * 276 ms core-1.v52.sg3.sg.gs [103.14.244.98]
7 278 ms 278 ms 279 ms core-1.v41.sg1.sg.gs [203.175.175.129]
8 280 ms 278 ms 276 ms dns.sg.gs [203.175.175.203]
Trace complete.

[bundy]

Outback Western Australia
Mobile 4g telstra
[color=#00FFFF]203.175.175.203[/color]
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.43.1 - 0 | 6 | 6 | 2 | 3 | 7 | 3 |
| No response from host - 100 | 6 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 6 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 6 | 0 | 0 | 0 | 0 | 0 |
|TenGigE0-3-0-15.wel-edge901.perth.telstra.net - 0 | 6 | 6 | 49 | 53 | 62 | 54 |
|bundle-ether6.wel-core3.perth.telstra.net - 0 | 6 | 6 | 50 | 61 | 92 | 50 |
|tengige0-8-0-5-1.pie-core1.perth.telstra.net - 0 | 6 | 6 | 48 | 51 | 54 | 50 |
|tengige0-5-1-0.pthp-core01.perth.net.reach.com - 0 | 6 | 6 | 46 | 51 | 55 | 46 |
|i-0-1-4-0.skdi-core01.bx.telstraglobal.net - 0 | 6 | 6 | 98 | 103 | 117 | 101 |
| i-0-3-0-0.6ntp02.bi.telstraglobal.net - 0 | 6 | 6 | 97 | 105 | 118 | 106 |
| 203.116.5.157 - 17 | 6 | 5 | 94 | 98 | 104 | 98 |
| 203.118.15.181 - 0 | 5 | 5 | 97 | 99 | 102 | 101 |
| 203.118.15.242 - 0 | 5 | 5 | 96 | 111 | 131 | 131 |
| starhub-sg.sg.gs - 0 | 5 | 5 | 97 | 110 | 126 | 124 |
| core-1.v31.sg1.sg.gs - 0 | 5 | 5 | 98 | 100 | 105 | 105 |
| dns.sg.gs - 0 | 5 | 5 | 122 | 126 | 129 | 122 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )







[color=#00FFFF]103.9.100.1[/color]
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.43.1 - 0 | 9 | 9 | 1 | 2 | 3 | 3 |
| No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
|TenGigE0-3-0-15.wel-edge901.perth.telstra.net - 0 | 8 | 8 | 47 | 53 | 57 | 57 |
|bundle-ether6.wel-core3.perth.telstra.net - 0 | 8 | 8 | 52 | 55 | 59 | 55 |
|tengige0-8-0-5-1.pie-core1.perth.telstra.net - 0 | 8 | 8 | 51 | 54 | 60 | 51 |
|tengige0-0-1-0.pthp-core01.perth.net.reach.com - 0 | 8 | 8 | 51 | 53 | 57 | 52 |
|i-0-0-1-0.skdi-core01.bx.telstraglobal.net - 0 | 8 | 8 | 96 | 107 | 134 | 134 |
| i-0-3-0-0.6ntp02.bi.telstraglobal.net - 0 | 8 | 8 | 98 | 107 | 126 | 98 |
| 203.116.5.157 - 0 | 8 | 8 | 96 | 111 | 138 | 102 |
| 203.118.15.186 - 0 | 8 | 8 | 97 | 105 | 122 | 98 |
| an-ats-int11.starhub.net.sg - 0 | 8 | 8 | 100 | 143 | 412 | 104 |
| sh2.eqx1.sg.vodien.com - 0 | 8 | 8 | 99 | 107 | 120 | 106 |
| tl1.sg.vodien.com - 0 | 8 | 8 | 97 | 122 | 136 | 125 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )

[WarHorseOne]

Location: Hunter Valley, NSW, Australia.
ISP: DODO (reselling Telstra)
103.9.100.1:

Spoiler

l:\Users\Mitchell>ping 103.9.100.1
Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=166ms TTL=51
Reply from 103.9.100.1: bytes=32 time=166ms TTL=50
Reply from 103.9.100.1: bytes=32 time=167ms TTL=50
Reply from 103.9.100.1: bytes=32 time=165ms TTL=50
Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 167ms, Average = 166ms

l:\Users\Mitchell>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 *REDACTED* [*REDACTED*]
2 22 ms 22 ms 21 ms 96.3.148.122.network.m2core.net.au [122.148.3.96]
3 22 ms 22 ms 22 ms be2-v539-bsr02-masceqx.syd.nsw.m2core.net.au [122.148.4.65]
4 23 ms 22 ms 23 ms 119.225.42.181
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 23 ms 23 ms 24 ms 59.154.18.8
9 259 ms 165 ms 164 ms 203.208.131.125
10 166 ms 164 ms 164 ms 203.208.158.2
11 165 ms 165 ms 165 ms 203.208.190.38
12 167 ms 167 ms 167 ms 29.168.22.103.in-addr.arpa [103.22.168.29]
13 169 ms 167 ms 167 ms tl1.sg.vodien.com [103.9.100.1]
Trace complete.

203.175.175.203:

Spoiler

l:\Users\Mitchell>ping 203.175.175.203
Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=232ms TTL=47
Reply from 203.175.175.203: bytes=32 time=232ms TTL=47
Reply from 203.175.175.203: bytes=32 time=233ms TTL=47
Reply from 203.175.175.203: bytes=32 time=233ms TTL=46
Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 232ms, Maximum = 233ms, Average = 232ms

l:\Users\Mitchell>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 *REDACTED* [*REDACTED*]
2 23 ms 22 ms 22 ms 96.3.148.122.network.m2core.net.au [122.148.3.96]
3 24 ms 25 ms 25 ms be2-v539-bsr02-masceqx.syd.nsw.m2core.net.au [122.148.4.65]
4 24 ms 24 ms 24 ms TenGigE0-0-0-4.ken-edge902.sydney.telstra.net [139.130.199.89]
5 27 ms 27 ms 26 ms bundle-ether14.ken-core10.sydney.telstra.net [203.50.11.96]
6 38 ms 38 ms 37 ms bundle-ether12.win-core10.melbourne.telstra.net [203.50.11.123]
7 46 ms 47 ms 47 ms bundle-ether6.fli-core1.adelaide.telstra.net [203.50.11.90]
8 82 ms 82 ms 83 ms bundle-ether5.wel-core3.perth.telstra.net [203.50.11.19]
9 82 ms 82 ms 79 ms tengige0-8-0-5-1.pie-core1.perth.telstra.net [203.50.6.198]
10 79 ms 79 ms 79 ms tengige0-5-1-0.pthp-core01.perth.net.reach.com [203.50.13.254]
11 183 ms 183 ms 183 ms 202.84.143.94
12 183 ms 185 ms 183 ms 202.84.243.82
13 235 ms 234 ms 235 ms 203.116.5.157
14 232 ms 233 ms 233 ms 203.118.15.181
15 234 ms 232 ms 232 ms an-ats-loc11.starhub.net.sg [203.118.15.242]
16 233 ms 232 ms 233 ms starhub-sg.sg.gs [203.116.39.138]
17 194 ms 235 ms 235 ms core-1.v31.sg1.sg.gs [203.175.175.21]
18 233 ms 234 ms 232 ms dns.sg.gs [203.175.175.203]
Trace complete.

192.99.109.129 (mwomercs.com just for comparison):

Spoiler

l:\Users\Mitchell>ping 192.99.109.129
Pinging 192.99.109.129 with 32 bytes of data:
Reply from 192.99.109.129: bytes=32 time=247ms TTL=46
Reply from 192.99.109.129: bytes=32 time=249ms TTL=47
Reply from 192.99.109.129: bytes=32 time=248ms TTL=46
Reply from 192.99.109.129: bytes=32 time=247ms TTL=46
Ping statistics for 192.99.109.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 247ms, Maximum = 249ms, Average = 247ms

l:\Users\Mitchell>tracert 192.99.109.129
Tracing route to 192.99.109.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms *REDACTED* [*REDACTED*]
2 22 ms 21 ms 21 ms 96.3.148.122.network.m2core.net.au [122.148.3.96]
3 23 ms 22 ms 22 ms be2-v539-bsr02-masceqx.syd.nsw.m2core.net.au [122.148.4.65]
4 22 ms 22 ms 22 ms 119.225.42.181
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 26 ms 26 ms 26 ms 59.154.18.12
10 * * * Request timed out.
11 * * * Request timed out.
12 25 ms 25 ms 26 ms 59.154.18.26
13 182 ms 182 ms 182 ms 203.208.190.69
14 186 ms 182 ms 181 ms 203.208.171.38
15 * * * Request timed out.
16 * * * Request timed out.
17 260 ms 313 ms 418 ms mtl-2-6k.qc.ca [198.27.73.179]
18 247 ms 248 ms 248 ms bhs-g2-6k.qc.ca [198.27.73.7]
19 248 ms 248 ms 248 ms 198.27.73.233
20 246 ms 247 ms 247 ms 192.99.109.129
Trace complete.

EDIT: Formatting

Edited by WarHorseOne, 19 June 2015 - 05:25 AM.

[matux]

Location: Gold Coast, Qld, Australia
ISP: iinet

103.9.100.1
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 168 | 168 | 1 | 14 | 162 | 2 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| ae2.cr1.bne7.on.ii.net - 0 | 168 | 168 | 18 | 35 | 188 | 20 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| pos-0-3-1.bdr1.sin1.on.ii.net - 0 | 168 | 168 | 153 | 173 | 468 | 156 |
| eie1.eqx1.sg.vodien.com - 0 | 168 | 168 | 153 | 173 | 443 | 154 |
| tl1.sg.vodien.com - 0 | 168 | 168 | 153 | 172 | 448 | 154 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


203.175.175.203
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 213 | 213 | 1 | 122 | 547 | 74 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| ae2.cr1.bne7.on.ii.net - 1 | 203 | 201 | 17 | 168 | 810 | 250 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| pos1-2-0.bdr1.sin1.on.ii.net - 0 | 213 | 213 | 155 | 265 | 701 | 242 |
| eqix-sg.sg.gs - 0 | 213 | 213 | 155 | 277 | 701 | 242 |
| core-1.v30.sg3.sg.gs - 0 | 213 | 213 | 155 | 275 | 746 | 238 |
| core-2.v41.sg1.sg.gs - 0 | 213 | 213 | 156 | 263 | 703 | 241 |
| dns.sg.gs - 0 | 213 | 213 | 154 | 271 | 701 | 239 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Edited by matux, 19 June 2015 - 05:24 AM.

[CMDR Argo]

San Marcos California United States

Provider: ATT UVERSE TOP TIER


C:\>ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=335ms TTL=49
Reply from 203.175.175.203: bytes=32 time=325ms TTL=49
Reply from 203.175.175.203: bytes=32 time=315ms TTL=49
Reply from 203.175.175.203: bytes=32 time=290ms 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 = 290ms, Maximum = 335ms, Average = 316ms

C:\>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 2 ms homeportal [192.168.1.254]
2 25 ms 22 ms 21 ms 107-218-12-2.lightspeed.sndgca.sbcglobal.net [10
7.218.12.2]
3 22 ms 22 ms 21 ms 75.20.78.172
4 107 ms 108 ms 115 ms 12.83.70.181
5 131 ms 133 ms 144 ms ggr2.la2ca.ip.att.net [12.122.129.97]
6 125 ms 128 ms 133 ms ix-15-0.tcore1.LVW-Los-Angeles.as6453.net [66.11
0.59.41]
7 127 ms 107 ms 133 ms 63.243.197.2
8 114 ms 114 ms 122 ms core-1.v30.lax1.sg.gs [124.6.40.21]
9 306 ms 278 ms 291 ms core-1.v54.hk1.sg.gs [103.14.244.102]
10 310 ms 338 ms 297 ms core-1.v52.sg3.sg.gs [103.14.244.98]
11 302 ms 270 ms 309 ms core-1.v41.sg1.sg.gs [203.175.175.129]
12 279 ms 293 ms 297 ms dns.sg.gs [203.175.175.203]

Trace complete.

C:\>ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=226ms TTL=53
Reply from 103.9.100.1: bytes=32 time=255ms TTL=53
Reply from 103.9.100.1: bytes=32 time=331ms TTL=53
Reply from 103.9.100.1: bytes=32 time=278ms 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 = 226ms, Maximum = 331ms, Average = 272ms

C:\>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 1 ms 2 ms homeportal [192.168.1.254]
2 24 ms 21 ms 22 ms 107-218-12-2.lightspeed.sndgca.sbcglobal.net [10
7.218.12.2]
3 * * * Request timed out.
4 130 ms 132 ms 136 ms 12.83.70.177
5 144 ms 118 ms 115 ms ggr2.la2ca.ip.att.net [12.122.129.97]
6 134 ms 134 ms 91 ms ix-15-0.tcore1.LVW-Los-Angeles.as6453.net [66.11
0.59.41]
7 288 ms 272 ms 206 ms if-2-2.tcore2.LVW-Los-Angeles.as6453.net [66.110
.59.2]
8 276 ms 213 ms 292 ms if-7-2.tcore2.SVW-Singapore.as6453.net [180.87.1
5.25]
9 286 ms 295 ms 252 ms if-20-2.tcore1.SVQ-Singapore.as6453.net [180.87.
96.21]
10 325 ms 322 ms 310 ms 180.87.96.2
11 313 ms 316 ms 353 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
12 319 ms 227 ms 324 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

[Quattro1982]

Looks like you guys are looking at 2 providers, HostSG and Vodien
Location: Singapore
ISP: StarHub MaxOnline Cable Broadband

203.175.175.203
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| unknown.maxonline.com.sg - 0 | 42 | 42 | 10 | 21 | 86 | 86 |
| unknown.maxonline.com.sg - 0 | 42 | 42 | 9 | 21 | 85 | 85 |
| 172.20.53.65 - 0 | 42 | 42 | 11 | 21 | 86 | 86 |
| 172.26.53.1 - 0 | 42 | 42 | 12 | 24 | 86 | 86 |
| 172.20.7.222 - 0 | 42 | 42 | 14 | 24 | 86 | 86 |
| 203.116.97.73 - 0 | 42 | 42 | 9 | 22 | 144 | 36 |
| an-ats-loc11.starhub.net.sg - 0 | 42 | 42 | 10 | 21 | 36 | 36 |
| starhub-sg.sg.gs - 0 | 42 | 42 | 11 | 22 | 37 | 37 |
| core-2.v32.sg1.sg.gs - 0 | 42 | 42 | 13 | 25 | 87 | 87 |
| dns.sg.gs - 0 | 42 | 42 | 16 | 22 | 33 | 33 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


103.9.100.1
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| unknown.maxonline.com.sg - 0 | 41 | 41 | 10 | 20 | 48 | 20 |
| unknown.maxonline.com.sg - 0 | 41 | 41 | 8 | 18 | 47 | 17 |
| 172.20.53.65 - 0 | 41 | 41 | 8 | 19 | 40 | 21 |
| 172.26.53.1 - 0 | 41 | 41 | 13 | 22 | 46 | 20 |
| 172.20.7.178 - 0 | 41 | 41 | 14 | 22 | 46 | 19 |
| 203.116.97.73 - 0 | 41 | 41 | 11 | 26 | 212 | 24 |
| an-atl-loc11.starhub.net.sg - 0 | 41 | 41 | 10 | 21 | 48 | 21 |
| sh1.eqx1.sg.vodien.com - 0 | 41 | 41 | 13 | 23 | 47 | 26 |
| tl1.sg.vodien.com - 0 | 41 | 41 | 14 | 24 | 47 | 28 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


=================================================

Just to give more data, I use my 4G mobile broadband

Location: Singapore
ISP: StarHub Mobile

203.175.175.203
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| **************** - 0 | 46 | 46 | 17 | 29 | 124 | 26 |
| ******************** - 0 | 46 | 46 | 16 | 31 | 169 | 26 |
| 203.116.246.177 - 0 | 46 | 46 | 15 | 28 | 168 | 26 |
| starhub-sg.sg.gs - 0 | 46 | 46 | 16 | 36 | 174 | 22 |
| core-1.v31.sg1.sg.gs - 0 | 46 | 46 | 16 | 28 | 108 | 25 |
| dns.sg.gs - 0 | 46 | 46 | 15 | 29 | 163 | 26 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

103.9.100.1
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| **************** - 0 | 38 | 38 | 18 | 37 | 50 | 39 |
| ******************** - 0 | 38 | 38 | 17 | 37 | 64 | 38 |
| 203.116.246.177 - 0 | 38 | 38 | 18 | 38 | 62 | 35 |
| 203.118.15.237 - 0 | 38 | 38 | 16 | 38 | 63 | 32 |
| 203.118.2.26 - 0 | 38 | 38 | 17 | 39 | 61 | 39 |
| an-atl-loc11.starhub.net.sg - 0 | 38 | 38 | 18 | 38 | 62 | 37 |
| sh1.eqx1.sg.vodien.com - 0 | 38 | 38 | 19 | 38 | 60 | 37 |
| tl1.sg.vodien.com - 0 | 38 | 38 | 18 | 41 | 67 | 34 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Edited by Quattro1982, 19 June 2015 - 06:58 AM.

[Eboli]

Ping to 103.9.100.1 = Min 143ms, max 147ms, average 144ms
Ping to 203.175.175.203 = Min 143ms, max 160ms, average 147ms


Location, Canberra, Australia
Service Provider: iinet

Cheers!
Eboli

Edited by Eboli, 19 June 2015 - 07:51 AM.

[Karamarka]

• 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

ping to both = 165ms
victoria, aus
optus

[Jonatan Payne]

California, East Bay, ComCast

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=200ms TTL=54
Reply from 103.9.100.1: bytes=32 time=199ms TTL=54
Reply from 103.9.100.1: bytes=32 time=199ms TTL=54
Reply from 103.9.100.1: bytes=32 time=200ms TTL=54

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



Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=199ms TTL=51
Reply from 203.175.175.203: bytes=32 time=199ms TTL=51
Reply from 203.175.175.203: bytes=32 time=199ms TTL=51
Reply from 203.175.175.203: bytes=32 time=198ms TTL=51

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



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 8 ms 9 ms 7 ms c-76-21-88-1.hsd1.ca.comcast.net [76.21.88.1]
3 9 ms 7 ms 8 ms te-0-7-0-12-sur04.pinole.ca.sfba.comcast.net [68
.85.190.137]
4 9 ms 8 ms 8 ms te-0-7-0-21-sur03.pinole.ca.sfba.comcast.net [69
.139.198.197]
5 16 ms 16 ms 15 ms te-0-2-0-9-ar01.sfsutro.ca.sfba.comcast.net [69.
139.199.54]
6 15 ms 15 ms 14 ms be-80-ar01.santaclara.ca.sfba.comcast.net [68.85
.154.130]
7 * * * Request timed out.
8 15 ms 15 ms 15 ms he-0-11-0-1-pe02.529bryant.ca.ibone.comcast.net
[68.86.86.146]
9 14 ms 14 ms 14 ms ix-0-1-1-0.tcore1.PDI-Palo-Alto.as6453.net [66.1
98.127.33]
10 188 ms 188 ms 189 ms if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.1
27.2]
11 190 ms * 189 ms if-9-2.tcore1.TV2-Tokyo.as6453.net [180.87.180.1
8]
12 192 ms 192 ms 192 ms if-2-2.tcore2.TV2-Tokyo.as6453.net [180.87.180.2
]
13 190 ms 190 ms 190 ms if-6-2.tcore1.SVW-Singapore.as6453.net [180.87.1
2.109]
14 189 ms 191 ms 189 ms if-2-2.tcore2.SVW-Singapore.as6453.net [180.87.1
2.2]
15 189 ms 189 ms 191 ms if-20-2.tcore1.SVQ-Singapore.as6453.net [180.87.
96.21]
16 200 ms 199 ms 202 ms 180.87.96.2
17 199 ms 199 ms 199 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
18 200 ms 200 ms 200 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 192.168.1.1
2 9 ms 7 ms 8 ms c-76-21-88-1.hsd1.ca.comcast.net [76.21.88.1]
3 8 ms 8 ms 8 ms te-0-7-0-12-sur04.pinole.ca.sfba.comcast.net [68
.85.190.137]
4 9 ms 8 ms 8 ms te-0-7-0-22-sur03.pinole.ca.sfba.comcast.net [69
.139.198.201]
5 16 ms 16 ms 15 ms te-1-11-0-12-ar01.sfsutro.ca.sfba.comcast.net [6
8.87.194.90]
6 14 ms 15 ms 15 ms be-80-ar01.santaclara.ca.sfba.comcast.net [68.85
.154.130]
7 * * * Request timed out.
8 15 ms 14 ms 15 ms he-0-11-0-1-pe02.529bryant.ca.ibone.comcast.net
[68.86.86.146]
9 15 ms 14 ms 14 ms ix-0-1-1-0.tcore1.PDI-Palo-Alto.as6453.net [66.1
98.127.33]
10 25 ms 25 ms 24 ms if-3-2.tcore1.LVW-Los-Angeles.as6453.net [66.198
.127.26]
11 24 ms 24 ms 24 ms 63.243.197.2
12 39 ms 52 ms 37 ms core-1.v30.lax1.sg.gs [124.6.40.21]
13 193 ms 181 ms 176 ms core-1.v54.hk1.sg.gs [103.14.244.102]
14 200 ms 199 ms 199 ms core-1.v52.sg3.sg.gs [103.14.244.98]
15 200 ms 200 ms 199 ms core-2.v41.sg1.sg.gs [203.175.175.130]
16 199 ms 199 ms 199 ms dns.sg.gs [203.175.175.203]

Trace complete.

Edited by Hvergelmir, 19 June 2015 - 11:12 AM.

[HulkBear Furey]

Location: Whangarei, New Zealand, 1 hour north of Auckland
ISP: Myrepublic with gaming latency and 100mb download and 50mb upload

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

C:\Users\Work>tracert 103.9.100.1

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

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 145 ms 145 ms 145 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

C:\Users\Work>tracert 203.175.175.203

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

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 122 ms 122 ms 123 ms dns.sg.gs [203.175.175.203]

Trace complete.

C:\Users\Work>ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=146ms TTL=56
Reply from 103.9.100.1: bytes=32 time=146ms TTL=56
Reply from 103.9.100.1: bytes=32 time=147ms TTL=56
Reply from 103.9.100.1: bytes=32 time=146ms 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 = 146ms, Maximum = 147ms, Average = 146ms

C:\Users\Work>ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=122ms TTL=53
Reply from 203.175.175.203: bytes=32 time=123ms TTL=53
Reply from 203.175.175.203: bytes=32 time=123ms TTL=53
Reply from 203.175.175.203: bytes=32 time=123ms 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 = 122ms, Maximum = 123ms, Average = 122ms

C:\Users\Work>

[dtgamemaster]

M1 Fiberoptic

103.9.100.1

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 15 | 15 | 0 | 0 | 0 | 0 |
| 1.64.156.175.unknown.m1.com.sg - 0 | 15 | 15 | 1 | 2 | 6 | 2 |
| 242.246.65.202.unknown.m1.com.sg - 0 | 15 | 15 | 3 | 4 | 17 | 4 |
| 241.246.65.202.unknown.m1.com.sg - 0 | 15 | 15 | 1 | 1 | 2 | 2 |
| 37.246.65.202.unknown.m1.com.sg - 25 | 8 | 6 | 0 | 10 | 27 | 2 |
| 21.246.65.202.unknown.m1.com.sg - 0 | 15 | 15 | 2 | 2 | 3 | 2 |
| eie1.eqx1.sg.vodien.com - 0 | 15 | 15 | 2 | 3 | 10 | 3 |
| tl1.sg.vodien.com - 0 | 15 | 15 | 3 | 3 | 4 | 4 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

203.175.175.203

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 12 | 12 | 0 | 0 | 0 | 0 |
| 1.64.156.175.unknown.m1.com.sg - 0 | 12 | 12 | 2 | 2 | 3 | 3 |
| 242.246.65.202.unknown.m1.com.sg - 0 | 12 | 12 | 4 | 7 | 10 | 8 |
| No response from host - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| 37.246.65.202.unknown.m1.com.sg - 13 | 8 | 7 | 0 | 14 | 25 | 24 |
| 21.246.65.202.unknown.m1.com.sg - 0 | 12 | 12 | 2 | 2 | 3 | 2 |
| eqix-sg.sg.gs - 0 | 12 | 12 | 2 | 2 | 3 | 3 |
| core-1.v30.sg3.sg.gs - 0 | 12 | 12 | 3 | 6 | 12 | 3 |
| core-2.v41.sg1.sg.gs - 0 | 12 | 12 | 4 | 4 | 8 | 4 |
| dns.sg.gs - 0 | 12 | 12 | 3 | 3 | 3 | 3 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Edited by dtgamemaster, 19 June 2015 - 06:29 PM.

[Gryphorim]

Melbourne city, Victoria, Australia

ISP: Telstra Velocity

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

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 7 ms 4 ms 5 ms 172.18.210.15
3 6 ms 4 ms 5 ms 172.18.68.133
4 7 ms 4 ms 5 ms bundle-ether4.lon-edge902.melbourne.telstra.net
[203.50.76.12]
5 6 ms 10 ms 12 ms bundle-ether11.exi-core10.melbourne.telstra.net
[203.50.11.113]
6 19 ms 24 ms 22 ms bundle-ether5.way-core4.adelaide.telstra.net [20
3.50.11.92]
7 55 ms 55 ms 52 ms bundle-ether5.pie-core1.perth.telstra.net [203.5
0.11.17]
8 52 ms 57 ms 53 ms gigabitethernet0-7-0-0.pthp-core01.perth.net.rea
ch.com [203.50.13.246]
9 107 ms 105 ms 102 ms i-0-5-4-0.skdi-core01.bx.telstraglobal.net [202.
84.143.181]
10 104 ms 103 ms 105 ms i-0-3-0-0.6ntp02.bi.telstraglobal.net [202.84.24
3.82]
11 115 ms 104 ms 104 ms 203.116.5.157
12 98 ms 98 ms 98 ms 203.118.15.186
13 100 ms 98 ms 97 ms an-ats-int11.starhub.net.sg [203.118.15.110]
14 100 ms 105 ms 113 ms sh2.eqx1.sg.vodien.com [203.116.246.18]
15 100 ms 102 ms 104 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 www.routerlogin.com [192.168.0.1]
2 5 ms 4 ms 4 ms 172.18.210.15
3 6 ms 4 ms 5 ms 172.18.68.141
4 8 ms 5 ms 5 ms bundle-ether4.lon-edge902.melbourne.telstra.net
[203.50.76.12]
5 12 ms 10 ms 9 ms bundle-ether11.exi-core10.melbourne.telstra.net
[203.50.11.113]
6 22 ms 23 ms 23 ms bundle-ether5.way-core4.adelaide.telstra.net [20
3.50.11.92]
7 53 ms 51 ms 51 ms bundle-ether5.pie-core1.perth.telstra.net [203.5
0.11.17]
8 48 ms 52 ms 50 ms tengige0-5-1-0.pthp-core01.perth.net.reach.com [
203.50.13.254]
9 105 ms 108 ms 113 ms 202.84.143.94
10 106 ms 102 ms 105 ms i-0-3-0-0.6ntp02.bi.telstraglobal.net [202.84.24
3.82]
11 111 ms 128 ms 101 ms 203.116.5.157
12 100 ms 105 ms 103 ms 203.118.15.186
13 97 ms 98 ms 98 ms an-ats-loc11.starhub.net.sg [203.118.15.238]
14 99 ms 98 ms 98 ms starhub-sg.sg.gs [203.116.39.138]
15 109 ms 109 ms 112 ms core-1.v31.sg1.sg.gs [203.175.175.21]
16 104 ms 103 ms 103 ms dns.sg.gs [203.175.175.203]

Trace complete.

Edited by Gryphorim, 19 June 2015 - 06:37 PM.

[Khan Ninah]

I live in Singapore so if these are truly the pings i am gonna get....I AM SO STOKED!

My ISP is MyRepublic.



Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=4ms TTL=59
Reply from 103.9.100.1: bytes=32 time=2ms TTL=59
Reply from 103.9.100.1: bytes=32 time=3ms TTL=59
Reply from 103.9.100.1: bytes=32 time=2ms TTL=59

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 = 4ms, Average = 2ms

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

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 = 3ms, Average = 3ms


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 2 ms 2 ms 2 ms 172.22.0.1
3 * * * Request timed out.
4 2 ms 3 ms 3 ms 40GE-103-6-148-45.myrepublic.com.sg [103.6.148.4
5]
5 3 ms 3 ms * eie1.eqx1.sg.vodien.com [202.79.197.178]
6 3 ms 3 ms 3 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 router.asus.com [192.168.1.1]
2 2 ms 1 ms 4 ms 172.22.0.1
3 * * * Request timed out.
4 2 ms 2 ms 2 ms 40GE-103-6-148-45.myrepublic.com.sg [103.6.148.4
5]
5 2 ms 2 ms 2 ms eqix-sg.sg.gs [202.79.197.159]
6 3 ms 9 ms 7 ms core-1.v30.sg3.sg.gs [203.175.175.53]
7 5 ms 4 ms 4 ms core-1.v41.sg1.sg.gs [203.175.175.129]
8 4 ms 3 ms 2 ms dns.sg.gs [203.175.175.203]

Trace complete.

Edited by Tenderballz, 19 June 2015 - 06:45 PM.

[Kiiyor]

Location: Melbourne, Australia
Provider: iiNet
Speed test:



Big ping test:

Spoiler

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

 
Ping statistics for 103.9.100.1:
	Packets: Sent = 493, Received = 492, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 130ms, Maximum = 173ms, Average = 134ms

Tracert's to 203.175.175.203

Spoiler

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  3	14 ms	11 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	11 ms	17 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	13 ms	12 ms	12 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   133 ms   132 ms   132 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   131 ms   131 ms   131 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	57 ms	49 ms	49 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   132 ms   130 ms   129 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
10   131 ms   131 ms   131 ms  eqix-sg.sg.gs [202.79.197.159]
11   135 ms   134 ms   133 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
12   133 ms   133 ms   132 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
13   132 ms   133 ms   131 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.

 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  3	11 ms	11 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	19 ms	11 ms	12 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	13 ms	12 ms	13 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   133 ms   132 ms   133 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   132 ms   133 ms   134 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	49 ms	49 ms	49 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   131 ms   131 ms   131 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
10   132 ms   130 ms   131 ms  eqix-sg.sg.gs [202.79.197.159]
11   133 ms   134 ms   141 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
12   133 ms   132 ms   135 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
13   131 ms   131 ms   131 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.

 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  3	12 ms	13 ms	12 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	11 ms	15 ms	11 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	12 ms	11 ms	11 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   132 ms   131 ms   132 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   132 ms   133 ms   131 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	49 ms	48 ms	50 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   131 ms   131 ms   129 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
10   130 ms   131 ms   132 ms  eqix-sg.sg.gs [202.79.197.159]
11   135 ms   131 ms   143 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
12   132 ms   135 ms   131 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
13   134 ms   132 ms   132 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.

 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  3	13 ms	12 ms	12 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	12 ms	10 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	11 ms	11 ms	14 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   132 ms   132 ms   133 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   133 ms   132 ms   132 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	53 ms	49 ms	50 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   130 ms   130 ms   131 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
10   133 ms   131 ms   131 ms  eqix-sg.sg.gs [202.79.197.159]
11   133 ms   133 ms   133 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
12   133 ms   131 ms   132 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
13   131 ms   131 ms   131 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.

 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  3	13 ms	12 ms	13 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	14 ms	11 ms	11 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	12 ms	13 ms	11 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   131 ms   140 ms   131 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   135 ms   133 ms   135 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	48 ms	49 ms	51 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   132 ms   131 ms   132 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
10   130 ms   135 ms   134 ms  eqix-sg.sg.gs [202.79.197.159]
11   134 ms   135 ms   133 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
12   132 ms   133 ms   134 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
13   134 ms   130 ms   134 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.

 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  3	13 ms	12 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	18 ms	11 ms	12 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	12 ms	11 ms	11 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   132 ms   133 ms   137 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   133 ms   131 ms   131 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	50 ms	51 ms	51 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   130 ms   132 ms   133 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
10   132 ms   131 ms   132 ms  eqix-sg.sg.gs [202.79.197.159]
11   134 ms   137 ms   143 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
12   132 ms   132 ms   132 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
13   154 ms   131 ms   130 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.

 
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
 
  3	11 ms	14 ms	12 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	11 ms	12 ms	13 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	12 ms	11 ms	17 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   132 ms   131 ms   130 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   137 ms   133 ms   133 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	49 ms	49 ms	52 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   130 ms   132 ms   130 ms  pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
10   130 ms   132 ms   131 ms  eqix-sg.sg.gs [202.79.197.159]
11   133 ms   132 ms   133 ms  core-1.v30.sg3.sg.gs [203.175.175.53]
12   133 ms   133 ms   131 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
13   132 ms   132 ms   132 ms  dns.sg.gs [203.175.175.203]
 
Trace complete.
 

Tracert's to 103.9.100.1

Spoiler

 
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
 
  3	11 ms	13 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	17 ms	11 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	12 ms	11 ms	13 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   132 ms   131 ms   131 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   136 ms   134 ms   132 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	48 ms	50 ms	48 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   132 ms   131 ms   133 ms  po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
10   131 ms   131 ms   131 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
11   132 ms   132 ms   135 ms  tl1.sg.vodien.com [103.9.100.1]
 
Trace complete.

 
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
 
  3	13 ms	11 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	13 ms	11 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	11 ms	12 ms	20 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   133 ms   131 ms   132 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   133 ms   133 ms   135 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	48 ms	50 ms	48 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   132 ms   131 ms   131 ms  po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
10   131 ms   133 ms   133 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
11   132 ms   133 ms   131 ms  tl1.sg.vodien.com [103.9.100.1]
 
Trace complete.

 
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
 
  3	12 ms	12 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	14 ms	12 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	12 ms	18 ms	14 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   133 ms   131 ms   134 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   133 ms   133 ms   133 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	49 ms	49 ms	48 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   134 ms   136 ms   135 ms  po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
10   131 ms   132 ms   131 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
11   132 ms   137 ms   133 ms  tl1.sg.vodien.com [103.9.100.1]
 
Trace complete.

 
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
 
  3	11 ms	12 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	11 ms	11 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	36 ms	12 ms	13 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   131 ms   131 ms   131 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   132 ms   138 ms   132 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	49 ms	48 ms	49 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   131 ms   131 ms   132 ms  po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
10   133 ms   130 ms   131 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
11   132 ms   131 ms   131 ms  tl1.sg.vodien.com [103.9.100.1]
 
Trace complete.

 
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
 
  3	11 ms	13 ms	11 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	12 ms	13 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	12 ms	12 ms	11 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   132 ms   132 ms   133 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   133 ms   133 ms   133 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	49 ms	48 ms	48 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   136 ms   131 ms   130 ms  po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
10   131 ms   131 ms   131 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
11   132 ms   132 ms   133 ms  tl1.sg.vodien.com [103.9.100.1]
 
Trace complete.

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
 
  3	11 ms	11 ms	12 ms  lo0.iin-tact-hfc-bal.bng1.mel4.iinet.net.au [203.215.7.246]
  4	12 ms	11 ms	12 ms  lo0.bng1.mel4.on.ii.net [150.101.32.44]
  5	17 ms	11 ms	12 ms  ae4.cr1.mel4.on.ii.net [150.101.33.106]
  6   132 ms   134 ms   133 ms  ae1.cr1.adl2.on.ii.net [150.101.33.41]
  7   132 ms   137 ms   132 ms  ae2.cr1.per4.on.ii.net [150.101.33.39]
  8	50 ms	55 ms	49 ms  ae0.cr1.per1.on.ii.net [150.101.34.171]
  9   131 ms   131 ms   132 ms  po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
10   131 ms   133 ms   132 ms  eie1.eqx1.sg.vodien.com [202.79.197.178]
11   132 ms   133 ms   132 ms  tl1.sg.vodien.com [103.9.100.1]
 
Trace complete.

[Delphino]

Geographic location: Melbourne, Australia
ISP: Internode

Ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=143ms TTL=55
Reply from 103.9.100.1: bytes=32 time=145ms TTL=55
Reply from 103.9.100.1: bytes=32 time=144ms TTL=57
Reply from 103.9.100.1: bytes=32 time=143ms 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 = 143ms, Maximum = 145ms, Average = 143ms

Traceroute 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 24 ms 25 ms 24 ms lns20.mel4.on.ii.net [150.101.212.44]
3 25 ms 24 ms 24 ms xe-0-3-2.cr1.mel4.on.ii.net [150.101.208.65]
4 143 ms 144 ms 144 ms ae1.cr1.adl2.on.ii.net [150.101.33.41]
5 143 ms 143 ms 144 ms ae2.cr1.per4.on.ii.net [150.101.33.39]
6 62 ms 62 ms 61 ms ae0.cr1.per1.on.ii.net [150.101.34.171]
7 143 ms 143 ms 142 ms pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
8 143 ms 143 ms 142 ms eie1.eqx1.sg.vodien.com [202.79.197.178]
9 144 ms 143 ms 144 ms tl1.sg.vodien.com [103.9.100.1]

MTR 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=144ms TTL=52
Reply from 203.175.175.203: bytes=32 time=143ms TTL=54
Reply from 203.175.175.203: bytes=32 time=144ms TTL=54
Reply from 203.175.175.203: bytes=32 time=144ms TTL=54

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

Traceroute 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 25 ms 25 ms 25 ms lns20.mel4.on.ii.net [150.101.212.44]
3 25 ms 25 ms 24 ms xe-0-3-2.cr1.mel4.on.ii.net [150.101.208.65]
4 143 ms 143 ms 144 ms ae1.cr1.adl2.on.ii.net [150.101.33.41]
5 144 ms 143 ms 144 ms ae2.cr1.per4.on.ii.net [150.101.33.39]
6 62 ms 63 ms 62 ms ae0.cr1.per1.on.ii.net [150.101.34.171]
7 143 ms 143 ms 143 ms po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
8 161 ms 144 ms 143 ms eqix-sg.sg.gs [202.79.197.159]
9 145 ms 144 ms 144 ms core-1.v30.sg3.sg.gs [203.175.175.53]
10 145 ms 153 ms 145 ms core-2.v41.sg1.sg.gs [203.175.175.130]
11 145 ms 144 ms 147 ms dns.sg.gs [203.175.175.203]

MTR 203.175.175.203

[Appogee]

Location: Middle East. My usual in-game ping here is 210ms.

For IP 103.9.100.1, the TTL is 53 but round trip time is 339ms.

For IP 203.175.175.203, the TTL is 55 but round trip time is 109ms.

Conclusion: use the second provider!

Edited by Appogee, 20 June 2015 - 06:27 AM.