All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
OVH Asia-Pacific Network, latest latency optimizations
Over a year ago, OVH opened up shop in the Asia-Pacific region with 2 datacenters: Singapore (SG) and Sydney (AU).
We are continuously working on improving our network by adding providers, capacity and new rules to reduce the latency.
Below are some of the latest improvements done in the Asia-Pacific region:
- Singapore <> Sydney: is now on SeaMeWe-3 cable -> We have much more direct path (before 144ms now down to 88ms)
- Sydney <> Europe is now routed through Singapore (before via US) -> Better latency (around 35ms less)
- Transit Singapore : we now have TATA and NTT connected to 2 differents POPs (GSS1 & SG1) -> This ensures a better redundancy
We have also improved the routing to several locations (latest improvements below):
- China – China Telecom: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4809 (before 220ms down to 36ms)
- Vietnam: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS7602
- Indonesia: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4761
- Philippines: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS9658
- India – Amazon: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS16509-ap-south-1
- Thailand: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4765
Would like to see some improvements on the OVH Network?
Please feel free to send us your traceroute results to our public mailing list for further investigations:
- To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
- To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server IP)
- Save the traceroute results
- Send a blank email to [email protected]
- Follow the instructions in the automated reply to sign up to the mailing list
- Send your traceroute results to [email protected] and the team will investigate
(use "sgp.smokeping.ovh.net" for Singapore Datacenter or “syd.smokeping.ovh.net" for the Sydney Datacenter)
OVH Tools:
- Looking Glass: https://lg.ovh.net
- Singapore smokeping: http://sgp.smokeping.ovh.net/smokeping?target=APAC
- Sydney smokeping: http://syd.smokeping.ovh.net/smokeping?target=APAC
- Network status: http://weathermap.ovh.net/#apac
WHO ARE WE?
OVH (https://www.ovh.com) is a global hyper-scale cloud provider that offers innovative products and services focusing on private, public and hybrid cloud, and bare metal (dedicated servers).
It offers businesses a benchmark for value and performance in the sector.
Founded in 1999, the group manages and maintains 28 datacentres across 4 continents, deploys its own global fibre optic network, and has a full control over the supply chain
(from server manufacturing and in-house maintenance of its infrastructure right down to customer support).
OVH provides simple, powerful tools for businesses, revolutionising the way that more than 1 million customers work across the globe.
Respect for individuals' right to privacy and equal access to new technologies are central to the company's values.
For OVH, "Innovation is Freedom".
Comments
I have sent multiple time , email to [email protected] in the past regrading issue i am having but lets post it here also ,
PTCL , major isp in Pakistan having million users . already using SeaMeWe-3 .
Traceroute
here is to leaseweb Sinapore
From my internet connection (Indosat, Indonesia)
in Shenzhen China
From a 100Mbit line at my office (in the Netherlands, isp KPN:
Pinging sgp.smokeping.ovh.net [139.99.127.250] with 32 bytes of data: Reply from 139.99.127.250: bytes=32 time=190ms TTL=53 Reply from 139.99.127.250: bytes=32 time=191ms TTL=53 Reply from 139.99.127.250: bytes=32 time=190ms TTL=53 Reply from 139.99.127.250: bytes=32 time=190ms TTL=53
Ping statistics for 139.99.127.250: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 190ms, Maximum = 191ms, Average = 190ms
From a 10Gbps server @ i3D/SmartDC Rotterdam, the Netherlands:
root@srv4-rotterdam:~# ping sgp.smokeping.ovh.net PING sgp.smokeping.ovh.net (139.99.127.250) 56(84) bytes of data. From sgp.smokeping.ovh.net (139.99.127.250) icmp_seq=1 Destination Port Unreachable 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=2 ttl=50 time=187 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=3 ttl=50 time=187 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=4 ttl=50 time=186 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=5 ttl=50 time=187 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=6 ttl=50 time=187 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=7 ttl=50 time=187 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=8 ttl=50 time=187 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=9 ttl=50 time=187 ms 64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=10 ttl=50 time=187 ms --- sgp.smokeping.ovh.net ping statistics --- 10 packets transmitted, 9 received, +1 errors, 10% packet loss, time 9008ms rtt min/avg/max/mdev = 186.965/187.089/187.178/0.066 ms
ovh not peering with my isp biznetnetworks ?
latency normal for indonesia < > sg arround 15ms
Hope you guys are doing this as well :-)
Still weird routing for Sydney location.
Pretty improved routing fro Singapore location.
Tracing via Telkom, Indonesia (AS7713)
Hetzner FSN
Choopa NJ
guangzhou city , guangdong province , China telecom
About the same as it always was from LA and Chicago. It's not great but not bad either.
From Mumbai, India, Syscon Infoway Private Limited (SIPL) Sydney seems to be having very odd routing as my ISP has premium mix of Asian Providers (Tata/Airtel).
Mumbai(SIPL) -> Mumbai(Tata) -> Marseille(Tata) -> Paris(Tata) -> France(OVH) -> Singapore (OVH) -> Australia (OVH)
@FredQc do you believe there's anything wrong with your traces? If not, why post them. They didn't ask to just post random traceroutes where the route is okay. And yours seem more than fine.
I find them useful handy to get an idea of what to expect...
To be pedantic they didn't ask people to post in the first place. They asked people to send them to their mailing list.
WTF. 500ms from HK. Routing via France? WTF?
and
From Bangladesh (Link 3 - AS23688)
"Send your traceroute results to [email protected] and the team will investigate"
We got some pretty interesting trace route here.
sgp.smokeping.ovh.net:
syd.smokeping.ovh.net:
Latency to China CN2 (AS4809) is 36ms, that's good.
However who can afford CN2 premium?
All other results to Chinese endpoints look terrible.
Mailing lists are the fastest and most reliable way to get support.
And now retards invaded the mailing list, posting traces with 250ms from Romania of all places and 188ms from Hetzner without any comment or explanation. Both are normal (the first one caused by ISP having 60ms before it even gets to Frankfurt), but I have no idea what the poster had in mind, maybe it's to congratulate OVH on having good routes already in place, or something.
I like how it started as a promo post and turned into this
Good job OVH
They want to have their network improved they should be happy to accept support in any form.
OVH dont regard mainland China as their target market. Also, you can buy CN2 VPS from CloudIPLC.
Thank you all for your comments. The aim is to improve the network, so we keen to get all the feedback we can.
The best way to get in contact with us is through the mailing list. Please send the traceroute results to [email protected] and the team will investigate. (See the original post to find out how to subscribe)
Today we made 2 more changes improving the latency in Hong-Kong (http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS17444) and Taiwan (http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS3462)
@openos If you can provide a traceroute we will see what we can do.
from AS17974
From ISP : MyRepublic Indonesia ( AS63859 )
To sgp.smokeping.ovh.net
To syd.smokeping.ovh.net