Fibre Internet: My Republic/ViewQuest/Starhub/Singtel

[mmv]

I was wondering if anyone with the "Fiber service providers" in the subject line could perform a ping test to 3 different parts of the globe mentioned below. I find this to be one of the most accurate means (in my opinion) to test the "real" speed of the providers.

A ping test involves bringing up your "cmd" window (In Windows, select Start > Programs > Accessories > Command Prompt) and simply typing in "ping xxx.xx.xx.xxx". An average ping will show after the ping is complete.

Ping Test to 3 major regions:

Japan Data Center: 202.67.53.202
U.S.A Data Center: 184.107.107.176
Europe Data center: 209.130.141.243

If you could post your results along with the following I would really appreciate any help!

Provider:
Plan:
Lan/Wirless:
Japan:
USA:
Europe:

[Wd40]

Mine is not fibre. Its the cheapest 3MBPS Starhub broadband.

Here are my results:

1)Min 678ms Max 1356ms Avg 854ms
2)Min 289ms Max 421ms Avg 340ms
3)Min 317ms Max 511ms Avg 374ms

[mmv]

Thanks Wd40.

For your reference I am currently using Starhub MaxOnline fastest broadband speed service. Here are my results.

Japan: Min 88ms, Max 98ms, Avg 93ms.
USA: Min 281ms, Max 292ms, Avg 287ms.
EU: Min 320ms, Max 346ms, Avg 330ms.

[x9200]

I am on something called MaxOnline Express Plus and have the pings within 2% of your results.

[JR8]

I'm on some 'fibre' service or other, and it's no quicker than broadband was back in Europe.

[zzm9980]

Mine is not fibre. Its the cheapest 3MBPS Starhub broadband.

Here are my results:

1)Min 678ms Max 1356ms Avg 854ms
2)Min 289ms Max 421ms Avg 340ms
3)Min 317ms Max 511ms Avg 374ms

Those results are horrendous compared to X92's. Latency should not be affected so much by the amount of bandwidth (unless you're using all of it), but by your service provider's network. Were you running torrents at the or something? If not I suspect something is wrong with the last run to your place.

[zzm9980]

MyRepublic Pure (100 down/50 up) connected by ethernet to my router:

Japan
--- 202.67.53.202 ping statistics ---
33 packets transmitted, 33 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 197.499/198.884/199.742/0.495 ms

Europe
--- 209.130.141.243 ping statistics ---
15 packets transmitted, 15 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 258.934/277.160/288.179/9.575 ms

USA
--- 184.107.107.176 ping statistics ---
148 packets transmitted, 148 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 265.992/267.812/269.353/0.572 ms
---

You should also consider that Singtel, Starhub, and M1 force all HTTP and HTTPS traffic through their transparent caches. I get the impression you may be someone that will care about that. No way around it unless you tunnel your traffic.

[Wd40]

Mine is not fibre. Its the cheapest 3MBPS Starhub broadband.

Here are my results:

1)Min 678ms Max 1356ms Avg 854ms
2)Min 289ms Max 421ms Avg 340ms
3)Min 317ms Max 511ms Avg 374ms

Those results are horrendous compared to X92's. Latency should not be affected so much by the amount of bandwidth (unless you're using all of it), but by your service provider's network. Were you running torrents at the or something? If not I suspect something is wrong with the last run to your place.

Not sure, if I am missing something. But if you look at my figures other than Japan(the 1st one), the US and EU figures are pretty close to MMV's. So its not that bad after all, isn't it? Mine is the cheapest 3MBPS connection, not fibre, regular starhub cable broadband and on wifi. I spend $24 per month for internet which is I think 30% discounted because its a 24 month contract.

I wasn't running any torrent, but audio songs were streaming on another device(ipad).

[Wd40]

I just did the test again with nothing running:

Japan:
min:89ms max:94ms avg:91ms

US:
min:282ms max:286ms avg:284ms

EU:
min:316ms max:319ms avg:317ms

Wow! Big difference from last time.

[zzm9980]

I just did the test again with nothing running:

Japan:
min:89ms max:94ms avg:91ms

US:
min:282ms max:286ms avg:284ms

EU:
min:316ms max:319ms avg:317ms

Wow! Big difference from last time.

Yeah, that looks much better. Were you on wireless for the first one? Perhaps someone's phone was interrupting.

[Wd40]

I just did the test again with nothing running:

Japan:
min:89ms max:94ms avg:91ms

US:
min:282ms max:286ms avg:284ms

EU:
min:316ms max:319ms avg:317ms

Wow! Big difference from last time.

Yeah, that looks much better. Were you on wireless for the first one? Perhaps someone's phone was interrupting.

Yes, I am always on wifi.

[sundaymorningstaple]

Starhub - Max Infinity Platnium
Wireless
2045 hrs

