Howdy, Stranger!

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


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

OVH_APACOVH_APAC Member, Patron Provider
edited May 2018 in Providers

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):

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:

  1. To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
  2. To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server 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

(use "sgp.smokeping.ovh.net" for Singapore Datacenter or “syd.smokeping.ovh.net" for the Sydney Datacenter)

OVH Tools:

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".

«13456712

Comments

  • karanchookaranchoo Member
    edited May 2018

    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 .

    Pinging sgp.smokeping.ovh.net [139.99.127.250] with 32 bytes of data:
    Reply from 139.99.127.250: bytes=32 time=420ms TTL=33
    Reply from 139.99.127.250: bytes=32 time=589ms TTL=33
    Reply from 139.99.127.250: bytes=32 time=503ms TTL=33
    Reply from 139.99.127.250: bytes=32 time=509ms TTL=33
    Reply from 139.99.127.250: bytes=32 time=504ms TTL=33
    Reply from 139.99.127.250: bytes=32 time=583ms TTL=33
    
    Ping statistics for 139.99.127.250:
        Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 420ms, Maximum = 589ms, Average = 518ms
    

    Traceroute

      Tracing route to sgp.smokeping.ovh.net [139.99.127.250] over a maximum of 30 hops:
    
      1     9 ms    <1 ms    <1 ms  192.168.10.1
      2    15 ms     8 ms     4 ms  192.168.1.1
      3   124 ms   114 ms    93 ms  182.176.0.108
      4   185 ms   195 ms   130 ms  10.0.3.158
      5   161 ms    85 ms   161 ms  182.176.139.193
      6   126 ms    99 ms    51 ms  182.176.139.178
      7   119 ms   299 ms   250 ms  rwp44.pie.net.pk [221.120.248.11]
      8   108 ms   102 ms    61 ms  rwp44.pie.net.pk [221.120.248.42]
      9   144 ms   268 ms   182 ms  xe2-2-1.catania7.cat.seabone.net [93.186.129.176]
     10   220 ms   253 ms   219 ms  ae10.milano58.mil.seabone.net [195.22.208.117]
     11   247 ms   392 ms   267 ms  be100-152.mil-5-a9.it.eu [91.121.131.62]
     12   365 ms   324 ms   287 ms  vl110.rbx-d2-a75.fr.eu [91.121.215.220]
     13   304 ms   282 ms     *     be100-1258.gsw-1-a9.fr.eu [91.121.215.219]
     14     *      289 ms   318 ms  be1.lyo-1-6k.fr.eu [91.121.131.114]
     15   332 ms   354 ms   334 ms  be1.mar-1-6k.fr.eu [91.121.131.118]
     16   343 ms   350 ms   293 ms  be5.mar-5-6k.fr.eu [91.121.215.155]
     17   561 ms   547 ms   589 ms  be100-1330.sin1-sgcs2-g1-nc5.sng.asia [178.33.100.255]
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20   529 ms   654 ms     *     sgp.smokeping.ovh.net [139.99.127.250]
     21   528 ms   589 ms   522 ms  sgp.smokeping.ovh.net [139.99.127.250]
    
    Trace complete.
    

    here is to leaseweb Sinapore

      Tracing route to 103.28.54.16 over a maximum of 30 hops
    
        1    26 ms     1 ms     1 ms  192.168.10.1
        2     1 ms     1 ms     9 ms  192.168.1.1
        3     *      126 ms   110 ms  182.176.0.108
        4   161 ms   182 ms   205 ms  10.55.0.34
        5   210 ms   138 ms   157 ms  182.176.139.193
        6    44 ms    45 ms    46 ms  182.176.139.178
        7    53 ms    61 ms    48 ms  static-10GE-KHI275-P01-SwA.pie.net.pk [202.125.128.173]
        8    75 ms    51 ms    51 ms  rwp44.pie.net.pk [221.120.248.46]
        9   122 ms   122 ms   133 ms  habib-rafiq.khi77d2.pie.net.pk [202.125.129.218]
       10   181 ms   150 ms   127 ms  32590.sgw.equinix.com [27.111.228.176]
       11   238 ms   170 ms   152 ms  192.168.152.5
       12   124 ms   124 ms   124 ms  103.28.54.16
    
      Trace complete.
    
  • From my internet connection (Indosat, Indonesia)

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  10.10.15.1
      2     *     *     *  *
      3     9 ms    10 ms    10 ms  202-93-46-30.resources.indosat.com [202.93.46.30]
      4    59 ms     9 ms     9 ms  202-93-46-29.resources.indosat.com [202.93.46.29]
      5     *        *        *     Request timed out.
      6   117 ms    36 ms    36 ms  114-0-78-88.resources.indosat.com [114.0.78.88]
      7    22 ms    22 ms    22 ms  114-0-78-205.resources.indosat.com [114.0.78.205]
      8    22 ms    22 ms    22 ms  114-4-19-102.resources.indosat.com [114.4.19.102]
      9     *        *        *     Request timed out.
     10    23 ms    23 ms    24 ms  sin1-sgcs2-g1-nc5.sng.asia [103.5.15.5]
     11     *        *        *     Request timed out.
     12     *        *        *     Request timed out.
     13     *       42 ms    46 ms  sgp.smokeping.ovh.net [139.99.127.250]
    
  • openosopenos Member
    edited May 2018

    in Shenzhen China

    Cw8Cid.png

  • FoxelVoxFoxelVox Member
    edited May 2018

    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

  • shellshell Member
    edited May 2018
                                                                                            
    [root@router] > tool traceroute sgp.smokeping.ovh.net count=10 use-dns=yes                                                           
     # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST STD-DEV STATUS                                             
     1 182.253.32.x                       0%   10   3.9ms    17.1     1.3    40.5    16.8                                                    
     2 182.253.187.145                    0%   10   3.3ms     2.7     1.7     3.3     0.5                                                    
     3 182.253.255.110                    0%   10   3.6ms     3.6     1.5       5     1.1                                                    
     4 jkt-gs-9.biznetnetworks.com        0%   10  16.6ms    16.1    13.6    18.6     1.7                                                    
     5 v603.core1.sin1.he.net             0%   10  22.6ms    17.2    14.4    22.6     3.1                                                    
     6                                  100%   10 timeout                                                                                    
     7 sin1-sgcs2-g1-nc5.sng.asia         0%   10  15.7ms    15.2    14.3    15.7     0.4                                                    
    
    

    ovh not peering with my isp biznetnetworks ?
    latency normal for indonesia < > sg arround 15ms

  • Hope you guys are doing this as well :-)

    @OVH_APAC said:

    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:

    1. To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
    2. To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server 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
    Thanked by 1inklight
  • crpatelcrpatel Member

    Still weird routing for Sydney location.

    Tracing route to syd.smokeping.ovh.net [139.99.128.38]
    over a maximum of 30 hops:
    
          1    <1 ms     1 ms     1 ms  121.243.78.193
          2     4 ms     3 ms     3 ms  121.243.78.21
          3     9 ms     9 ms     9 ms  121.244.40.158.static-mumbai.vsnl.net.in [121.244.40.158]
          4     9 ms     9 ms     9 ms  ix-ae-0-4.tcore1.mlv-mumbai.as6453.net [180.87.38.5]
          5   125 ms   126 ms   130 ms  if-ae-5-2.tcore1.wyn-marseille.as6453.net [80.231.217.29]
          6   125 ms   125 ms   125 ms  if-ae-8-1600.tcore1.pye-paris.as6453.net [80.231.217.6]
          7   129 ms   124 ms   127 ms  if-ae-11-2.tcore1.pvu-paris.as6453.net [80.231.153.49]
          8     *        *        *     Request timed out.
          9   125 ms   125 ms   134 ms  ae-1-3102.ear2.paris1.level3.net [4.69.140.30]
         10   130 ms   130 ms   130 ms  be100-106.gsw-1-a9.fr.eu [178.33.100.221]
         11   136 ms   136 ms   136 ms  be1.lyo-1-6k.fr.eu [91.121.131.114]
         12   141 ms   141 ms   141 ms  be1.mar-1-6k.fr.eu [91.121.131.118]
         13   142 ms   141 ms   141 ms  be5.mar-5-6k.fr.eu [91.121.215.155]
         14   177 ms   177 ms   177 ms  be100-1330.sin1-sgcs2-g1-nc5.sng.asia [178.33.100.255]
         15   179 ms   177 ms   177 ms  sin-sg1-bb1-a9.sng.asia [103.5.15.4]
         16   265 ms   264 ms   264 ms  syd-sy2-bb1-a9.aus.asia [103.5.15.27]
         17   264 ms   265 ms   264 ms  syd1-sy2-g1-nc5.aus.asia [103.5.14.221]
         18     *        *        *     Request timed out.
         19     *        *        *     Request timed out.
         20   305 ms   263 ms   263 ms  syd.smokeping.ovh.net [139.99.128.38]
    
        Trace complete.
    

    Pretty improved routing fro Singapore location.

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1    <1 ms     1 ms     1 ms  121.243.78.193
      2     3 ms     5 ms     3 ms  121.243.78.21
      3     9 ms    16 ms    15 ms  121.244.40.158.static-mumbai.vsnl.net.in [121.244.40.158]
      4    39 ms     *       39 ms  172.31.180.57
      5    36 ms    36 ms    40 ms  ix-ae-4-2.tcore1.cxr-chennai.as6453.net [180.87.36.9]
      6    65 ms    65 ms    65 ms  if-ae-3-3.tcore2.cxr-chennai.as6453.net [180.87.36.6]
      7    65 ms    64 ms    76 ms  if-ae-10-2.tcore2.svw-singapore.as6453.net [180.87.37.65]
      8    65 ms    65 ms    65 ms  sin-gss1-bb1-a9.sng.asia [103.5.15.18]
      9    65 ms    65 ms    65 ms  sin1-sgcs2-g2-nc5.sng.asia [103.5.15.17]
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12    65 ms    65 ms    65 ms  sgp.smokeping.ovh.net [139.99.127.250]
    
    Trace complete.
    
  • isijosamuaisijosamua Member
    edited May 2018

    Tracing via Telkom, Indonesia (AS7713)

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1     *        *        *     Request timed out.
      2     1 ms     1 ms     1 ms  36.85.224.1
      3     3 ms     1 ms     1 ms  149.subnet125-160-15.infra.telkom.net.id [125.160.15.149]
      4     2 ms     1 ms     1 ms  101.171.94.61.in-addr.arpa [61.94.171.101]
      5    54 ms    54 ms    54 ms  122.193.240.180.in-addr.arpa [180.240.193.122]
      6    58 ms    57 ms    54 ms  121.193.240.180.in-addr.arpa [180.240.193.121]
      7    62 ms    64 ms    66 ms  120.204.240.180.in-addr.arpa [180.240.204.120]
      8    57 ms    57 ms    56 ms  sin-sg1-bb1-a9.sng.asia [103.5.15.206]
      9   163 ms   167 ms   168 ms  sin1-sgcs2-g1-nc5.sng.asia [103.5.15.5]
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12    55 ms    55 ms    55 ms  sgp.smokeping.ovh.net [139.99.127.250]
    
  • FredQcFredQc Member

    Hetzner FSN

    traceroute to sgp.smokeping.ovh.net (139.99.127.250), 30 hops max, 60 byte packets
     1  []  0.275 ms  0.264 ms  0.300 ms
     2  core24.fsn1.hetzner.com (213.239.245.149)  0.236 ms core23.fsn1.hetzner.com (213.239.245.109)  0.775 ms  0.770 ms
     3  core1.fra.hetzner.com (213.239.229.77)  5.151 ms core1.fra.hetzner.com (213.239.203.153)  4.917 ms core4.fra.hetzner.com (213.239.229.73)  4.906 ms
     4  core9.fra.hetzner.com (213.239.224.221)  5.124 ms core9.fra.hetzner.com (213.239.224.178)  11.693 ms core9.fra.hetzner.com (213.239.224.174)  11.681 ms
     5  fra-1-a9.de.eu (94.23.122.250)  5.521 ms  5.592 ms  5.506 ms
     6  be101.sbg-g1-nc5.fr.eu (94.23.122.136)  42.661 ms  10.925 ms  8.612 ms
     7  be100-1254.th2-1-a9.fr.eu (94.23.122.139)  13.803 ms  14.039 ms  14.025 ms
     8  be1.lyo-5-6k.fr.eu (91.121.131.221)  20.181 ms  20.091 ms  20.003 ms
     9  be2.mar-5-6k.fr.eu (91.121.131.223)  190.089 ms  190.173 ms  190.265 ms
    10  be100-1330.sin1-sgcs2-g1-nc5.sng.asia (178.33.100.255)  190.746 ms  190.745 ms  190.734 ms
    11  * * *
    12  * * *
    13  sgp.smokeping.ovh.net (139.99.127.250)  190.380 ms  190.380 ms  190.370 ms
    
    
    traceroute to syd.smokeping.ovh.net (139.99.128.38), 30 hops max, 60 byte packets
     1  []  0.385 ms  0.416 ms  0.410 ms
     2  core24.fsn1.hetzner.com (213.239.245.149)  0.281 ms  0.330 ms  0.326 ms
     3  core4.fra.hetzner.com (213.239.229.73)  4.926 ms core5.fra.hetzner.com (213.239.224.254)  4.926 ms core5.fra.hetzner.com (213.239.224.250)  4.915 ms
     4  core9.fra.hetzner.com (213.239.224.178)  6.704 ms core9.fra.hetzner.com (213.239.224.221)  5.183 ms core9.fra.hetzner.com (213.239.224.174)  6.694 ms
     5  fra-1-a9.de.eu (94.23.122.250)  5.867 ms  5.674 ms  5.914 ms
     6  be101.sbg-g1-nc5.fr.eu (94.23.122.136)  8.835 ms  8.534 ms  8.782 ms
     7  be100-1254.th2-1-a9.fr.eu (94.23.122.139)  14.178 ms  14.330 ms  14.217 ms
     8  be1.lyo-5-6k.fr.eu (91.121.131.221)  20.178 ms  19.921 ms  19.904 ms
     9  be2.mar-5-6k.fr.eu (91.121.131.223)  24.299 ms  24.344 ms  24.425 ms
    10  be100-1330.sin1-sgcs2-g1-nc5.sng.asia (178.33.100.255)  190.568 ms  190.609 ms  190.765 ms
    11  sin-sg1-bb1-a9.sng.asia (103.5.15.4)  193.120 ms  192.882 ms  192.616 ms
    12  syd-sy2-bb1-a9.aus.asia (103.5.15.27)  278.528 ms  278.620 ms  278.687 ms
    13  syd1-sy2-g1-nc5.aus.asia (103.5.14.221)  278.505 ms  278.592 ms  278.479 ms
    14  * * *
    15  * * *
    16  syd.smokeping.ovh.net (139.99.128.38)  277.782 ms  277.776 ms  277.758 ms
    
  • FredQcFredQc Member

    Choopa NJ

    traceroute to sgp.smokeping.ovh.net (139.99.127.250), 30 hops max, 60 byte packets
     1  * * *
     2  vl201-c8-7-b2-1.pnj1.choopa.net (208.167.226.81)  0.398 ms  0.643 ms  0.834 ms
     3  vl130-br1.pnj1.choopa.net (108.61.244.73)  0.756 ms vl834-br2.pnj1.choopa.net (108.61.244.77)  0.216 ms vl130-br1.pnj1.choopa.net (108.61.244.73)  0.751 ms
     4  vl23-er1.pnj1.choopa.net (108.61.248.6)  6.708 ms * *
     5  * * *
     6  nyiix.nyc.ny.us (198.32.160.77)  11.946 ms  1.148 ms  11.904 ms
     7  * be8.nwk-20-6k.nj.us (178.32.135.59)  1.461 ms *
     8  be100-5.nwk-1-a9.nj.us (192.99.146.94)  2.143 ms be100-1039.ash-5-a9.va.us (198.27.73.203)  7.328 ms be100-5.nwk-1-a9.nj.us (192.99.146.94)  11.974 ms
     9  be100-1039.ash-5-a9.va.us (198.27.73.203)  17.322 ms  30.780 ms be100-1366.lax-la1-bb1-a9.ca.us (178.32.135.157)  63.297 ms
    10  be100-1365.sjo-sv5-bb1-a9.ca.us (198.27.73.105)  76.109 ms be100-1366.lax-la1-bb1-a9.ca.us (178.32.135.157)  67.047 ms be100-1365.sjo-sv5-bb1-a9.ca.us (198.27.73.105)  76.007 ms
    11  sin-gss1-bb1-a9.sng.asia (103.5.15.28)  235.684 ms be100-1365.sjo-sv5-bb1-a9.ca.us (198.27.73.105)  107.741 ms  75.980 ms
    12  sin1-sgcs2-g2-nc5.sng.asia (103.5.15.17)  235.599 ms sin-gss1-bb1-a9.sng.asia (103.5.15.28)  235.952 ms  236.088 ms
    13  * * *
    14  * * *
    15  sgp.smokeping.ovh.net (139.99.127.250)  235.280 ms * *
    
    
    traceroute to syd.smokeping.ovh.net (139.99.128.38), 30 hops max, 60 byte packets
     1  * * *
     2  vl201-c8-7-b2-1.pnj1.choopa.net (208.167.226.81)  0.366 ms  0.641 ms  0.841 ms
     3  vl130-br1.pnj1.choopa.net (108.61.244.73)  5.386 ms  5.405 ms  5.472 ms
     4  er1.pnj1.choopa.net (108.61.244.202)  0.183 ms * vl41-er1-q8.pnj1.choopa.net (108.61.2.78)  1.195 ms
     5  nyiix.nyc.ny.us (198.32.160.77)  1.782 ms *  1.803 ms
     6  nyiix.nyc.ny.us (198.32.160.77)  1.869 ms  1.898 ms  1.705 ms
     7  be8.nwk-20-6k.nj.us (178.32.135.59)  1.428 ms be100-5.nwk-5-a9.nj.us (192.99.146.96)  1.709 ms *
     8  be100-5.nwk-5-a9.nj.us (192.99.146.96)  1.710 ms  9.793 ms be100-1007.ash-5-a9.va.us (198.27.73.219)  6.973 ms
     9  * be100-1007.ash-5-a9.va.us (198.27.73.219)  7.343 ms  15.061 ms
    10  be100-1367.lax-la1-bb1-a9.ca.us (178.32.135.160)  71.117 ms  71.586 ms  63.115 ms
    11  be100-1069.syd1-sy2-g2-nc5.aus.asia (198.27.73.169)  210.038 ms  209.972 ms  218.813 ms
    12  * * *
    13  syd.smokeping.ovh.net (139.99.128.38)  208.986 ms * *
    
  • gongyigongyi Member
    edited May 2018

    guangzhou city , guangdong province , China telecom

  • edited May 2018

    About the same as it always was from LA and Chicago. It's not great but not bad either.

  • subhojitduttasubhojitdutta Member
    edited May 2018

    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)

    Traceroute has started…
    
    traceroute to syd.smokeping.ovh.net (139.99.128.38), 64 hops max, 72 byte packets
     1  192.168.2.1 (192.168.2.1)  1.967 ms  1.670 ms  1.555 ms
     2  22-111-87-183.mysipl.com (183.87.111.22)  5.654 ms  6.016 ms  3.600 ms
     3  * * *
     4  42-97-87-183.mysipl.com (183.87.97.42)  19.371 ms  20.675 ms  20.646 ms
     5  172.23.78.237 (172.23.78.237)  18.038 ms  16.016 ms  15.637 ms
     6  ix-ae-0-4.tcore1.mlv-mumbai.as6453.net (180.87.38.5)  85.479 ms  84.981 ms  84.890 ms
     7  if-ae-5-2.tcore1.wyn-marseille.as6453.net (80.231.217.29)  135.721 ms  138.420 ms  138.429 ms
     8  if-ae-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6)  138.034 ms  139.406 ms  139.271 ms
     9  if-ae-11-2.tcore1.pvu-paris.as6453.net (80.231.153.49)  135.879 ms  134.303 ms  135.913 ms
    10  * * *
    11  * * *
    12  be100-106.gsw-1-a9.fr.eu (178.33.100.221)  125.513 ms  123.144 ms  124.936 ms
    13  be1.lyo-1-6k.fr.eu (91.121.131.114)  129.029 ms  129.323 ms  129.557 ms
    14  be1.mar-1-6k.fr.eu (91.121.131.118)  137.419 ms  140.899 ms  136.101 ms
    15  be5.mar-5-6k.fr.eu (91.121.215.155)  136.430 ms  137.167 ms  137.551 ms
    16  be100-1330.sin1-sgcs2-g1-nc5.sng.asia (178.33.100.255)  176.682 ms  176.442 ms  175.890 ms
    17  sin-sg1-bb1-a9.sng.asia (103.5.15.4)  172.272 ms  169.974 ms  170.666 ms
    18  syd-sy2-bb1-a9.aus.asia (103.5.15.27)  400.234 ms  409.241 ms  367.071 ms
    19  syd1-sy2-g1-nc5.aus.asia (103.5.14.221)  451.866 ms  409.250 ms  366.741 ms
    20  * * *
    21  * * *
    22  syd.smokeping.ovh.net (139.99.128.38)  437.041 ms  408.681 ms  409.594 ms
    
  • rm_rm_ IPv6 Advocate, Veteran
    edited May 2018

    @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.

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

  • filefile Member

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

    To be pedantic they didn't ask people to post in the first place. They asked people to send them to their mailing list.

    Thanked by 1rm_
  • randvegetarandvegeta Member, Host Rep

    WTF. 500ms from HK. Routing via France? WTF?

    Ping statistics for 139.99.127.250:  
    Packets: Sent = 36, Received = 36, Lost = 0 (0% loss),  
    Approximate round trip times in milli-seconds:  
    Minimum = 431ms, Maximum = 553ms, Average = 474ms  
    

    and

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]  
    over a maximum of 30 hops:  
    
      1     2 ms     1 ms     2 ms  10.0.16.1  
      2     4 ms     2 ms     2 ms  59.188.224.129  
      3     2 ms     2 ms     2 ms  203.176.194.221  
      4     3 ms     2 ms     2 ms  irb8.10g-tc1.wpc.nwtgigalink.com [113.10.229.97]  
      5     3 ms     2 ms     2 ms  ae2.10g-pp1.wpc.nwtgigalink.com [113.10.229.178]  
      6   265 ms   202 ms   202 ms  ge-1-3-3-xcr1.hkg.cw.net [195.89.101.109]  
      7   273 ms   205 ms   301 ms  xe-4-0-0-xcr1.sng.cw.net [195.2.10.178]  
      8   280 ms   253 ms   355 ms  ae2-xcr2.sgs.cw.net [195.2.24.166]  
      9   341 ms   308 ms   289 ms  ae27-xcr1.mar.cw.net [195.2.9.101]  
     10   268 ms   304 ms   239 ms  ae2-xcr2.prp.cw.net [195.2.10.125]  
     11   266 ms   304 ms   304 ms  gsw-1-a9.fr.eu [54.36.50.70]  
     12   212 ms   303 ms   275 ms  be1.lyo-1-6k.fr.eu [91.121.131.114]  
     13   332 ms   301 ms   273 ms  be1.mar-1-6k.fr.eu [91.121.131.118]  
     14   335 ms   304 ms   304 ms  be5.mar-5-6k.fr.eu [91.121.215.155]  
     15   510 ms   448 ms   467 ms  be100-1330.sin1-sgcs2-g1-nc5.sng.asia [178.33.100.255]  
     16     *        *        *     Request timed out.  
     17     *        *        *     Request timed out.  
     18   448 ms   431 ms   484 ms  sgp.smokeping.ovh.net [139.99.127.250]  
    
    Trace complete.  
    
    Thanked by 1Clouvider
  • Mahfuz_SS_EHLMahfuz_SS_EHL Host Rep, Veteran
    edited May 2018

    From Bangladesh (Link 3 - AS23688)

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1    <1> ms    <1> ms    <1> ms  192.168.0.1
      2     5 ms     4 ms     3 ms  27.147.231.161
      3     *        *        *     Request timed out.
      4     6 ms     4 ms     5 ms  203.76.118.133
      5    15 ms    23 ms    22 ms  203.76.104.101
      6    32 ms    33 ms    24 ms  start.link3.net [203.76.118.1]
      7    23 ms    21 ms    23 ms  103.9.104.121
      8     9 ms    12 ms    11 ms  103.9.104.65
      9    76 ms    74 ms    66 ms  103.9.104.85
     10     *        *        *     Request timed out.
     11    64 ms    64 ms    65 ms  sin1-sgcs2-g1-nc5.sng.asia [103.5.15.5]
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14    64 ms    63 ms    65 ms  sgp.smokeping.ovh.net [139.99.127.250]
    
    Trace complete.
    
    Tracing route to syd.smokeping.ovh.net [139.99.128.38]
    over a maximum of 30 hops:
    
      1    <1> ms    <1> ms    <1> ms  192.168.0.1
      2     7 ms    10 ms     9 ms  27.147.231.161
      3     2 ms     *        *     10.20.245.85
      4     9 ms     5 ms     5 ms  203.76.118.133
      5     7 ms     5 ms     5 ms  dhk.link3.net [203.76.104.1]
      6     8 ms    13 ms     9 ms  start.link3.net [203.76.118.1]
      7     5 ms     4 ms     5 ms  103.9.104.121
      8    25 ms    24 ms    30 ms  103.9.104.65
      9    78 ms    65 ms    71 ms  103.9.104.85
     10     *        *        *     Request timed out.
     11   153 ms   164 ms   151 ms  syd-sy2-bb1-a9.aus.asia [103.5.15.27]
     12   151 ms   155 ms   153 ms  syd1-sy2-g1-nc5.aus.asia [103.5.14.221]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *      155 ms   155 ms  syd.smokeping.ovh.net [139.99.128.38]
    
    Trace complete.
    
  • crpatelcrpatel Member

    @Mahfuz_SS_EHL That's pretty decent routing for Sydney location.

  • NeoonNeoon Community Contributor, Veteran
    edited May 2018

    "Send your traceroute results to [email protected] and the team will investigate"

  • zllovesukizllovesuki Member
    edited May 2018

    We got some pretty interesting trace route here.

    sgp.smokeping.ovh.net:

     1  gateway-64-62-136 (64.62.136.1)  0.310 ms  0.139 ms  0.130 ms
     2  10ge7-3.core1.sjc2.he.net (72.52.92.110)  0.756 ms  0.672 ms  0.677 ms
     3  * * *
     4  sin-gss1-bb1-a9.sng.asia (103.5.15.28)  235.270 ms  236.021 ms  235.421 ms
     5  sin1-sgcs2-g2-nc5.sng.asia (103.5.15.17)  235.308 ms  235.378 ms  235.355 ms
     6  * * *
     7  * * *
     8  sgp.smokeping.ovh.net (139.99.127.250)  234.742 ms  234.657 ms  234.661 ms
    

    syd.smokeping.ovh.net:

     1  gateway-64-62-136 (64.62.136.1)  0.284 ms  0.136 ms  0.131 ms
     2  10ge7-3.core1.sjc2.he.net (72.52.92.110)  0.736 ms  0.676 ms  0.773 ms
     3  * * *
     4  be100-1365.lax-la1-bb1-a9.ca.us (198.27.73.104)  12.046 ms  12.053 ms  11.737 ms
     5  be100-1069.syd1-sy2-g2-nc5.aus.asia (198.27.73.169)  279.001 ms  278.950 ms  279.220 ms
     6  * * *
     7  * * *
     8  syd.smokeping.ovh.net (139.99.128.38)  278.390 ms  278.590 ms  278.319 ms
    
  • msg7086msg7086 Member

    Latency to China CN2 (AS4809) is 36ms, that's good.

    However who can afford CN2 premium?

    All other results to Chinese endpoints look terrible.

  • FHRFHR Member, Host Rep

    @Neoon said:
    "Send your traceroute results to [email protected] and the team will investigate"

    Mailing lists are the fastest and most reliable way to get support.

  • rm_rm_ IPv6 Advocate, Veteran
    edited May 2018

    Neoon said: "Send your traceroute results to [email protected] and the team will investigate"

    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.

  • ClouviderClouvider Member, Patron Provider

    I like how it started as a promo post and turned into this

    @randvegeta said:
    WTF. 500ms from HK. Routing via France? WTF?

    Ping statistics for 139.99.127.250:  
    Packets: Sent = 36, Received = 36, Lost = 0 (0% loss),  
    Approximate round trip times in milli-seconds:  
    Minimum = 431ms, Maximum = 553ms, Average = 474ms  
    

    and

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]  
    over a maximum of 30 hops:  
      
      1     2 ms     1 ms     2 ms  10.0.16.1  
      2     4 ms     2 ms     2 ms  59.188.224.129  
      3     2 ms     2 ms     2 ms  203.176.194.221  
      4     3 ms     2 ms     2 ms  irb8.10g-tc1.wpc.nwtgigalink.com [113.10.229.97]  
      5     3 ms     2 ms     2 ms  ae2.10g-pp1.wpc.nwtgigalink.com [113.10.229.178]  
      6   265 ms   202 ms   202 ms  ge-1-3-3-xcr1.hkg.cw.net [195.89.101.109]  
      7   273 ms   205 ms   301 ms  xe-4-0-0-xcr1.sng.cw.net [195.2.10.178]  
      8   280 ms   253 ms   355 ms  ae2-xcr2.sgs.cw.net [195.2.24.166]  
      9   341 ms   308 ms   289 ms  ae27-xcr1.mar.cw.net [195.2.9.101]  
     10   268 ms   304 ms   239 ms  ae2-xcr2.prp.cw.net [195.2.10.125]  
     11   266 ms   304 ms   304 ms  gsw-1-a9.fr.eu [54.36.50.70]  
     12   212 ms   303 ms   275 ms  be1.lyo-1-6k.fr.eu [91.121.131.114]  
     13   332 ms   301 ms   273 ms  be1.mar-1-6k.fr.eu [91.121.131.118]  
     14   335 ms   304 ms   304 ms  be5.mar-5-6k.fr.eu [91.121.215.155]  
     15   510 ms   448 ms   467 ms  be100-1330.sin1-sgcs2-g1-nc5.sng.asia [178.33.100.255]  
     16     *        *        *     Request timed out.  
     17     *        *        *     Request timed out.  
     18   448 ms   431 ms   484 ms  sgp.smokeping.ovh.net [139.99.127.250]  
      
    Trace complete.  
    

    Good job OVH :)

    Thanked by 1randvegeta
  • ClouviderClouvider Member, Patron Provider

    @file said:

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

    To be pedantic they didn't ask people to post in the first place. They asked people to send them to their mailing list.

    They want to have their network improved they should be happy to accept support in any form.

  • @msg7086 said:
    Latency to China CN2 (AS4809) is 36ms, that's good.

    However who can afford CN2 premium?

    All other results to Chinese endpoints look terrible.

    OVH dont regard mainland China as their target market. Also, you can buy CN2 VPS from CloudIPLC.

  • OVH_APACOVH_APAC Member, Patron Provider

    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.

    Thanked by 1jihchi
  • polzpolz Member

    from AS17974

  • From ISP : MyRepublic Indonesia ( AS63859 )

    To sgp.smokeping.ovh.net

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.10.1
      2     2 ms     2 ms     1 ms  10.58.0.1
      3     2 ms     2 ms     2 ms  172.16.11.12
      4     3 ms     2 ms     2 ms  103.47.134.209
      5   184 ms   186 ms   187 ms  103.54.219.41
      6   184 ms   184 ms   186 ms  103.56.234.73
      7     *        *        *     Request timed out.
      8    15 ms    15 ms    15 ms  sin1-sgcs2-g1-nc5.sng.asia [103.5.15.5]
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11    14 ms    14 ms    14 ms  sgp.smokeping.ovh.net [139.99.127.250]
    
    Trace complete. <>
    Pinging sgp.smokeping.ovh.net [139.99.127.250] with 32 bytes of data:
    Reply from 139.99.127.250: bytes=32 time=14ms TTL=51
    Reply from 139.99.127.250: bytes=32 time=14ms TTL=51
    Reply from 139.99.127.250: bytes=32 time=14ms TTL=51
    Reply from 139.99.127.250: bytes=32 time=14ms TTL=51<>

    To syd.smokeping.ovh.net

    Tracing route to syd.smokeping.ovh.NET [139.99.128.38]
    over a maximum of 30 hops:
    
      1     2 ms    <1 ms    <1 ms  192.168.10.1
      2     2 ms     2 ms     2 ms  10.58.0.1
      3     2 ms     2 ms     2 ms  172.16.11.12
      4     2 ms     2 ms     2 ms  103.47.134.209
      5   185 ms   185 ms   185 ms  103.54.219.41
      6   185 ms   184 ms   185 ms  103.56.234.61
      7     *        *        *     Request timed out.
      8    16 ms    15 ms    16 ms  sin-gss1-bb1-a9.sgp.asia [103.5.15.15]
      9   241 ms   241 ms   241 ms  sjo-sv5-bb1-a9.ca.us [103.5.15.29]
     10   241 ms   241 ms   241 ms  be100-1365.lax-la1-bb1-a9.ca.us [198.27.73.104]
     11   388 ms   388 ms   388 ms  be100-1069.syd1-sy2-g2-nc5.aus.asia [198.27.73.169]
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14   387 ms   387 ms   387 ms  syd.smokeping.ovh.net [139.99.128.38]
    
    Trace complete.<>
    Pinging syd.smokeping.ovh.NET [139.99.128.38] with 32 bytes of data:
    Reply from 139.99.128.38: bytes=32 time=387ms TTL=45
    Reply from 139.99.128.38: bytes=32 time=387ms TTL=45
    Reply from 139.99.128.38: bytes=32 time=387ms TTL=45
    Reply from 139.99.128.38: bytes=32 time=387ms TTL=45<>
Sign In or Register to comment.