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 - Page 3
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

1356712

Comments

  • lovesinlovesin Member
    edited May 2018

    In addition to problems with China Telecom AS4134, there are also problems with Hetzner Finland.

    on hetzner findland to http://sgp.smokeping.ovh.net/smokeping

        PING sgp.smokeping.ovh.net (139.99.127.250) 56(84) bytes of data.
        64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=1 ttl=51 time=200 ms
        64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=2 ttl=51 time=200 ms
        64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=3 ttl=51 time=200 ms
        64 bytes from sgp.smokeping.ovh.net (139.99.127.250): icmp_seq=4 ttl=51 time=200 ms
    

    trace

             1  static.1.11.216.95.clients.your-server.de (95.216.11.1)  5.341 ms  5.324 ms  5.312 ms
             2  core31.hel1.hetzner.com (213.239.224.133)  0.475 ms core32.hel1.hetzner.com (213.239.224.137)  0.371 ms core31.hel1.hetzner.com (213.239.224.133)  0.378 ms
             3  core6.hel.hetzner.com (213.239.224.25)  0.883 ms  0.846 ms core6.hel.hetzner.com (213.239.224.37)  0.857 ms
             4  core3.sto.hetzner.com (213.239.224.17)  8.117 ms  8.111 ms  8.099 ms
             5  core2.ams.hetzner.com (213.239.245.37)  26.265 ms  26.270 ms  26.259 ms
             6  * * *
             7  be104.rbx-g1-nc5.fr.eu (178.33.100.160)  60.046 ms  59.666 ms  32.195 ms
             8  be100-1044.gsw-1-a9.fr.eu (94.23.122.215)  31.974 ms  32.265 ms  32.217 ms
             9  be1.lyo-1-6k.fr.eu (91.121.131.114)  38.562 ms  38.394 ms be1.lyo-5-6k.fr.eu (91.121.131.221)  39.726 ms
            10  be1.mar-1-6k.fr.eu (91.121.131.118)  42.422 ms be2.mar-5-6k.fr.eu (91.121.131.223)  43.728 ms  43.898 ms
            11  be100-1330.sin1-sgcs2-g1-nc5.sng.asia (178.33.100.255)  219.134 ms be5.mar-5-6k.fr.eu (91.121.215.155)  42.450 ms be100-1330.sin1-sgcs2-g1-nc5.sng.asia (178.33.100.255)  219.136 ms
            12  be100-1330.sin1-sgcs2-g1-nc5.sng.asia (178.33.100.255)  217.740 ms * *
            13  * * *
            14  sgp.smokeping.ovh.net (139.99.127.250)  200.904 ms * *
    

    on hetzner findland to my ovh sgp vps

            PING 139.99.43.24x (139.99.43.24x) 56(84) bytes of data.
            64 bytes from 139.99.43.24x: icmp_seq=1 ttl=46 time=220 ms
            64 bytes from 139.99.43.24x: icmp_seq=2 ttl=46 time=220 ms
            64 bytes from 139.99.43.24x: icmp_seq=3 ttl=46 time=220 ms
            64 bytes from 139.99.43.24x: icmp_seq=4 ttl=46 time=220 ms
    
  • AS4134 users will never be OVH's target customers.

  • fkjfkj Member

    OVH_APAC said: @fkj - We have 40ms now. Can you please recheck and let me know.

    Noop, still 200ms+.

    tracepath -b sgp.smokeping.ovh.net 1?: [LOCALHOST] pmtu 1500 University network 5: 203.188.117.1 (203.188.117.1) 3.271ms 6: 165084185137.ctinets.com (165.84.185.137) 3.589ms 7: 061244119042.ctinets.com (61.244.119.42) 3.682ms 8: 014136204189.static.ctinets.com (14.136.204.189) 3.418ms asymm 9 9: 014136129037.ctinets.com (14.136.129.37) 13.387ms asymm 10 10: 014136129218.ctinets.com (14.136.129.218) 3.844ms 11: no reply 12: sin1-sgcs2-g1-nc5.sng.asia (103.5.15.5) 221.544ms asymm 19 13: no reply 14: no reply 15: sgp.smokeping.ovh.net (139.99.127.250) 220.536ms reached Resume: pmtu 1500 hops 15 back 24

  • ClouviderClouvider Member, Patron Provider

    @singhigh said:
    AS4134 users will never be OVH's target customers.

    Never is too strong of a word.

    Connectivity to them improves both in terms of capacity and price as the technology improves and will reach sustainable prices in a decade for sure.

  • MikeAMikeA Member, Patron Provider
    edited May 2018

    A government who doesn't censor the web would probably help with connectivity too in some form.

  • rm_rm_ IPv6 Advocate, Veteran

    lovesin said: there are also problems with Hetzner Finland.

    Why do you believe there is a problem, what ping do you expect from Singapore to Finland?

  • @Clouvider said:

    @singhigh said:
    AS4134 users will never be OVH's target customers.

    Never is too strong of a word.

    Connectivity to them improves both in terms of capacity and price as the technology improves and will reach sustainable prices in a decade for sure.

    Even in decades, I guess no. Too many users gathered in a same ASN with a lot of dirty traffics.

  • lovesinlovesin Member
    edited May 2018

    @rm_ said:

    lovesin said: there are also problems with Hetzner Finland.

    Why do you believe there is a problem, what ping do you expect from Singapore to Finland?

    My other Singapore servers are usually around 170ms.

  • EdmondEdmond Member

    @lovesin said:

    @rm_ said:

    lovesin said: there are also problems with Hetzner Finland.

    Why do you believe there is a problem, what ping do you expect from Singapore to Finland?

    My other Singapore servers are usually around 170ms.

    I seem to be getting that as well but it's not as high as it seems, it all depends on each provider's routes. You could have providers were the latency is even worst for that certain destination.

  • rm_rm_ IPv6 Advocate, Veteran

    lovesin said: My other Singapore servers are usually around 170ms.

    From Finland? Can you post some traceroutes? It is normal to have 170-180ms to Central or Western Europe, but given how Hetzner routes Finland it will typically have a higher ping.

  • ClouviderClouvider Member, Patron Provider

    @MikeA said:
    A government who doesn't censor the web would probably help with connectivity too in some form.

    Definitely.

    @singhigh said:

    @Clouvider said:

    @singhigh said:
    AS4134 users will never be OVH's target customers.

    Never is too strong of a word.

    Connectivity to them improves both in terms of capacity and price as the technology improves and will reach sustainable prices in a decade for sure.

    Even in decades, I guess no. Too many users gathered in a same ASN with a lot of dirty traffics.

    I wouldn’t underestimate the spending power here; it’s a huge officially virtually untapped emerging market. The Royal Wedding offer we published the other day was virtually sold out to China.

  • fkjfkj Member

    @rm_ said:

    lovesin said: My other Singapore servers are usually around 170ms.

    From Finland? Can you post some traceroutes? It is normal to have 170-180ms to Central or Western Europe, but given how Hetzner routes Finland it will typically have a higher ping.

    I bet that was the LeaseWeb DC.

  • edited May 2018

    @OVH_APAC
    i'm registered your mailing list but don't know how to use it =,=

    So i will post tracert into here

    From Ninh Thuan Province, Vietnam, ISP: FPT

    Tracing route to ns544569.ip-139-99-124.net [139.99.124.68]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.1.1 
      2     2 ms     1 ms     1 ms  118.69.255.40 
      3     9 ms    10 ms    13 ms  183.80.133.250 
      4    28 ms    28 ms    28 ms  118.69.166.245 
      5    27 ms    27 ms    28 ms  ix-xe-0-2-2-0.tcore2.svw-singapore.as6453.net [180.87.15.37] 
      6    28 ms    28 ms    28 ms  sin-gss1-bb1-a9.sng.asia [103.5.15.18] 
      7    30 ms    35 ms    28 ms  sin1-sgcs2-g2-nc5.sng.asia [103.5.15.17] 
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10    28 ms    28 ms    31 ms  ns544569.ip-139-99-124.net [139.99.124.68] 
    
    Trace complete.
    

    Another From Ninh Thuan Province, Vietnam, ISP: VNPT

    Tracing route to ns544569.ip-139-99-124.net [139.99.124.68]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.1.1 
      2     1 ms     1 ms     1 ms  static.vnpt.vn [123.29.12.146] 
      3     6 ms     6 ms     6 ms  static.vnpt.vn [113.171.46.117] 
      4     *        *        *     Request timed out.
      5    35 ms    34 ms    35 ms  unknown.telstraglobal.net [202.127.78.129] 
      6    35 ms    35 ms    35 ms  i-0-6-0-11.hkhh-core02.bi.telstraglobal.net [202.84.156.137] 
      7    65 ms    67 ms    67 ms  i-0-3-0-12.istt-core02.bx.telstraglobal.net [202.84.137.38] 
      8    64 ms    64 ms    64 ms  i-0-2-0-8.istt-core02.bi.telstraglobal.net [202.84.225.214] 
      9    52 ms    52 ms    52 ms  ix-ae-23-0.tcore1.svq-singapore.as6453.net [180.87.96.129] 
     10    53 ms    52 ms    53 ms  if-ae-20-2.tcore2.svw-singapore.as6453.net [180.87.96.22] 
     11    53 ms    53 ms    53 ms  sin-gss1-bb1-a9.sng.asia [103.5.15.18] 
     12    54 ms    55 ms    53 ms  sin1-sgcs2-g2-nc5.sng.asia [103.5.15.17] 
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15    53 ms    52 ms    53 ms  ns544569.ip-139-99-124.net [139.99.124.68]
    

    From Hanoi, Vietnam, FPT ISP

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     1 ms  LINKSYS-EA7500 [192.168.1.1] 
      2     9 ms     2 ms     3 ms  118.70.0.15 
      3     2 ms     2 ms     2 ms  118.70.3.25 
      4    22 ms    23 ms    23 ms  183.80.133.145 
      5    41 ms    41 ms    43 ms  118.69.166.70 
      6    42 ms    42 ms    41 ms  118.69.247.130 
      7    41 ms    40 ms    41 ms  ix-xe-0-2-2-0.tcore2.svw-singapore.as6453.net [180.87.15.37] 
      8    42 ms    42 ms    42 ms  sin-gss1-bb1-a9.sng.asia [103.5.15.18] 
      9    42 ms    42 ms    41 ms  sin1-sgcs2-g2-nc5.sng.asia [103.5.15.17] 
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12    41 ms    42 ms    41 ms  sgp.smokeping.ovh.net [139.99.127.250] 
    
    Trace complete.
    

    And, From Da Nang, Vietnam, ISP:CMC

    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1     5 ms     5 ms    15 ms  100.81.0.1 
      2     7 ms     4 ms     7 ms  100.81.0.1 
      3    19 ms    11 ms    21 ms  static.cmcti.vn [101.99.48.129] 
      4    32 ms    38 ms    39 ms  static.cmcti.vn [101.99.48.161] 
      5    46 ms    27 ms    23 ms  static.cmcti.vn [101.99.0.186] 
      6     *        *        *     Request timed out.
      7    69 ms    74 ms    64 ms  sin1-sgcs2-g1-nc5.sng.asia [103.5.15.5] 
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10    56 ms    55 ms    72 ms  sgp.smokeping.ovh.net [139.99.127.250] 
    
    Trace complete.
    
    
    
            Trace complete.
    
  • I love OVH for its stable solid service, yours too. Though I am a Chinese but, I clear if more Chinese traffic, the less stable service will have (

    @Clouvider said:

    @singhigh said:

    @Clouvider said:

    @singhigh said:
    AS4134 users will never be OVH's target customers.

    Never is too strong of a word.

    Connectivity to them improves both in terms of capacity and price as the technology improves and will reach sustainable prices in a decade for sure.

    Even in decades, I guess no. Too many users gathered in a same ASN with a lot of dirty traffics.

    I wouldn’t underestimate the spending power here; it’s a huge officially virtually untapped emerging market. The Royal Wedding offer we published the other day was virtually sold out to China.

    Thanked by 1Clouvider
  • @lovesin said:

    My other Singapore servers are usually around 170ms.

    Whoa, wait! Ping from Finland to Singapore at 170ms?! What DC/provider is that?

  • edited May 2018

    @OVH_APAC
    other tracert, this ip can't ping or complete tracert to OVH Singapore, from Khanh Hoa Province, Vietnam, ISP: VNPT

      1    <1 ms    <1 ms    <1 ms  192.168.1.1
      2     4 ms     2 ms     3 ms  static.vnpt.vn [123.29.8.69]
      3     3 ms     3 ms     4 ms  static.vnpt.vn [113.171.58.101]
      4    13 ms    23 ms    19 ms  static.vnpt.vn [123.29.9.193]
      5    12 ms    11 ms    13 ms  static.vnpt.vn [123.29.8.238]
      6    42 ms    39 ms    39 ms  unknown.telstraglobal.net [210.57.81.77]
      7    37 ms    40 ms    39 ms  unknown.telstraglobal.net [202.84.157.190]
      8    73 ms    71 ms    71 ms  i-0-2-0-13.istt-core02.bx.telstraglobal.net [202
    .84.136.206]
      9    75 ms    75 ms    75 ms  i-0-2-0-8.istt-core02.bi.telstraglobal.net [202.
    84.225.214]
     10   210 ms   207 ms   207 ms  ix-ae-23-0.tcore1.svq-singapore.as6453.net [180.
    87.96.129]
     11   217 ms   215 ms   256 ms  if-ae-20-2.tcore2.svw-singapore.as6453.net [180.
    87.96.22]
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17     *
    
  • openosopenos Member
    edited May 2018

    China Unicom

    DYsS6.md.png

    ....................................................

    China Mobile

    DYHXG.md.png

    DYVu9.md.png

  • @openos AS OVH said thats all they can do. If you need China traffic, don't use OVH.

  • OVH_APACOVH_APAC Member, Patron Provider

    @lost_connection - We have contacted the provider. We will see what we can do.

    FYI, We have also made some changes in Taiwan today

    We changed some routing rules to New Century InfoComm and Digital United to improve the latency. From 185ms to 80ms and from 175ms to 55ms

    More details:

    Thanks,

    Thanked by 2MikeA hanoi
  • hanoihanoi Member

    @OVH_APAC said:
    @lost_connection - We have contacted the provider. We will see what we can do.

    FYI, We have also made some changes in Taiwan today

    We changed some routing rules to New Century InfoComm and Digital United to improve the latency. From 185ms to 80ms and from 175ms to 55ms

    More details:

    Thanks,

    Actually, some Vietnamese submarine cables are under construction.

    https://news.zing.vn/cap-aag-sua-chua-ket-noi-internet-tu-viet-nam-di-quoc-te-bi-anh-huong-post845925.html

    https://translate.google.com/translate?hl=vi&amp;sl=auto&amp;tl=en&amp;u=https://news.zing.vn/cap-aag-sua-chua-ket-noi-internet-tu-viet-nam-di-quoc-te-bi-anh-huong-post845925.html

    Btw, I really appreciate OVH's effort to improve network.

  • @hanoi said:

    @OVH_APAC said:
    @lost_connection - We have contacted the provider. We will see what we can do.

    FYI, We have also made some changes in Taiwan today

    We changed some routing rules to New Century InfoComm and Digital United to improve the latency. From 185ms to 80ms and from 175ms to 55ms

    More details:

    Thanks,

    Actually, some Vietnamese submarine cables are under construction.

    https://news.zing.vn/cap-aag-sua-chua-ket-noi-internet-tu-viet-nam-di-quoc-te-bi-anh-huong-post845925.html

    https://translate.google.com/translate?hl=vi&amp;sl=auto&amp;tl=en&amp;u=https://news.zing.vn/cap-aag-sua-chua-ket-noi-internet-tu-viet-nam-di-quoc-te-bi-anh-huong-post845925.html

    Btw, I really appreciate OVH's effort to improve network.

    only on route from Hongkong to USA, not route throught Singapore.

  • OVH_APACOVH_APAC Member, Patron Provider

    @lost_connection - We were having some issues, but they look to be resolved now: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS18403

    Thanked by 1flonetmelb
  • traceroute to sgp.smokeping.ovh.net (139.99.127.250), 30 hops max, 60 byte packets
     1  _gateway (192.168.1.1)  3.870 ms  3.895 ms  3.941 ms
     2  192.168.48.252 (192.168.48.252)  7.493 ms  7.691 ms  7.852 ms
     3  192.168.0.1 (192.168.0.1)  8.273 ms  10.354 ms  10.358 ms
     4  * * *
     5  * * *
     6  * be8-cg03-pe04.fast.net.id (202.73.96.25)  27.950 ms  30.919 ms
     7  lynx-static-116-68-231-197.lynx.net.id (116.68.231.197)  51.400 ms  52.412 ms  52.384 ms
     8  * * *
     9  sin1-sgcs2-g2-nc5.sng.asia (103.5.15.17)  61.444 ms  65.457 ms  69.541 ms
    10  * * *
    11  * * *
    12  sgp.smokeping.ovh.net (139.99.127.250)  71.704 ms * *
    

    @OVH_APAC Firstmedia Indonesia, surabaya. able to reduce the latency? thanks

  • lovemindsloveminds Member
    edited June 2018

    from CloudVSP datacenter in Canton,China via ChinaTelecom (AS58466/4134)

                                                           My traceroute  [v0.86]
    CloudVSP (0.0.0.0)                                                                                Wed Jun 13 16:26:54 2018
    Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                               Packets               Pings
     Host                                                                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. ???
     2. 10.254.2.254                                                                          0.7%   429    1.1   2.2   0.9  18.3   2.5
     3. 10.229.0.8                                                                            0.0%   429    0.5   0.5   0.4   0.9   0.0
     4. 100.125.175.3                                                                         0.0%   429   13.0  37.8   1.9  61.4  17.9
     5. 172.31.2.101                                                                          0.5%   429    2.6  11.7   2.6 190.2  23.4
     6. 172.31.3.33                                                                           0.0%   429    2.9   8.7   2.7 103.2  16.9
     7. 172.31.4.241                                                                         28.0%   429    0.9   0.9   0.8   3.6   0.1
     8. ???
     9. 105.96.135.219.broad.fs.gd.dynamic.163data.com.cn                                     0.0%   429    4.1   3.6   1.6   9.9   1.1
    10. 113.108.208.229                                                                       0.0%   429    5.4   5.2   2.8  23.1   1.6
    11. 202.97.94.142                                                                        53.0%   429    3.4   4.2   3.3  33.3   3.1
    12. 202.97.94.98                                                                          0.0%   429    8.8   8.2   4.4  17.9   2.2
    13. 202.97.60.214                                                                         3.5%   429  174.2 174.9 172.4 271.9   8.9
    14. ae-2.r31.tokyjp05.jp.bb.gin.ntt.net                                                   9.6%   429  170.5 195.6 170.3 239.6  25.1
    15. ae-9.r21.sngpsi07.sg.bb.gin.ntt.net                                                  10.7%   429  240.2 265.8 240.0 299.4  23.6
    16. ae-2.r00.sngpsi07.sg.bb.gin.ntt.net                                                   9.1%   429  285.1 285.1 282.7 286.3   0.2
    17. sin-sg1-bb1-a9.sng.asia                                                               9.6%   428  289.0 289.6 287.0 328.6   4.0
    18. sin1-sgcs2-g1-nc5.sng.asia                                                            6.3%   428  287.0 287.8 284.9 319.9   2.3
    19. ???
    20. ???
    21. sgp.smokeping.ovh.net                                                                 5.6%   428  239.9 239.9 239.7 242.1   0.2
    
  • vpsGODvpsGOD Member, Host Rep

    Jio, India

    C:\Users\DeadEnd>tracert sgp.smokeping.ovh.net
    
    Tracing route to sgp.smokeping.ovh.net [139.99.127.250]
    over a maximum of 30 hops:
    
      1     4 ms     4 ms     4 ms  192.168.43.1
      2     *        *        *     Request timed out.
      3    94 ms    78 ms    78 ms  10.71.201.26
      4    80 ms    58 ms    78 ms  172.25.55.209
      5    78 ms    58 ms    68 ms  172.26.56.79
      6   123 ms    88 ms    69 ms  172.25.8.9
      7    97 ms    92 ms    71 ms  172.25.8.249
      8   126 ms    71 ms    77 ms  172.26.29.42
      9    91 ms    80 ms   393 ms  172.26.29.42
     10    83 ms    73 ms    88 ms  103.198.140.64
     11   109 ms   110 ms    93 ms  103.198.140.15
     12     *        *        *     Request timed out.
     13   134 ms   112 ms   111 ms  sin1-sgcs2-g1-nc5.sng.asia [103.5.15.5]
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16   113 ms   107 ms   111 ms  sgp.smokeping.ovh.net [139.99.127.250]
    
    Trace complete.
    
  • dgprasetyadgprasetya Member
    edited June 2018

    @OVH_APAC from Telkom Indonesia
    sudo mtr --report sgp.smokeping.ovh.net Start: Wed Jun 13 15:57:18 2018 HOST: debian Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.1.1 0.0% 10 0.3 0.3 0.3 0.4 0.0 2.|-- 192.168.100.1 0.0% 10 1.1 0.9 0.7 1.2 0.0 3.|-- 36.73.64.1 0.0% 10 149.7 141.3 34.1 204.8 63.6 4.|-- 125.160.1.197 0.0% 10 2.5 1.8 1.4 2.6 0.0 5.|-- 180.252.3.241 0.0% 10 2.3 2.8 1.6 5.3 1.1 6.|-- 180.240.191.42 0.0% 10 33.1 28.0 22.3 33.1 3.7 7.|-- 180.240.191.41 0.0% 10 21.9 35.3 21.8 155.0 42.1 8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 9.|-- 180.240.204.62 0.0% 10 23.1 23.4 22.7 27.0 1.2 10.|-- sin-sg1-bb1-a9.sng.asia 0.0% 10 29.0 29.0 28.7 29.9 0.0 11.|-- sin1-sgcs2-g1-nc5.sng.asi 0.0% 10 29.5 29.4 29.2 29.7 0.0 12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 14.|-- sgp.smokeping.ovh.net 0.0% 10 23.1 23.1 22.9 23.6 0.0

  • OVH_APACOVH_APAC Member, Patron Provider

    Hello
    @pxhaxor,
    At this stage this is the best we can do from this provider. http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS9905

    @loveminds At this stage this is the best we can do from this provider. http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4134)

    @dgprasetya 23ms, Good latency! :-)

    @vpsGOD We will contact you in PM as our network team will require more details to assist you.

  • > @OVH_APAC said:

    Hello
    @pxhaxor,
    At this stage this is the best we can do from this provider. http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS9905

    @loveminds At this stage this is the best we can do from this provider. http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4134)

    @dgprasetya 23ms, Good latency! :-)

    @vpsGOD We will contact you in PM as our network team will require more details to assist you.

    China mobile is best, that China Telecom or Unicom via Tokyo but acceptable

  • @OVH_APAC Can u Add China Telecom Canton (AS58466,61.145.126.1) and China Unicom Canton (AS17622,58.248.72.1)

  • TFN(AS9924) to SGP OVH is horrible.
    TFN -> San Jose -> Chicago -> Palo Alto -> San Jose -> Singapore

    Besides, Hinet(AS3462), the largest ISP in Taiwan, has a bad routing with NTT.

    Hinet(AS3462) to SPG digitalocean is routing via TATA(AS6453) with a stable ping.

Sign In or Register to comment.