Howdy, Stranger!

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

Sign In Register

Quick Links


Categories

In this Discussion

› › OVH Asia-Pacific Network, latest latency optimizations - Page 12
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.

OVH Asia-Pacific Network, latest latency optimizations

1…67891012»

Comments

  • dgprasetyadgprasetya Member

    @Dazzle said:

    @dgprasetya said:
    @OVH_APAC

    from 139.99.23.174 to 103.131.119.17

    from 103.131.119.17 to 139.99.23.174

    long route and many RTO. Please advice. thanks

    What?

    Dah bagus itu

    normally 10-15 hop

  • CybrCybr Member

    @dgprasetya said:
    I can't reach the webserver, seems like network connection timeout.

    but the latency is normal:

    weird.. any advice?

    Fix the web server.

  • dgprasetyadgprasetya Member

    @Cybr said:

    @dgprasetya said:
    I can't reach the webserver, seems like network connection timeout.

    but the latency is normal:

    weird.. any advice?

    Fix the web server.

    no no no,.. the web server is ok.

    However this issue solved when i enable proxy dns Cloudflare.

  • sibapersibaper Member

    @dgprasetya said: However this issue solved when i enable proxy dns Cloudflare.

    so not related to OVH :|

    as usual it's DNS

  • dgprasetyadgprasetya Member

    I suspect this case is similar to Digitalocean vs Telkom Indonesia

    @sibaper said:

    @dgprasetya said: However this issue solved when i enable proxy dns Cloudflare.

    so not related to OVH :|

    as usual it's DNS

    ok thanks for your advices bro, but i think it's not DNS.

    dugaan sementara ip address kena rules firewall
    dan sebenarnya yg komplain adalah client saya, di sini hanya saya hanya memposisikan sebagai client, kmungkinan besar ip public client bukan 103.131.119.17

  • isunbejoisunbejo Member

    https://mobile.twitter.com/digitalocean/status/1278860119246241793

  • dgprasetyadgprasetya Member

    @isunbejo said:

    https://mobile.twitter.com/digitalocean/status/1278860119246241793

    sometimes, thinking because of that issue, but the last hop responding to me or clients. so, it's not network congestion.

  • comXyzcomXyz Member

    Does the Vietnam VPS have Vietnam IP address?
    https://www.ovhcloud.com/asia/vps/vps-vietnam/

  • OVH_APACOVH_APAC Member, Patron Provider

    Hi @comXyz, for Asia Pacific datacenters it will be either Singapore or Australia IP address

    Thanked by 1comXyz
  • bshbsh Member
    edited December 2021

    @OVH_APAC said:
    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.

    Please feel free to send us your traceroute results to our public mailing list for further investigations:

    Tracerouting from my ADVANCE-APAC-LE to another dedi from other provider, both are SG-based, I meet a malrouting at Zenlayer' hops, taking over 160ms latency from SG to SG then.

     1  2402:1f00:8001:12ff:ff:ff:ff:fd (2402:1f00:8001:12ff:ff:ff:ff:fd)  0.855 ms  0.493 ms  0.571 ms                      
 2  vl15.sgp1-sdagg6a-a72.sng.asia (2001:41d0:0:50::6c47:307d)  0.181 ms  vl15.sgp1-sdagg6b-a72.sng.asia (2001:41d0:0:50::6c47:307e)  0.345 ms  0.350 ms                                                                                         
 3  2001:41d0:0:50::3:434 (2001:41d0:0:50::3:434)  0.959 ms  2001:41d0:0:50::3:43a (2001:41d0:0:50::3:43a)  0.949 ms  2001:41d0:0:50::3:436 (2001:41d0:0:50::3:436)  0.965 ms                                                                    
 4  2001:41d0:0:50::7:16 (2001:41d0:0:50::7:16)  0.357 ms  2001:41d0:0:50::7:1a (2001:41d0:0:50::7:1a)  0.379 ms  2001:41d0:0:50::7:18 (2001:41d0:0:50::7:18)  0.392 ms                                                                          5  *  *  *                                                                                                              
 6  *  *  *                                                                                                              
 7  *  *  *                                                                                                              
 8  2001:df5:b800:bb00:0:2:1859:1 (2001:df5:b800:bb00:0:2:1859:1)  6.172 ms  18.189 ms  2.317 ms                         
 9  2602:ffe4:400:105::1 (2602:ffe4:400:105::1)  1.216 ms  1.304 ms  1.204 ms                                           
 10  2602:ffe4:400:127::2 (2602:ffe4:400:127::2)  5.242 ms  2602:ffe4:400:11d::2 (2602:ffe4:400:11d::2)  9.091 ms  6.424 ms                                                                                                                      
 11  2a0b:21c0:1000:2::1e (2a0b:21c0:1000:2::1e)  164.526 ms  164.355 ms  164.423 ms                                     
 12  2406:d500:12:299:: (2406:d500:12:299::)  167.165 ms  166.744 ms  167.233 ms                                         
 13  *  *^C
  • OVH_APACOVH_APAC Member, Patron Provider

    @bsh said:

    @OVH_APAC said:
    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.

    Please feel free to send us your traceroute results to our public mailing list for further investigations:

    Tracerouting from my ADVANCE-APAC-LE to another dedi from other provider, both are SG-based, I meet a malrouting at Zenlayer' hops, taking over 160ms latency from SG to SG then.

     1  2402:1f00:8001:12ff:ff:ff:ff:fd (2402:1f00:8001:12ff:ff:ff:ff:fd)  0.855 ms  0.493 ms  0.571 ms                      
 2  vl15.sgp1-sdagg6a-a72.sng.asia (2001:41d0:0:50::6c47:307d)  0.181 ms  vl15.sgp1-sdagg6b-a72.sng.asia (2001:41d0:0:50::6c47:307e)  0.345 ms  0.350 ms                                                                                         
 3  2001:41d0:0:50::3:434 (2001:41d0:0:50::3:434)  0.959 ms  2001:41d0:0:50::3:43a (2001:41d0:0:50::3:43a)  0.949 ms  2001:41d0:0:50::3:436 (2001:41d0:0:50::3:436)  0.965 ms                                                                    
 4  2001:41d0:0:50::7:16 (2001:41d0:0:50::7:16)  0.357 ms  2001:41d0:0:50::7:1a (2001:41d0:0:50::7:1a)  0.379 ms  2001:41d0:0:50::7:18 (2001:41d0:0:50::7:18)  0.392 ms                                                                          5  *  *  *                                                                                                              
 6  *  *  *                                                                                                              
 7  *  *  *                                                                                                              
 8  2001:df5:b800:bb00:0:2:1859:1 (2001:df5:b800:bb00:0:2:1859:1)  6.172 ms  18.189 ms  2.317 ms                         
 9  2602:ffe4:400:105::1 (2602:ffe4:400:105::1)  1.216 ms  1.304 ms  1.204 ms                                           
 10  2602:ffe4:400:127::2 (2602:ffe4:400:127::2)  5.242 ms  2602:ffe4:400:11d::2 (2602:ffe4:400:11d::2)  9.091 ms  6.424 ms                                                                                                                      
 11  2a0b:21c0:1000:2::1e (2a0b:21c0:1000:2::1e)  164.526 ms  164.355 ms  164.423 ms                                     
 12  2406:d500:12:299:: (2406:d500:12:299::)  167.165 ms  166.744 ms  167.233 ms                                         
 13  *  *^C

    Hello @bsh ,
    It looks like this provider is sending the traffic back via a longer route. Can you please send us a traceroute back (Provider to OVHcloud) to this website and will investigate further:
    http://traceroute.apac-tools.ovh
    Thank you!

  • bshbsh Member
    edited December 2021

    Hello @OVH_APAC
    Tracing back was done and sent to your website full results

    Here just a cut:
    4 2a02:6ea0:8:1190:5500::1 1.009 ms 0.949 ms 0.911 ms
    5 vl1101.par-eq5-core-1.cdn77.com 173.285 ms 173.188 ms 177.282 ms
    6 * *
    be101.par-th2-pb1-nc5.fr.eu 166.104 ms
    7 * * *
    8 2001:41d0:aaaa:100::3 172.810 ms
    2001:41d0:aaaa:100::7 175.860 ms
    2001:41d0:aaaa:100::5 176.826 ms
    9 *
    2001:41d0:aaaa:100::2 165.534 ms *
    10 * * *
    11 * * *
    12 * * *
    13 vl100.sgp-d2-a72.sng.asia 164.703 ms
    14 2001:41d0:0:50::7:1b 167.378 ms
    15 2001:41d0:0:50::3:439 166.835 ms 164.596 ms 164.530 ms
    16 vl15.sgp1-sdtor102a-n93.sng.asia 167.331 ms 165.045 ms 165.144 ms
    17 ***
    18 ***
    until
    64 ***

  • bshbsh Member

    Roundtrip time should be about 1ms now, after tout-de-suite intervention by Chacha Team :)
    Nice merci :)

  • skorupionskorupion Member, Host Rep

    got the free bf public cloud credits now time to redeem

  • nanankcorneringnanankcornering Member

    @OVH_APAC

    Any solution in regards with connectivity with Indonesia's Telin network?

  • CoffeeCoffee Member

    @nanankcornering said: Telin

    This is what stopping me to buy OVH SG VPS. We expect 20ms latency, not 200ms.

    IIRC the network issues arise at the beginning of Jan 2020. Started with Linode and DO, then followed by others. Some are fixed, most are still crap. Sometimes they fixed the latency but limit the bandwidth.
    Sometimes it's 20ms away with their Indihome network, but 250ms away with their Telkomsel network. Like what happened to Racks Central network.

    Telkom bangsat.

  • bshbsh Member

    @nanankcornering said:
    @OVH_APAC

    Any solution in regards with connectivity with Indonesia's Telin network?

    Look at this, it seems routed to San Jose, or no route then chosen to SJ, CA.
    Does your local ISP have a good peering yet?

  • LeftupLeftup Member

    If I'm not mistaken,
    I've read somewhere that previously OVH have peering with Telin/Telkom, then Telin want money from OVH or they will stop the peering.

    And current is the result, OVH route from Telin/Telkom is via lax/sjc last time I checked.

  • OhJohnOhJohn Member
    edited December 2021

    So when they write here https://network.status-ovhcloud.com/incidents/jjzpx30f08nh : "No impact is expected", they just mean: "All routes will go down". (Yeah, they are up again as of now, but had been down in this maintenance window).

  • bshbsh Member

    @OhJohn said:
    https://network.status-ovhcloud.com/incidents/jjzpx30f08nh :

    When I visit above site, Google warns me about mimic websites

  • OhJohnOhJohn Member

    Their old travaux.ovh.net redirects to that new status site. Seems as if google did not catch up?

  • bshbsh Member

    @OhJohn said:
    Their old travaux.ovh.net redirects to that new status site. Seems as if google did not catch up?

    Yep, maybe outdated or something AI :)

Sign In or Register to comment.