Japan: Min 90ms, Max 94ms, Avg 92ms
US: Min 260ms, Max 265ms, Avg 262ms
Europe: Min 310ms, Max 312ms, Avg 310ms

Not sure how many other computers currently running, probably at least two others, normally streaming music or videos.

[mmv]

Appreciate everyone sending in the pings! So far it seems like there is not much difference. However, no one with "high end" fiber has posted as of yet. The main reason I am concerned is I connect to US servers a fair amount of the time. I was trying to get that number ~150ms if possible...

I had heard that "My Republic's Gamer Plan" apparently has separate routing. I just do not want to pay an extra $30 a month for something that make no difference on speed to international locations.

[zzm9980]

Appreciate everyone sending in the pings! So far it seems like there is not much difference. However, no one with "high end" fiber has posted as of yet. The main reason I am concerned is I connect to US servers a fair amount of the time. I was trying to get that number ~150ms if possible...

I had heard that "My Republic's Gamer Plan" apparently has separate routing. I just do not want to pay an extra $30 a month for something that make no difference on speed to international locations.

I think it will be impossible to get under 200ms to the US. My company has a huge amount of bandwidth and the best routing possible to the west coast of the US, but we do 175-180ms (see below).

I like to ping level3's DNS root in San Jose. You'll be hard pressed to find a better connected host with a fixed location (not GLSB) and an easy to remember IP:

--- 4.2.2.2 ping statistics ---
52 packets transmitted, 52 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 172.497/187.530/210.375/8.904 ms

So about ~180ms across the ocean. Give or take a few %.

You can even see here the two hops along the route before and after they hit the undersea cable:

ge-0-1-7-0.sngtp-dr2.ix.singtel.com (203.208.151.181) 1.770 ms
so-4-2-2-0.toknf-cr3.ix.singtel.com (203.208.173.106) 184.779 ms

MyRepublic has phenomenal customer service that's practically un-heard of here in Singapore, let alone Asia. I'm sure they would either run the tests you're asking us about and provide the honest results, or let you cancel the gamer plan if you're not happy with it. I also don't think it's separate routing, but just QoS.

[zzm9980]

Also if you're so worried about the US host, maybe you should look at the routing on that side. I did a traceroute and the routes are jacked long after we're in the US:

Code: Select all

5  165.21.12.68 (165.21.12.68)  8.298 ms  1.737 ms  1.594 ms
 6  203.208.190.21 (203.208.190.21)  1.774 ms  1.720 ms  1.827 ms
 7  203.208.153.241 (203.208.153.241)  2.375 ms  2.488 ms  2.369 ms
 8  ge-2-1-0-0.laxow-dr1.ix.singtel.com (203.208.171.10)  186.603 ms  186.567 ms  196.704 ms
 9  203.208.153.46 (203.208.153.46)  185.569 ms  185.695 ms
    te0-7-0-23.ccr22.lax04.atlas.cogentco.com (154.54.12.129)  198.988 ms
10  be2022.mpd22.lax01.atlas.cogentco.com (154.54.88.1)  190.938 ms
    be2020.ccr22.lax01.atlas.cogentco.com (154.54.88.17)  192.705 ms  193.052 ms
11  be2066.ccr22.iah01.atlas.cogentco.com (154.54.7.53)  222.810 ms
    be2068.mpd22.iah01.atlas.cogentco.com (154.54.7.157)  226.736 ms
    be2066.ccr22.iah01.atlas.cogentco.com (154.54.7.53)  222.523 ms
12  be2146.ccr22.dfw01.atlas.cogentco.com (154.54.25.242)  237.090 ms
    be2147.ccr22.dfw01.atlas.cogentco.com (154.54.27.18)  230.618 ms
    be2146.ccr22.dfw01.atlas.cogentco.com (154.54.25.242)  237.172 ms
13  be2010.ccr22.mci01.atlas.cogentco.com (154.54.46.217)  223.271 ms
    be2141.mpd22.mci01.atlas.cogentco.com (154.54.5.157)  226.673 ms
    be2010.ccr22.mci01.atlas.cogentco.com (154.54.46.217)  223.291 ms
14  be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82)  262.039 ms
    be2157.ccr22.ord01.atlas.cogentco.com (154.54.6.118)  236.961 ms
    be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82)  261.766 ms
15  be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6)  262.861 ms
    be2082.ccr22.yyz02.atlas.cogentco.com (154.54.28.10)  252.644 ms
    be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6)  262.853 ms
16  te7-1.mag02.yyz02.atlas.cogentco.com (154.54.40.166)  251.227 ms
    te7-1.mag01.yyz02.atlas.cogentco.com (154.54.40.178)  462.937 ms  459.209 ms

I get much better times to even Amazon's EC2 cloud in Northern California:

--- 54.215.xxx.xxx ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 181.247/184.601/187.668/2.629 ms