New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Lower? I think not. Anything under 300 is generally good. 200ms is as good as I've seen it.
Don~t think so ~
@william could probably help ~
Yes, but only barely.
FEA (Flag Europe Asia) has landing in UK and up to HK.
HE is on another (a combination of SeaMeWe-4 and an Asian cable) from Marseille (FR) and gets ~185ms from Paris to HK. Marseille HK is around 170ms alone.
This is a low quality route however.
NTT uses the same cable (or one on the same route now) and gets ~200ms.
Traditionally this route (suez canal) is one of the most fault issue ones as well, unlike US->Asia.
I almost manage 180ms (195 to be exact) from Amsterdam to my server with your in HK, but again the same Marseille-SG-HK HE route:
Well there is also TEA-2 and ERMC: http://teacable.com/en
^^ Bics: http://bics.com/sites/default/files/Global Map_0.pdf
Hetzner to/from whatever @randvegeta is hosting off of (hosthongkong) is 195ms. Seems like HHK to HE in Interxion Marseille gives 175ms though, so just under 180ms. Online.net is hosted quite close to that (~7ms), so that gives you an option on either end.
That's nice to know. In LT is get around 220ms and in the UK, depending on ISP, between 250 and 350 (but I only tested on crappy ADSL). I dont have any servers in NL or DE though. I've heard HE.net opened a direct route to Europe from HK but it seems to randomly switch to US at times. You guys see this?
Best I've seen personally was 195-200ms via RETN, which was great for me while I was in LT.
Which is an extremely expensive route western carriers tend to not use. You can guess why (hint: the route and the owner/operator).
He asked sub 180 ms, well this route has RTD of 140ms. But still the HE route seems to be the most cost effective.
azure should be able to do?but u need Multiple azure
Thank you so much for the very detail tips.
HE is really a high C/P way to connect HK to EU ...
I have already test some vps ,and get around 190ms ,over all its good ~
Thanks for the tip~ I only find one IDC using TEA ,it is 51dic in Hongkong ,The price is ok ,but they only offer 5m bandwidth ....
I try to connect it to moscow first , i get a 135ms ...which is pretty amazing ...
But i havent find any vps provider have direct route from Frankfurt to HK using TEA ~
I will try harder to find one .
HKG -> FRA 171ms
WOW , a pure HE IDC in HK. very nice~ already sent pm ,would like to buy one
Generally very bad choice. As noted HE to/in Asia is mostly horrible.
You could just use the HE tunnelbroker thingy for connection to europe on an otherwise well-connected vps in HK, would prevent you from having to go full HE.
Really bad, so we use IPLC -> He -> Softlayer -> Internet.
Thanks ~ i am now using tunnel broker to connect the two vps by ipv6 ..
the ping is about 190ms ,PL about 0.2% ,not bad ~