Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Advertise on LowEndTalk.com
OVH Singapore: Weird routing behavior
New on LowEndTalk? Please read our 'Community Rules' by clicking on it in the right menu!

OVH Singapore: Weird routing behavior

elos42elos42 Member
edited April 2018 in Providers

I have an OVH singapore VPS. I've had it for several months, and it's always shown a peculiar problem.

When you try to access the VPS from various points around the world, the traffic is often handed over to the nearest OVH network.

So, even though the server is in Singapore, and I try to traceroute to it from the US West Coast, the traffic will head to OVH, Canada. From there, it will go to OVH France and from there to Singapore. So, instead of a 170 ms latency, you end up with a 300 ms latency.

Similarly, if I try to ping the Singapore server from some of the ISPs in India, the traffic is handed over to OVH France, and from there, it comes to Singapore.

Does this have to do with

1) poor peering on part of OVH, or
2) some misconfiguration on their network that prevents other networks from 'seeing' the real location of the IP?
3) or some other explanation?

Can I somehow increase the 'visibility' of the IP from my end? I've changed the reverse IP from a '.eu' domain to an international domain. That didn't help.

PS: There are some others also that are similarly affected. But this seems to be the worst case.

Thanked by 1hanoi

Comments

  • YokedEggYokedEgg Member
    edited April 2018

    Edited this post like 3 times, can't read lol.

    That's how OVH works. They always keep it in house, but there's definitely something wrong with going from Canada to France, seems counterproductive.

    The safest bet is to go with either France or Canada, the powerhouse locations. The newer locations don't seem to be as good, usually because it's basically the same shit in a new location routed from an old location (such as OVH BHS -> OVH US).

    Yoked or Yolked? You decide.

  • MikeAMikeA Member, Provider

    Send an email on the respective regions OVH mailing list or try emailing one of the network/peering people on the corp.ovh addresses, you can find them around online or check on Twitter for them. They will fix issues like this most of the time when they are made aware. It is annoying but most of the old issues were fixed.

    ExtraVM - AMD Ryzen VPS starting @ $3.50
    USA (TX, VA, FL), CA, FR, UK, SGP, AU

  • tomletomle Member
    edited April 2018

    Hot potato routing, your isp will try to hand it over to OVH as soon as possible, which for NA means in Canada. From there, OVH routes it internally and have decided that they prefer to route it via the EU, which makes sense since they have capacity over the Atlantic but probably not over the Pacific.

    Try checking with them though.

    RIPE LIR: Contact me for ASN registrations/IPv6. No IPv4 space left.

  • rm_rm_ Member
    edited April 2018

    tomle said: which for NA means in Canada.

    Not necessarily, they have PoPs across the US too, including Seattle, Palo Alto or LA, going to which would make more sense from West Coast than to Canada.
    https://www.ovh.com/world/about-us/network.xml

    Thanked by 1FHR
  • Shot2Shot2 Member

    Enabling their permanent firewall (mitigation) may also force routing through Fr.

    Providing less than /64 means "we are clueless about IPv6". My geekbench results. I haz OneProv, Servarica, Veesp.

  • rm_rm_ Member
    edited April 2018

    Shot2 said: may also force routing through Fr.

    It shouldn't, there is now VAC in SG as well.

    In any case, better to report such issues to their "traceroute" mailing list.
    subscribe: [email protected]
    post: [email protected]

  • I brought this to the attention of their customer service. They took a couple of days to examine it, and finally suggested that I should host in France if I wanted better latency to India, and not in Singapore (or something to that effect.)

    Can they really fix it? I'll try emailing them again, but my hopes are not very high.

  • YokedEggYokedEgg Member
    edited April 2018

    @elos42 said:
    I brought this to the attention of their customer service. They took a couple of days to examine it, and finally suggested that I should host in France if I wanted better latency to India, and not in Singapore (or something to that effect.)

    Can they really fix it? I'll try emailing them again, but my hopes are not very high.

    They're actually on LET now, if you can get ahold of them. Maybe try tagging them. Might get less of a canned reply.

    Thanked by 1elos42

    Yoked or Yolked? You decide.

  • Thanked by 1elos42

    Founder, IDGAF Group. No Seriously! Subsidiaries: NeedSomeIT? - Tectrix Host - Tectrix Cloud - DYSH Labs. We consult on Anything related to tech!

  • But is that the default behavior for all ISPs? Do they try to hand over to the receiving ISP as soon as possible, without looking at the geolocation of the destination IP? Or is it the case here that the geolocation of the OVH IP is being shown as France (actually if you go by RIR and ASN, it is).

    Or do they hand over as soon as possible irrespective of such issues as a standard practice? I have another VPS on Tata. There too, I can see that the ISPs hand over to Tata as soon as possible, but not in Asia.
    In other words, if I'm tracerouting from the US or Europe, it is handed over to Tata immediately at those locations. But if I'm tracerouting from Japan, it's not taken to Europe or US, but to India and handed over. That's still acceptable. But in case of OVH, it goes from Asia to Europe to Asia (except from some originating ISPs who are correctly able to locate the destination IP in Singapore and take it all the way to Singapore and hand it over)

    @tomle said:
    Hot potato routing, your isp will try to hand it over to OVH as soon as possible, which for NA means in Canada. From there, OVH routes it internally and have decided that they prefer to route it via the EU, which makes sense since they have capacity over the Atlantic but probably not over the Pacific.

    Try checking with them though.

  • Thanks.
    If they can only fix this, I can move my production units to them easily.

  • OVH_APACOVH_APAC Member, Provider
    edited April 2018

    @elos42 said:
    I have an OVH singapore VPS. I've had it for several months, and it's always shown a peculiar problem.

    When you try to access the VPS from various points around the world, the traffic is often handed over to the nearest OVH network.

    So, even though the server is in Singapore, and I try to traceroute to it from the US West Coast, the traffic will head to OVH, Canada. From there, it will go to OVH France and from there to Singapore. So, instead of a 170 ms latency, you end up with a 300 ms latency.

    Similarly, if I try to ping the Singapore server from some of the ISPs in India, the traffic is handed over to OVH France, and from there, it comes to Singapore.

    Does this have to do with

    1) poor peering on part of OVH, or
    2) some misconfiguration on their network that prevents other networks from 'seeing' the real location of the IP?
    3) or some other explanation?

    Can I somehow increase the 'visibility' of the IP from my end? I've changed the reverse IP from a '.eu' domain to an international domain. That didn't help.

    PS: There are some others also that are similarly affected. But this seems to be the worst case.

    Hi @elos42,

    I agree, this routing is less than ideal and I'm sorry it has become an inconvenience.

    OVH is continuously working to improve the network, and this is especially relevant in countries where we are still relatively new. This network improvement includes working with local Internet providers to improve these fixed routes, which are often configured on the side of the ISP.

    I need to specify that my intention is not to put blame on others. Routing on the Internet is extremely complex, and sometimes these issues are tricky to resolve because of a poor peering connection from the ISP. Quite often, you can have a good route from OVH to the ISP but the journey back might end up taking a longer path. We're constantly in contact with local providers as we work towards a better integration with the global OVH network.

    Over the coming months we plan to add new equipment to improve routing in the Asia region, which will enable us to improve the routing rules. In the mean time, as an OVH customer we encourage you to raise a support ticket so we can collect further information, like your public IP address, that might help us troubleshoot this routing even further and hopefully find a short-term solution.

    You can also send a traceroute to our public mailing for further investigation:

    1. To run a traceroute on Linux, enter the following terminal command: traceroute your.ovh.vps.ip
    2. To run a traceroute on Windows, enter the following command line: tracert your.ovh.vps.ip
    3. Save the traceroute results
    4. Send a blank email to [email protected]
    5. Follow the instructions in the automated reply to sign up to the mailing list
    6. Send your traceroute results to [email protected] and the team will investigate

    If you aren't an OVH customer, simply replace OVH server IP address with "sgp.smokeping.ovh.net".

    Thanks for your patience.

    Your friends at OVH.

  • @OVH_APAC said:

    @elos42 said:
    I have an OVH singapore VPS. I've had it for several months, and it's always shown a peculiar problem.

    When you try to access the VPS from various points around the world, the traffic is often handed over to the nearest OVH network.

    So, even though the server is in Singapore, and I try to traceroute to it from the US West Coast, the traffic will head to OVH, Canada. From there, it will go to OVH France and from there to Singapore. So, instead of a 170 ms latency, you end up with a 300 ms latency.

    Similarly, if I try to ping the Singapore server from some of the ISPs in India, the traffic is handed over to OVH France, and from there, it comes to Singapore.

    Does this have to do with

    1) poor peering on part of OVH, or
    2) some misconfiguration on their network that prevents other networks from 'seeing' the real location of the IP?
    3) or some other explanation?

    Can I somehow increase the 'visibility' of the IP from my end? I've changed the reverse IP from a '.eu' domain to an international domain. That didn't help.

    PS: There are some others also that are similarly affected. But this seems to be the worst case.

    Hi @elos42,

    I agree, this routing is less than ideal and I'm sorry it has become an inconvenience.

    OVH is continuously working to improve the network, and this is especially relevant in countries where we are still relatively new. This network improvement includes working with local Internet providers to improve these fixed routes, which are often configured on the side of the ISP.

    I need to specify that my intention is not to put blame on others. Routing on the Internet is extremely complex, and sometimes these issues are tricky to resolve because of a poor peering connection from the ISP. Quite often, you can have a good route from OVH to the ISP but the journey back might end up taking a longer path. We're constantly in contact with local providers as we work towards a better integration with the global OVH network.

    Over the coming months we plan to add new equipment to improve routing in the Asia region, which will enable us to improve the routing rules. In the mean time, as an OVH customer we encourage you to raise a support ticket so we can collect further information, like your public IP address, that might help us troubleshoot this routing even further and hopefully find a short-term solution.

    You can also send a traceroute to our public mailing for further investigation:

    1. To run a traceroute on Linux, enter the following terminal command: traceroute your.ovh.vps.ip
    2. To run a traceroute on Windows, enter the following command line: tracert your.ovh.vps.ip
    3. Save the traceroute results
    4. Send a blank email to [email protected]
    5. Follow the instructions in the automated reply to sign up to the mailing list
    6. Send your traceroute results to [email protected] and the team will investigate

    If you aren't an OVH customer, simply replace OVH server IP address with "sgp.smokeping.ovh.net".

    Thanks for your patience.

    Your friends at OVH.

    See, now that didn't seem to be a canned response.

    Yoked or Yolked? You decide.

  • That reminds me, when I do traceroute from my VPS to my Indian IP, it goes 'direct' from Singapore to India. But when I ping from my IP to my VPS, it takes the France route.

    Apart from peering, could it be something to do with the fact that the Singapore IP is show to belong to Canada? Could this be forcing these non-peered ISPs to route the traffic westward?

    I have several VPSes in Singapore from providers like Linode, DO and Upcloud, but none of them show the IP as belonging to another continent. Usually, it's Australia or Singapore.

    Can you sort of transfer these IPs from ARIN to APNIC? I believe once these are transferred to APNIC, many of the ISPs will start looking up the IP address in Asia, instead of sending traffic abroad. I am no expert, but this seems logical.

    See the results from https://rdpguard.com/free-whois.aspx for your smokeping sgp address (and see Linode and Upcloud results below that).

    Notice that the 'country' field is shown as Canada in case of OVH.

    -------------- OVH -----------------------

    WHOIS Source: ARIN
    IP Address: 139.99.127.250
    Country: caCanada
    Network Name: OVH-CUST-6463783
    Owner Name: f1domain.com
    CIDR: 139.99.113.32/28
    From IP: 139.99.113.32
    To IP: 139.99.113.47
    Allocated: Yes
    Contact Name: OVH Singapore PTE. LTD
    Address: 6296 Ash Shuayb Al Balad Jaddah Makkah Saudi Arabia, Jaddah Makkah
    Email: [email protected]
    Abuse Email: [email protected]
    Phone: +1-855-684-5463
    Fax:

    NetRange: 139.99.0.0 - 139.99.255.255
    CIDR: 139.99.0.0/16
    NetName: HO-2
    NetHandle: NET-139-99-0-0-1
    Parent: NET139 (NET-139-0-0-0-0)
    NetType: Direct Allocation
    OriginAS:
    Organization: OVH Hosting, Inc. (HO-2)
    RegDate: 2016-09-09
    Updated: 2016-09-09
    Ref: https://whois.arin.net/rest/net/NET-139-99-0-0-1

    ------------------ Linode -----------------------

    WHOIS Source: RIPE NCC
    IP Address: 139.162.23.4
    Country: sgSingapore
    Network Name: LINODE-AP
    Owner Name: Linode, LLC
    CIDR:
    From IP: 139.162.0.1
    To IP: 139.162.31.255
    Allocated: Yes
    Contact Name: Thomas Asaro
    Address: 329 E. Jimmie Leeds Road, Suite A, Galloway, NJ 08205, USA
    Email:
    Abuse Email: [email protected]
    Phone: +16093807504
    Fax:

    inetnum: 139.162.0.1 - 139.162.31.255
    netname: LINODE-AP
    descr: Linode, LLC
    country: SG
    admin-c: TA2589-RIPE
    tech-c: LA538-RIPE
    status: LEGACY
    remarks: This block is used for static customer allocations
    remarks: Please send abuse reports to [email protected]
    mnt-by: LINODE-LEG-MNT
    created: 2015-01-31T05:10:06Z
    last-modified: 2015-01-31T05:10:54Z
    source: RIPE

    -------------UPCLOUD---------------------

    WHOIS Source: RIPE NCC
    IP Address: 94.237.65.58
    Country: sgSingapore
    Network Name: UPCLOUD-SG-SIN1-NET
    Owner Name:
    CIDR: 94.237.64.0/22
    From IP: 94.237.64.0
    To IP: 94.237.67.255
    Allocated: Yes
    Contact Name: UpCloud Ltd
    Address: Etelaranta 12, 00130 Helsinki, Finland
    Email: [email protected]
    Abuse Email: [email protected]
    Phone:
    Fax:

    inetnum: 94.237.64.0 - 94.237.67.255
    netname: UPCLOUD-SG-SIN1-NET
    country: SG
    admin-c: UPC-RIPE
    tech-c: UPC-RIPE
    status: ASSIGNED PA
    mnt-by: MNT-UPCLOUD
    created: 2017-03-09T13:43:02Z
    last-modified: 2017-03-09T13:43:02Z
    source: RIPE

    role: UpCloud Ltd
    address: Etelaranta 12
    address: 00130 Helsinki
    address: Finland
    e-mail: [email protected]
    abuse-mailbox: [email protected]
    nic-hdl: UPC-RIPE
    mnt-by: MNT-UPCLOUD
    admin-c: JP1584-RIPE
    created: 2013-05-14T13:13:07Z
    last-modified: 2017-07-03T10:56:27Z
    source: RIPE

    Thanked by 1aglodek
  • ClouviderClouvider Member, Provider

    @elos42 BGP doesn’t care about such parameters like geolocation. It’s not something you can configure in your route maps on any gear. Hence why it’s quite often useful to have the same set of carriers at all locations to ease these handover issues. It is however not possible when some of them are not present in the region like, I think might be in this case, making it harder (bot not impossible) to play the ball using the regular techniques.

    Clouvider Limited - Leading Hosting & Connectivity Partner || Dedicated Server Sale from £45/m - Our Latest LET Offer

    Cloud Web Hosting | SSD & SAS HA OnApp VPS | US, UK, NL & DE Dedicated Servers | Network Services | Colocation | Managed Services

  • @OVH_APAC just wanted to update that the weird routing affects only IPv4 traffic. The same machine that sends IPv4 traffic from India to France to get to Singapore gets a direct route from India to Singapore on IPv6.

    If you want to see this in action, spin up a VPS on DO Bangalore DC, do a traceroute to one of your IPv4 addresses in Singapore and then do one to the same instance, but this time using IPv6. You'll see that IPv6 goes directly.

  • Try a vps with leaseweb SGP if your target is India .

    It gives me consistently 60-95ms even on 3g/4g, and their bandwidth allowances are generous on 4GB ram plan (8TB IIRC)

    Thanked by 1Clouvider

    Tired of LET scams?
    A Moderated forum : https://talk.lowendspirit.com/

  • OVH_APACOVH_APAC Member, Provider

    @elos42,
    Thank you for the update and please note we have made some improvement on the route from DO Bangalore to OVH in Singapore.
    You may check this out directly here:
    http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS14061-APAC-BLR1-1
    Latency reduced from 200ms to **38 ms **.

    Our network is still relatively new in the Asia-Pacific region but is constantly evolving.
    OVH aims to improve it day after day by adding providers, capacity and new rules to reduce the latency.
    We are currently working with providers based in India and maybe in the near future, we will even add a PoP to better manage connections with these providers.

    Once again, we encourage you to raise a support ticket for routing issues so we can assist you quicker than a forum post.

    Hope this helps.

  • I think the main issue here is that West Coast USA -> SGP got routed thru EU...

    Just reproduced this on he.net looking glass:

    Looking_Glass_Hurricane_Electric_AS6939.png

  • @OVH_APAC If it's so easy to fix these things, can I suggest that you fix the routing with the following ISPs?

    1) Bharti Airtel
    2) Idea Cellular
    3) Vodafone.

    Connectivity with the largest ISP, Reliance Jio, is already working fine.

    These four account for about 96% of the consumer traffic.

  • OVH_APACOVH_APAC Member, Provider

    @klikli said:
    I think the main issue here is that West Coast USA -> SGP got routed thru EU...

    Just reproduced this on he.net looking glass:

    Looking_Glass_Hurricane_Electric_AS6939.png

    We did have an issue with the LAX -> SGP link on that day so that might have been bad timing. We have also added a new link (Singapore to San Jose) that should help. I tested using the he.net looking glass and I'm now getting 168ms.

    For more information about the network issue: http://status.ovh.net/?do=details&id=15331

    --

    @elos42 said:
    @OVH_APAC If it's so easy to fix these things, can I suggest that you fix the routing with the following ISPs?

    1) Bharti Airtel
    2) Idea Cellular
    3) Vodafone.

    Connectivity with the largest ISP, Reliance Jio, is already working fine.

    These four account for about 96% of the consumer traffic.

    We have contacted Bharti Airtel and Idea Cellular in order to improve the network with those providers but it may take some time to get that up and running. We have made some changes and are monitoring our existing connections to see if we can make any improvements.

    Please see:

    http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS55410-1

    Thanks

    Thanked by 1klikli
  • @OVH_APAC ref vodafone result, please note that most of the time, the traffic flows direct from OVH to the ISP, but takes weird routes from ISP to OVH.

  • hostdarehostdare Member, Provider

    1 > 139.99.127.252 (139.99.127.252) [AS16276] 0.099ms 0.145ms 0.115ms
    2 > 10.95.209.14 (10.95.209.14) [] 0.128ms 0.160ms 0.106ms
    3 > 10.75.248.4 (10.75.248.4) [
    ] 1.114ms 0.949ms 0.830ms
    4 > sin-gss1-bb1-a9.sng.asia (103.5.15.16) [AS16276] 1.093ms 1.071ms 0.837ms
    5 > tata.as6453.sng.asia (103.5.15.19) [AS16276] 0.496ms 3.740ms 4.399ms
    6 > if-ae-7-2.tcore2.LVW-Los-Angeles.as6453.net (64.86.252.36) [AS6453] 172.158ms 171.688ms 172.345ms
    7 > if-ge-11-0-0-4.mcore5.LAA-Los-Angeles.as6453.net (64.86.252.46) [AS6453] 171.561ms 171.523ms 171.718ms
    8 > 209.58.33.150 (209.58.33.150) [AS6453] 213.270ms 213.249ms 213.191ms
    9 > 218.248.235.217 (218.248.235.217) [AS9829] 215.560ms 217.350ms 215.606ms
    10 > 218.248.114.30 (218.248.114.30) [AS9829] 226.509ms 226.480ms 226.549ms
    11 > ns12.bsnl.in (218.248.240.209) [AS9829] 226.354ms 226.477ms 226.352ms

    why need to route through LA ?

    HostDare - One of the cheapest and coolest providers online! :) | Our premium unmanaged vps plans | Cheap Shared Hosting

  • OVH Sucks. Do not buy their service.

  • @murshed said:
    OVH Sucks. Do not buy their service.

    Correction: Anything not in Canada or France sucks. OVH itself is pretty good though and working through some growth pains (wouldn't recommend new locations ATM).

    Yoked or Yolked? You decide.

  • EdmondEdmond Member without signature

    @YokedEgg said:

    @murshed said:
    OVH Sucks. Do not buy their service.

    Correction: Anything not in Canada or France sucks. OVH itself is pretty good though and working through some growth pains (wouldn't recommend new locations ATM).

    I agree, OVH in their Canadian and French DCs are great, but anything else is terrible, they just depend on those DCs to route their internet, why don't I just use the Canada or France one if your routing via those ones anyway?

    I live in BC, Canada and OVH has a PoP (which they need to upgrade) in Seattle. Yet all the traffic goes to BHS first before anywhere else, there's no point for me to purchase any other location except the ones that actually have good peers to hand the traffic off to.

  • hanoihanoi Member
    edited April 2018

    Same here: Trace route to CloudFlare


    ~/pro# traceroute 104.27.128.209 traceroute to 104.27.128.209 (104.27.128.209), 30 hops max, 60 byte packets 1 139.99.96.1 (139.99.96.1) 0.192 ms 0.179 ms 0.172 ms 2 192.168.250.254 (192.168.250.254) 0.153 ms 0.147 ms 0.141 ms 3 10.29.193.62 (10.29.193.62) 0.203 ms 0.203 ms 0.214 ms 4 10.29.192.10 (10.29.192.10) 0.185 ms 0.212 ms 0.207 ms 5 10.133.2.24 (10.133.2.24) 0.445 ms 0.602 ms 0.718 ms 6 10.75.0.10 (10.75.0.10) 0.144 ms 10.75.0.8 (10.75.0.8) 0.220 ms 10.75.0.10 (10.75.0.10) 0.161 ms 7 10.75.248.4 (10.75.248.4) 0.751 ms 0.785 ms 10.75.248.2 (10.75.248.2) 0.904 ms 8 sin1-sgcs2-g1-nc5.sng.asia (103.5.15.224) 0.907 ms * * 9 cloudflare.mrs.franceix.net (37.49.232.29) 167.143 ms be10.mar-5-6k.fr.eu (178.33.100.254) 166.656 ms cloudflare.mrs.franceix.net (37.49.232.29) 167.203 ms 10 104.27.128.209 (104.27.128.209) 166.529 ms cloudflare.mrs.franceix.net (37.49.232.29) 167.274 ms 104.27.128.209 (104.27.128.209) 166.417 ms ~/pro# traceroute 104.28.1.133 traceroute to 104.28.1.133 (104.28.1.133), 30 hops max, 60 byte packets 1 139.99.96.1 (139.99.96.1) 0.163 ms 0.147 ms 0.140 ms 2 192.168.250.254 (192.168.250.254) 0.134 ms 0.127 ms 0.121 ms 3 10.29.193.62 (10.29.193.62) 0.154 ms 0.204 ms 0.199 ms 4 10.29.192.10 (10.29.192.10) 0.183 ms 10.29.192.12 (10.29.192.12) 0.181 ms 0.188 ms 5 10.133.2.24 (10.133.2.24) 0.526 ms 0.662 ms 0.760 ms 6 10.75.0.10 (10.75.0.10) 0.162 ms 10.75.0.8 (10.75.0.8) 0.177 ms 0.167 ms 7 10.75.248.4 (10.75.248.4) 1.168 ms 10.75.248.2 (10.75.248.2) 0.738 ms 0.818 ms 8 sin-sg1-bb1-a9.sng.asia (103.5.15.4) 1.196 ms sin1-sgcs2-g1-nc5.sng.asia (103.5.15.224) 0.857 ms sin-sg1-bb1-a9.sng.asia (103.5.15.4) 1.272 ms 9 sin-sg1-bb1-a9.sng.asia (103.5.15.4) 1.345 ms 13335.sgw.equinix.com (27.111.228.132) 0.643 ms 0.642 ms 10 104.28.1.133 (104.28.1.133) 0.500 ms 0.500 ms 13335.sgw.equinix.com (27.111.228.132) 0.634 ms
  • There are some other hosts too who have poor peering. But what I really hate about the OVH situation is that their hardware is too good to be wasted like this.

  • OVH_APACOVH_APAC Member, Provider

    @hanoi said:
    Same here: Trace route to CloudFlare


    ~/pro# traceroute 104.27.128.209 traceroute to 104.27.128.209 (104.27.128.209), 30 hops max, 60 byte packets 1 139.99.96.1 (139.99.96.1) 0.192 ms 0.179 ms 0.172 ms 2 192.168.250.254 (192.168.250.254) 0.153 ms 0.147 ms 0.141 ms 3 10.29.193.62 (10.29.193.62) 0.203 ms 0.203 ms 0.214 ms 4 10.29.192.10 (10.29.192.10) 0.185 ms 0.212 ms 0.207 ms 5 10.133.2.24 (10.133.2.24) 0.445 ms 0.602 ms 0.718 ms 6 10.75.0.10 (10.75.0.10) 0.144 ms 10.75.0.8 (10.75.0.8) 0.220 ms 10.75.0.10 (10.75.0.10) 0.161 ms 7 10.75.248.4 (10.75.248.4) 0.751 ms 0.785 ms 10.75.248.2 (10.75.248.2) 0.904 ms 8 sin1-sgcs2-g1-nc5.sng.asia (103.5.15.224) 0.907 ms * * 9 cloudflare.mrs.franceix.net (37.49.232.29) 167.143 ms be10.mar-5-6k.fr.eu (178.33.100.254) 166.656 ms cloudflare.mrs.franceix.net (37.49.232.29) 167.203 ms 10 104.27.128.209 (104.27.128.209) 166.529 ms cloudflare.mrs.franceix.net (37.49.232.29) 167.274 ms 104.27.128.209 (104.27.128.209) 166.417 ms ~/pro# traceroute 104.28.1.133 traceroute to 104.28.1.133 (104.28.1.133), 30 hops max, 60 byte packets 1 139.99.96.1 (139.99.96.1) 0.163 ms 0.147 ms 0.140 ms 2 192.168.250.254 (192.168.250.254) 0.134 ms 0.127 ms 0.121 ms 3 10.29.193.62 (10.29.193.62) 0.154 ms 0.204 ms 0.199 ms 4 10.29.192.10 (10.29.192.10) 0.183 ms 10.29.192.12 (10.29.192.12) 0.181 ms 0.188 ms 5 10.133.2.24 (10.133.2.24) 0.526 ms 0.662 ms 0.760 ms 6 10.75.0.10 (10.75.0.10) 0.162 ms 10.75.0.8 (10.75.0.8) 0.177 ms 0.167 ms 7 10.75.248.4 (10.75.248.4) 1.168 ms 10.75.248.2 (10.75.248.2) 0.738 ms 0.818 ms 8 sin-sg1-bb1-a9.sng.asia (103.5.15.4) 1.196 ms sin1-sgcs2-g1-nc5.sng.asia (103.5.15.224) 0.857 ms sin-sg1-bb1-a9.sng.asia (103.5.15.4) 1.272 ms 9 sin-sg1-bb1-a9.sng.asia (103.5.15.4) 1.345 ms 13335.sgw.equinix.com (27.111.228.132) 0.643 ms 0.642 ms 10 104.28.1.133 (104.28.1.133) 0.500 ms 0.500 ms 13335.sgw.equinix.com (27.111.228.132) 0.634 ms

    Hi @hanoi. We are currently in contact with CloudFlare, and we're trying to determine why they aren't making subnet 104.27.128.0/20 available to OVH in Singapore. Stay tuned.

  • OVH_APACOVH_APAC Member, Provider

    @OVH_APAC said:

    @klikli said:
    I think the main issue here is that West Coast USA -> SGP got routed thru EU...

    Just reproduced this on he.net looking glass:

    Looking_Glass_Hurricane_Electric_AS6939.png

    We did have an issue with the LAX -> SGP link on that day so that might have been bad timing. We have also added a new link (Singapore to San Jose) that should help. I tested using the he.net looking glass and I'm now getting 168ms.

    For more information about the network issue: http://status.ovh.net/?do=details&id=15331

    --

    @elos42 said:
    @OVH_APAC If it's so easy to fix these things, can I suggest that you fix the routing with the following ISPs?

    1) Bharti Airtel
    2) Idea Cellular
    3) Vodafone.

    Connectivity with the largest ISP, Reliance Jio, is already working fine.

    These four account for about 96% of the consumer traffic.

    We have contacted Bharti Airtel and Idea Cellular in order to improve the network with those providers but it may take some time to get that up and running. We have made some changes and are monitoring our existing connections to see if we can make any improvements.

    Please see:

    http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS55410-1

    Thanks

    @elos42. We looked into it and we improved the peering link to Airtel. You can see the difference here: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS24560

    Thanked by 1elos42
  • hanoihanoi Member
    edited April 2018

    Dear @OVH_APAC, 2 hours ago, suddenly, you guys re-routed connection to FPT( one of 3 largest ISP in Vietnam) with unaccepted low latency & lost packets

    Resolver: Received error response 2. (server failure)er of fields   quit
                                                                                                                                                           Packets               Pings
     Host                                                                                                                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. 139.99.0.0/17      139.99.96.1                                                                                                                    0.0%    45    0.0   0.1   0.0   0.3   0.0
     2. ???                192.168.250.254                                                                                                                0.0%    45    0.1   0.1   0.0   0.4   0.0
     3. ???                10.29.193.62                                                                                                                   0.0%    45    0.2   0.2   0.1   0.4   0.0
     4. ???                10.29.192.10                                                                                                                   0.0%    45    0.2   0.3   0.1   4.2   0.6
     5. ???                10.133.2.24                                                                                                                    0.0%    45    0.5   0.7   0.4   4.8   0.8
     6. ???                10.75.0.8                                                                                                                      0.0%    45    0.2   0.2   0.1   0.4   0.0
     7. ???                10.75.248.2                                                                                                                    0.0%    45    0.7   0.9   0.6   1.2   0.0
     8. 103.5.12.0/22      sin1-sgcs2-g2-nc5.sng.asia                                                                                                     0.0%    44    1.1   1.0   0.6   1.3   0.0
     9. 103.5.12.0/22      sin-gss1-bb1-a9.sng.asia                                                                                                       0.0%    44    1.1   1.2   0.9   3.4   0.3
    10. 103.5.12.0/22      sjo-sv5-bb1-a9.ca.us                                                                                                           0.0%    44  160.2 160.4 160.1 162.6   0.3
    11. 198.27.64.0/18     be100-1365.lax-la1-bb1-a9.ca.us                                                                                                0.0%    44  173.0 173.3 173.0 173.8   0.0
    12. ???                fpt-telecom.as18403.any2ix.coresite.com                                                                                       50.0%    44  306.2 305.8 304.2 308.5   0.8
    13. 118.69.163.0/24    118.69.163.58                                                                                                                 46.5%    44  306.1 305.6 302.8 307.8   1.1
    14. 118.69.240.0/20    118.69.253.213                                                                                                                36.4%    44  305.1 304.9 298.7 322.9   3.7
    15. 42.116.255.0/24    42.116.255.138                                                                                                                44.2%    44  306.7 305.8 297.6 309.6   2.1
    16. 118.69.135.0/24    118.69.135.180                                                                                                                36.4%    44  303.6 305.7 303.3 311.3   1.5
    

    Some days ago, it was routed via NTT and still good until now

    Host Loss% Snt Last Avg Best Wrst StDev
    1. 139.99.0.0/17 139.99.96.1 0.0% 57 6.8 0.9 0.0 14.1 2.9
    2. ??? 192.168.250.254 0.0% 57 0.1 0.2 0.0 0.4 0.0
    3. ??? 10.29.193.62 0.0% 57 0.5 1.0 0.2 13.0 2.5
    4. ??? 10.29.192.10 0.0% 57 0.6 0.4 0.2 0.7 0.0
    5. ??? 10.133.2.24 0.0% 56 0.8 0.7 0.4 0.9 0.0
    6. ??? 10.75.0.8 0.0% 56 0.3 0.4 0.2 0.6 0.0
    7. ??? 10.75.248.2 0.0% 56 1.1 1.1 0.8 1.7 0.0
    8. 103.5.12.0/22 sin-sg1-bb1-a9.sng.asia 0.0% 56 3.2 2.1 0.9 26.4 3.3
    9. 103.5.12.0/22 ntt.as2914.sng.asia 0.0% 56 0.8 2.3 0.6 25.7 4.4
    10. 129.250.0.0/16 ae-4.r01.sngpsi07.sg.bb.gin.ntt.net 0.0% 56 0.9 1.0 0.7 1.5 0.0
    11. 129.250.0.0/16 ae-4.a00.sngpsi05.sg.bb.gin.ntt.net 0.0% 56 5.4 4.4 0.9 26.4 4.7
    12. 129.250.0.0/16 ae-7.r00.sngpsi05.sg.bb.gin.ntt.net 0.0% 56 1.4 1.1 0.8 1.4 0.0
    13. 116.51.16.0/20 ae-0.vodafone.sngpsi05.sg.bb.gin.ntt.net 0.0% 56 1.0 0.9 0.7 2.6 0.2
    14. 195.2.0.0/19 ae5-xcr1.hke.cw.net 0.0% 56 36.2 225.2 36.1 10610 1413.
    15. 213.185.192.0/19 fpt-gw-hke.cw.net 0.0% 56 43.6 44.3 43.3 61.9 3.3
    16. 118.69.132.0/24 118.69.132.50 0.0% 56 47.3 49.6 47.0 62.8 5.2
    17. 118.69.163.0/24 118.69.163.78 0.0% 56 47.3 48.1 47.0 74.5 4.1
    18. 118.69.132.0/24 118.69.132.132 0.0% 56 62.6 49.2 47.0 63.9 4.8
    19. 118.69.240.0/20 118.69.253.209 0.0% 56 47.1 47.6 47.0 65.3 2.5
    20. 42.116.255.0/24 42.116.255.134 0.0% 56 60.6 55.6 47.7 63.9 6.3
    21. 118.69.135.0/24 118.69.135.180 0.0% 56 59.0 48.0 47.1 60.4 2.7
    

    Please don't test your code in production

  • OVH_APACOVH_APAC Member, Provider

    @murshed said:
    OVH Sucks. Do not buy their service.

    @murshed. We apologise if we've let you down in the past. Happy to discuss your specific issue to see how we can improve :)

  • @OVH_APAC said:

    @murshed said:
    OVH Sucks. Do not buy their service.

    @murshed. We apologise if we've let you down in the past. Happy to discuss your specific issue to see how we can improve :)

    very slow ticket reply.no one help me provision my vps.still no one.I wait one day

  • edited April 2018

    Maybe it's an edge case with the peering of your provider. At least for the west coast. When I had an OVH dedi in SG, the west coast stuff would go across the Pacific so it was not bad. Less than 200ms. But the Chicago stuff would go across the Atlantic and through Europe and was at least 300-400ms as I recall.

  • hanoihanoi Member
    edited April 2018

    Seem OVH restored connection to FPT Vietnam via NTT. Thanks @OVH_APAC.
    And please do NOT play this game again.

    Thanked by 1geodirk
  • OVH_APACOVH_APAC Member, Provider
    edited April 2018

    @hanoi said:
    Dear @OVH_APAC, 2 hours ago, suddenly, you guys re-routed connection to FPT( one of 3 largest ISP in Vietnam) with unaccepted low latency & lost packets

    Resolver: Received error response 2. (server failure)er of fields   quit
                                                                                                                                                           Packets               Pings
     Host                                                                                                                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. 139.99.0.0/17      139.99.96.1                                                                                                                    0.0%    45    0.0   0.1   0.0   0.3   0.0
     2. ???                192.168.250.254                                                                                                                0.0%    45    0.1   0.1   0.0   0.4   0.0
     3. ???                10.29.193.62                                                                                                                   0.0%    45    0.2   0.2   0.1   0.4   0.0
     4. ???                10.29.192.10                                                                                                                   0.0%    45    0.2   0.3   0.1   4.2   0.6
     5. ???                10.133.2.24                                                                                                                    0.0%    45    0.5   0.7   0.4   4.8   0.8
     6. ???                10.75.0.8                                                                                                                      0.0%    45    0.2   0.2   0.1   0.4   0.0
     7. ???                10.75.248.2                                                                                                                    0.0%    45    0.7   0.9   0.6   1.2   0.0
     8. 103.5.12.0/22      sin1-sgcs2-g2-nc5.sng.asia                                                                                                     0.0%    44    1.1   1.0   0.6   1.3   0.0
     9. 103.5.12.0/22      sin-gss1-bb1-a9.sng.asia                                                                                                       0.0%    44    1.1   1.2   0.9   3.4   0.3
    10. 103.5.12.0/22      sjo-sv5-bb1-a9.ca.us                                                                                                           0.0%    44  160.2 160.4 160.1 162.6   0.3
    11. 198.27.64.0/18     be100-1365.lax-la1-bb1-a9.ca.us                                                                                                0.0%    44  173.0 173.3 173.0 173.8   0.0
    12. ???                fpt-telecom.as18403.any2ix.coresite.com                                                                                       50.0%    44  306.2 305.8 304.2 308.5   0.8
    13. 118.69.163.0/24    118.69.163.58                                                                                                                 46.5%    44  306.1 305.6 302.8 307.8   1.1
    14. 118.69.240.0/20    118.69.253.213                                                                                                                36.4%    44  305.1 304.9 298.7 322.9   3.7
    15. 42.116.255.0/24    42.116.255.138                                                                                                                44.2%    44  306.7 305.8 297.6 309.6   2.1
    16. 118.69.135.0/24    118.69.135.180                                                                                                                36.4%    44  303.6 305.7 303.3 311.3   1.5
    

    Some days ago, it was routed via NTT and still good until now

    Host Loss% Snt Last Avg Best Wrst StDev
    1. 139.99.0.0/17 139.99.96.1 0.0% 57 6.8 0.9 0.0 14.1 2.9
    2. ??? 192.168.250.254 0.0% 57 0.1 0.2 0.0 0.4 0.0
    3. ??? 10.29.193.62 0.0% 57 0.5 1.0 0.2 13.0 2.5
    4. ??? 10.29.192.10 0.0% 57 0.6 0.4 0.2 0.7 0.0
    5. ??? 10.133.2.24 0.0% 56 0.8 0.7 0.4 0.9 0.0
    6. ??? 10.75.0.8 0.0% 56 0.3 0.4 0.2 0.6 0.0
    7. ??? 10.75.248.2 0.0% 56 1.1 1.1 0.8 1.7 0.0
    8. 103.5.12.0/22 sin-sg1-bb1-a9.sng.asia 0.0% 56 3.2 2.1 0.9 26.4 3.3
    9. 103.5.12.0/22 ntt.as2914.sng.asia 0.0% 56 0.8 2.3 0.6 25.7 4.4
    10. 129.250.0.0/16 ae-4.r01.sngpsi07.sg.bb.gin.ntt.net 0.0% 56 0.9 1.0 0.7 1.5 0.0
    11. 129.250.0.0/16 ae-4.a00.sngpsi05.sg.bb.gin.ntt.net 0.0% 56 5.4 4.4 0.9 26.4 4.7
    12. 129.250.0.0/16 ae-7.r00.sngpsi05.sg.bb.gin.ntt.net 0.0% 56 1.4 1.1 0.8 1.4 0.0
    13. 116.51.16.0/20 ae-0.vodafone.sngpsi05.sg.bb.gin.ntt.net 0.0% 56 1.0 0.9 0.7 2.6 0.2
    14. 195.2.0.0/19 ae5-xcr1.hke.cw.net 0.0% 56 36.2 225.2 36.1 10610 1413.
    15. 213.185.192.0/19 fpt-gw-hke.cw.net 0.0% 56 43.6 44.3 43.3 61.9 3.3
    16. 118.69.132.0/24 118.69.132.50 0.0% 56 47.3 49.6 47.0 62.8 5.2
    17. 118.69.163.0/24 118.69.163.78 0.0% 56 47.3 48.1 47.0 74.5 4.1
    18. 118.69.132.0/24 118.69.132.132 0.0% 56 62.6 49.2 47.0 63.9 4.8
    19. 118.69.240.0/20 118.69.253.209 0.0% 56 47.1 47.6 47.0 65.3 2.5
    20. 42.116.255.0/24 42.116.255.134 0.0% 56 60.6 55.6 47.7 63.9 6.3
    21. 118.69.135.0/24 118.69.135.180 0.0% 56 59.0 48.0 47.1 60.4 2.7
    

    Please don't test your code in production

    Hi @hanoi. Thanks for raising this issue. We're working on it and the situation has improved already:

    From 192ms to… 47

    HOST: sgp Loss% Snt Last Avg Best Wrst StDev
    1.|-- 139.99.127.252 0.0% 10 0.2 0.2 0.1 0.3 0.0
    2.|-- 10.95.209.14 0.0% 10 0.2 0.2 0.2 0.3 0.0
    3.|-- 10.75.248.4 0.0% 10 1.0 1.0 0.8 1.2 0.0
    4.|-- sin1-sgcs2-g1-nc5.sng.asi 0.0% 10 0.8 1.0 0.8 1.6 0.0
    5.|-- sin-sg1-bb1-a9.sng.asia 0.0% 10 1.3 1.8 1.1 3.5 0.7
    6.|-- ntt.as2914.sng.asia 0.0% 10 1.0 0.8 0.7 1.1 0.0
    7.|-- ae-3.r01.sngpsi07.sg.bb.g 0.0% 10 0.9 0.8 0.8 1.0 0.0
    8.|-- ae-4.a00.sngpsi05.sg.bb.g 0.0% 10 1.2 1.3 0.9 1.7 0.0
    9.|-- ae-7.r00.sngpsi05.sg.bb.g 0.0% 10 0.9 0.9 0.8 1.0 0.0
    10.|-- ae-0.vodafone.sngpsi05.sg 0.0% 10 164.3 164.2 164.1 164.4 0.0
    11.|-- ae5-xcr1.hke.cw.net 0.0% 10 195.9 196.1 195.8 197.7 0.3
    12.|-- ftp-gw.hke.cw.net 0.0% 10 42.2 42.2 42.1 42.3 0.0
    13.|-- 118.69.132.50 0.0% 10 48.1 46.8 46.5 48.1 0.3
    14.|-- 118.69.163.78 0.0% 10 46.6 46.5 46.5 46.6 0.0
    15.|-- 118.69.132.132 0.0% 10 46.6 46.6 46.5 46.7 0.0
    16.|-- 118.69.253.211 0.0% 10 46.6 46.7 46.5 47.4 0.0
    17.|-- 118.69.125.150 0.0% 10 47.6 47.5 47.3 47.9 0.0
    18.|-- 118.69.135.180 0.0% 10 46.8 47.2 46.7 51.1 1.2

    Thanked by 1hanoi
  • Please see if you can also optimize the route to 66.249.79.66. That is Google, somewhere on the US West Coast. Most hosts take 180 ms. You are currently taking 240 ms.

  • elos42elos42 Member
    edited April 2018

    Also note that traffic from Google crawlers from the US West Coast seem to be going via Canada & Europe to your Singapore center. Not all the time, but, say about half the time. While the direct route is 240, the indirect route is 450 ms or thereabouts.

Sign In or Register to comment.