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

145791012

Comments

  • OVH_APACOVH_APAC Member, Patron Provider

    @sleepy said:
    @OVH_APAC How about I7-7700K or OC version in singapore?

    Hello @sleepy,
    You may check our upcoming Singapore servers here: https://www.ovh.com/asia/discover/what-is-next-in-singapore.xml
    I7-7700K are planned to be in stock by end of this month in both Singapore and Sydney datacenters. The OC version are only available in our european and north-american dacatenters at this stage.

  • rm_rm_ IPv6 Advocate, Veteran
    edited October 2018

    OVH_APAC said: This should be ok now:

    https://dnschecker.org/#AAAA/sgp.as16276.ovh
    https://dnschecker.org/#AAAA/syd.as16276.ovh

    Except you mixed them up, now sgp.as16276.ovh points to Australia:

    sgp.as16276.ovh has address 139.99.8.97
    sgp.as16276.ovh has IPv6 address 2402:1f00:8100:376::
    
    11. syd-sy2-bb2-a9.aus.asia          14.3%     7  312.9 313.3 312.6 314.9   0.6
    12. 2402:1f00:ffff:fe00::43          57.1%     7  311.3 311.3 310.9 311.7   0.0
    13. vl100.syd-d2-a72.aus.asia         0.0%     7  313.1 311.7 310.7 313.1   0.7
    14. be7.syd1-sdagg2a-n9.aus.asia      0.0%     6  312.8 312.3 311.3 314.3   1.1
    15. 2402:1f00:8100:376::              0.0%     6  311.9 313.2 311.9 314.4   1.0
    

    And syd.as16276.ovh points to Singapore.

    OVH_APAC said: Regarding your screenshot for the v6-side, could you provide more details

    Point is that when it breaks again, you will not know until we report it here or on the mailing list. All of OVH's Smokeping is v4-only, and there doesn't seem to be any other monitoring to track IPv6 failures -- it gets looked at only when users report that it's broken. This is lower effort spent on IPv6 than on IPv4, and as a result means overall lower quality and reliability of IPv6 at OVH compared to IPv4.

  • MikeAMikeA Member, Patron Provider

    @rm_ Speeds are typically much faster over v4, so I wouldn't recommend using v6 for majority of traffic anyways (at least in the other regions)

  • rm_rm_ IPv6 Advocate, Veteran

    MikeA said: Speeds are typically much faster over v4, so I wouldn't recommend using v6

    That's certainly a good idea if we want this to be the case forever.

  • OVH_APACOVH_APAC Member, Patron Provider

    @rm_ said:

    OVH_APAC said: This should be ok now:

    https://dnschecker.org/#AAAA/sgp.as16276.ovh
    https://dnschecker.org/#AAAA/syd.as16276.ovh

    Except you mixed them up, now sgp.as16276.ovh points to Australia:

    sgp.as16276.ovh has address 139.99.8.97
    > sgp.as16276.ovh has IPv6 address 2402:1f00:8100:376::
    > 
    > 11. syd-sy2-bb2-a9.aus.asia          14.3%     7  312.9 313.3 312.6 314.9   0.6
    > 12. 2402:1f00:ffff:fe00::43          57.1%     7  311.3 311.3 310.9 311.7   0.0
    > 13. vl100.syd-d2-a72.aus.asia         0.0%     7  313.1 311.7 310.7 313.1   0.7
    > 14. be7.syd1-sdagg2a-n9.aus.asia      0.0%     6  312.8 312.3 311.3 314.3   1.1
    > 15. 2402:1f00:8100:376::              0.0%     6  311.9 313.2 311.9 314.4   1.0
    > 

    And syd.as16276.ovh points to Singapore.

    OVH_APAC said: Regarding your screenshot for the v6-side, could you provide more details

    Point is that when it breaks again, you will not know until we report it here or on the mailing list. All of OVH's Smokeping is v4-only, and there doesn't seem to be any other monitoring to track IPv6 failures -- it gets looked at only when users report that it's broken. This is lower effort spent on IPv6 than on IPv4, and as a result means overall lower quality and reliability of IPv6 at OVH compared to IPv4.

    Hello @rm_
    Sorry for mixing up sgp/syd, we are fixing this now.
    Regarding IPv6 tools and reliability, I will push again this topic internally. Many thanks for your feedback.

    Thanked by 2rm_ flonetmelb
  • OVH_APACOVH_APAC Member, Patron Provider

    Hello,
    For those in Singapore the connection to Singtel has been improved and down to 2.5ms latency now!

    http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS9506

    Thanked by 1Hax
  • PINGAPACPINGAPAC Member
    edited November 2018

    Going to be hard to "benefit" from these 2.5ms "improvements" given the lack of available and interesting cheap offers VPS/cloud products in that datacenter to begin with...

    Thanked by 1sibaper
  • XeiXei Member
    edited November 2018

    ^ Mostly this, aside the fact their VPS line is a performance shit show. Bring on the Kimsufi's... or SYS ARM storage.

  • OVH_APACOVH_APAC Member, Patron Provider

    Hello,
    We made a latency improvement between OVH Singapore Datacenter and Philippines:
    SKYBroadband SKYCable Corp (AS23944 114.108.211.1) => down to ~70ms

    http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS23944

    We are continuously working on improving our network, if you experience latency issue with your OVH service in Singapore or Sydney, 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)
    2. Save the traceroute results
    3. Send a blank email to [email protected]
    4. Follow the instructions in the automated reply to sign up to the mailing list
    5. Send your traceroute results to [email protected] and the team will investigate

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

    Thanked by 2desperand eva2000
  • @OVH_APAC can you improve the ipv6 connectivity between Telekom Malaysia ISP and OVH Singapore? With IPv4,the lowest latency can get less than 10ms. But With IPv6,already few months the connection for ipv6 still bad.

  • OVH_APACOVH_APAC Member, Patron Provider

    Hello @go626201

    According to the below traceroute, we advise you to contact your ISP as the latency is increasing on the 6th hop (Telekom Malaysia).

    sin1-sgcs2 ~] > mtr 2001:e68:402c:8001::77 -zr
    Start: Mon Dec 17 05:09:31 2018
    HOST: sin1-sgcs2.smokeping.ovh.ne Loss% Snt Last Avg Best Wrst StDev
    1. AS16276 2402:1f00:8000:2ff: 0.0% 10 0.9 0.9 0.7 1.1 0.0
    2. AS16276 be101.sgp-d1-a72.sn 0.0% 10 0.8 0.7 0.6 0.9 0.0
    3. AS16276 be100-100.sin1-sgcs 10.0% 10 1.3 1.2 1.0 1.5 0.0
    4. AS16276 2402:1f00:ffff:fe00 40.0% 10 1.8 1.7 1.6 1.8 0.0
    5. AS??? 4788.sgw.equinix.co 0.0% 10 1.0 1.0 0.8 1.0 0.0
    ** 6. AS4788 2001:e68:402c:8001: 0.0% 10 73.9 73.9 73.7 74.0 0.0**

    Sorry we could not help further on your case.

  • @OVH_APAC Any updates regarding the availability of VPS/Cloud products in the Singapore DC?

    Also, any plans (even in a distant future) to open a DC in HK?

  • OVH_APACOVH_APAC Member, Patron Provider

    Hello @tcp6,
    Regarding Cloud products in Singapore DC, it is coming soon, you can find more and info and register your interest here to be alerted as soon as it is available. https://www.ovh.com/asia/discover/what-is-next-in-singapore.xml#public-cloud

    Regarding a DC in Hong-Kong, there are no plans at this stage as Singapore Datacenter is only around ~35 to 40ms away depending on your provider (example: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS45753)

    Do let us know if you experience higher latency.
    Thank you

    SGP => HKG (Netsec example)

  • @OVH_APAC said:
    Hello @tcp6,
    Regarding Cloud products in Singapore DC, it is coming soon, you can find more and info and register your interest here to be alerted as soon as it is available. https://www.ovh.com/asia/discover/what-is-next-in-singapore.xml#public-cloud

    Regarding a DC in Hong-Kong, there are no plans at this stage as Singapore Datacenter is only around ~35 to 40ms away depending on your provider (example: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS45753)

    Do let us know if you experience higher latency.
    Thank you

    SGP => HKG (Netsec example)

    How about latam?

  • tcp6tcp6 Member
    edited December 2018

    @inthecloudblog said:
    How about latam?

    Enquiring about LATAM in a thread dedicated to the APAC region and expecting an answer? Okay... :neutral:

  • OVH_APACOVH_APAC Member, Patron Provider

    Hello,
    We just made a big improvement with Netvigator, a residential Internet service provider in Hong Kong. --> now down to 35ms from our Singapore datacenter.

    Singapore: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4760
    Sydney: http://syd.smokeping.ovh.net/smokeping?target=APAC.AS4760

    Would you like to see some improvements on the OVH Network from our Singapore (SGP) or Sydney (SYD) datacenter?

    Please send us your traceroute results by completing the short form available at:
    http://traceroute.apac-tools.ovh

    • To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
    • To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server IP)
    • copy the traceroute results
    • Complete the form http://traceroute.apac-tools.ovh
    • Our Network team will investigate and get back to you

    OVH Tools:

  • @OVH_APAC said:
    Hello,
    We just made a big improvement with Netvigator, a residential Internet service provider in Hong Kong. --> now down to 35ms from our Singapore datacenter.

    Singapore: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4760
    Sydney: http://syd.smokeping.ovh.net/smokeping?target=APAC.AS4760

    Would you like to see some improvements on the OVH Network from our Singapore (SGP) or Sydney (SYD) datacenter?

    Please send us your traceroute results by completing the short form available at:
    http://traceroute.apac-tools.ovh

    • To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
    • To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server IP)
    • copy the traceroute results
    • Complete the form http://traceroute.apac-tools.ovh
    • Our Network team will investigate and get back to you

    OVH Tools:

    Thx for improving the network latency between HK and SG :smile: Also, if someone DDoS the SG server, will the system going to reroute those traffic to France for mitigation? or will it do the mitigation in the local data centre? Thanks.

  • taiwan fixed network

    PING 60.199.206.252 (60.199.206.252) 56(84) bytes of data.
    64 bytes from 60.199.206.252: icmp_seq=1 ttl=48 time=171 ms
    64 bytes from 60.199.206.252: icmp_seq=2 ttl=48 time=171 ms
    64 bytes from 60.199.206.252: icmp_seq=3 ttl=48 time=171 ms
    64 bytes from 60.199.206.252: icmp_seq=4 ttl=48 time=170 ms
    64 bytes from 60.199.206.252: icmp_seq=5 ttl=48 time=170 ms
    ^C
    --- 60.199.206.252 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4003ms
    rtt min/avg/max/mdev = 170.870/171.000/171.158/0.278 ms
    
    traceroute to 60.199.206.252 (60.199.206.252), 30 hops max, 60 byte packets
     1  gateway (139.99.40.1)  0.200 ms
     2  192.168.250.254 (192.168.250.254)  0.186 ms
     3  10.29.193.254 (10.29.193.254)  0.204 ms
     4  10.29.192.14 (10.29.192.14)  0.202 ms
     5  10.133.2.28 (10.133.2.28)  0.428 ms
     6  10.75.0.8 (10.75.0.8)  0.233 ms
     7  10.75.248.2 (10.75.248.2)  0.986 ms
     8  sin1-sgcs2-g1-nc5.sng.asia (103.5.15.224)  1.001 ms
     9  sin-sg1-bb1-a9.sng.asia (103.5.15.4)  1.257 ms
    10  203.78.181.173 (203.78.181.173)  172.041 ms
    11  203.78.181.173 (203.78.181.173)  172.043 ms
    12  *
    13  60-199-16-202.static.tfn.net.tw (60.199.16.202)  171.211 ms
    14  60-199-16-202.static.tfn.net.tw (60.199.16.202)  171.225 ms
    15  61-30-166-54.static.tfn.net.tw (61.30.166.54)  171.236 ms
    16  175-99-125-130.static.tfn.net.tw (175.99.125.130)  171.360 ms
    17  175-99-125-2.static.tfn.net.tw (175.99.125.2)  170.971 ms
    18  60-199-206-252.static.tfn.net.tw (60.199.206.252)  170.972 ms
    

    kbronet.com.tw

    PING 123.195.236.110 (123.195.236.110) 56(84) bytes of data.
    64 bytes from 123.195.236.110: icmp_seq=1 ttl=46 time=176 ms
    64 bytes from 123.195.236.110: icmp_seq=2 ttl=46 time=175 ms
    64 bytes from 123.195.236.110: icmp_seq=3 ttl=46 time=175 ms
    64 bytes from 123.195.236.110: icmp_seq=4 ttl=46 time=175 ms
    64 bytes from 123.195.236.110: icmp_seq=5 ttl=46 time=175 ms
    ^C
    --- 123.195.236.110 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4005ms
    rtt min/avg/max/mdev = 175.809/175.949/176.085/0.281 ms
    
    traceroute to 123.195.236.110 (123.195.236.110), 30 hops max, 60 byte packets
     1  gateway (139.99.40.1)  0.309 ms
     2  192.168.250.254 (192.168.250.254)  0.301 ms
     3  10.29.193.254 (10.29.193.254)  0.298 ms
     4  10.29.192.16 (10.29.192.16)  0.294 ms
     5  10.133.2.28 (10.133.2.28)  0.508 ms
     6  10.75.0.8 (10.75.0.8)  0.275 ms
     7  10.75.248.2 (10.75.248.2)  0.865 ms
     8  sin-sg1-bb1-a9.sng.asia (103.5.15.4)  1.271 ms
     9  sin-sg1-bb1-a9.sng.asia (103.5.15.4)  1.384 ms
    10  ae-1.r20.sngpsi07.sg.bb.gin.ntt.net (129.250.3.83)  1.249 ms
    11  ae-9.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.7.67)  35.008 ms
    12  ae-9.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.7.67)  35.031 ms
    13  ae-1.r02.taiptw01.tw.bb.gin.ntt.net (129.250.2.83)  58.485 ms
    14  xe-0-6-0-3-4.r02.taiptw01.tw.ce.gin.ntt.net (61.58.33.238)  175.783 ms
    15  xe-0-6-0-2-6.r02.taiptw01.tw.ce.gin.ntt.net (61.58.33.10)  195.046 ms
    16  60-199-4-214.static.tfn.net.tw (60.199.4.214)  176.764 ms
    17  219-80-114-10.static.tfn.net.tw (219.80.114.10)  176.584 ms
    18  *
    19  *
    20  123-195-236-110.dynamic.kbronet.com.tw (123.195.236.110)  175.590 ms !X
    

    taiwan edu

    PING 140.134.135.134 (140.134.135.134) 56(84) bytes of data.
    64 bytes from 140.134.135.134: icmp_seq=1 ttl=44 time=298 ms
    64 bytes from 140.134.135.134: icmp_seq=2 ttl=44 time=298 ms
    64 bytes from 140.134.135.134: icmp_seq=3 ttl=44 time=298 ms
    64 bytes from 140.134.135.134: icmp_seq=4 ttl=44 time=298 ms
    ^C
    --- 140.134.135.134 ping statistics ---
    5 packets transmitted, 4 received, 20% packet loss, time 4005ms
    rtt min/avg/max/mdev = 298.709/298.772/298.915/0.083 ms
    
    traceroute to 140.134.135.134 (140.134.135.134), 30 hops max, 60 byte packets
     1  gateway (139.99.40.1)  0.333 ms
     2  192.168.250.254 (192.168.250.254)  0.314 ms
     3  10.29.193.254 (10.29.193.254)  0.303 ms
     4  10.29.192.16 (10.29.192.16)  0.294 ms
     5  10.133.2.24 (10.133.2.24)  0.459 ms
     6  10.75.0.8 (10.75.0.8)  0.275 ms
     7  10.75.248.2 (10.75.248.2)  0.647 ms
     8  sin-gss1-bb1-a9.sng.asia (103.5.15.16)  1.023 ms
     9  sin-gss1-bb1-a9.sng.asia (103.5.15.16)  1.116 ms
    10  sjo-sv5-bb1-a9.ca.us (103.5.15.29)  160.601 ms
    11  public-peering-twgate.net (198.32.176.160)  160.895 ms
    12  public-peering-twgate.net (198.32.176.160)  160.876 ms
    13  9-60-41-175.TWGATE-IP.twgate.net (175.41.60.9)  161.110 ms
    14  203.72.43.29 (203.72.43.29)  298.681 ms
    15  203.72.43.29 (203.72.43.29)  299.945 ms
    16  192.192.61.66 (192.192.61.66)  296.470 ms
    17  192.192.61.1 (192.192.61.1)  298.030 ms
    18  192.192.61.34 (192.192.61.34)  297.387 ms
    19  192.192.61.10 (192.192.61.10)  300.940 ms
    20  192.192.61.121 (192.192.61.121)  298.818 ms
    21  140.134.7.253 (140.134.7.253)  301.761 ms
    22  140.134.7.253 (140.134.7.253)  300.033 ms
    23  140.134.7.253 (140.134.7.253)  299.993 ms
    24  140.134.135.134 (140.134.135.134)  299.041 ms
    
  • OVH_APACOVH_APAC Member, Patron Provider

    @leechitat said:

    @OVH_APAC said:
    Hello,
    We just made a big improvement with Netvigator, a residential Internet service provider in Hong Kong. --> now down to 35ms from our Singapore datacenter.

    Singapore: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4760
    Sydney: http://syd.smokeping.ovh.net/smokeping?target=APAC.AS4760

    Would you like to see some improvements on the OVH Network from our Singapore (SGP) or Sydney (SYD) datacenter?

    Please send us your traceroute results by completing the short form available at:
    http://traceroute.apac-tools.ovh

    • To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
    • To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server IP)
    • copy the traceroute results
    • Complete the form http://traceroute.apac-tools.ovh
    • Our Network team will investigate and get back to you

    OVH Tools:

    Thx for improving the network latency between HK and SG :smile: Also, if someone DDoS the SG server, will the system going to reroute those traffic to France for mitigation? or will it do the mitigation in the local data centre? Thanks.

    Hello @leechitat,
    OVH anti-DDoS technology is replicated in all our datacenters. The VAC (Vacuuming) is activated simultaneously in all of these datacentres, so that all regions can combine their power and absorb the traffic. They have a combined capacity of more than 4 Tbit/s.
    You can read more here: https://www.ovh.com/asia/anti-ddos/

    Thanked by 1leechitat
  • @OVH_APAC said:

    @leechitat said:

    @OVH_APAC said:
    Hello,
    We just made a big improvement with Netvigator, a residential Internet service provider in Hong Kong. --> now down to 35ms from our Singapore datacenter.

    Singapore: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4760
    Sydney: http://syd.smokeping.ovh.net/smokeping?target=APAC.AS4760

    Would you like to see some improvements on the OVH Network from our Singapore (SGP) or Sydney (SYD) datacenter?

    Please send us your traceroute results by completing the short form available at:
    http://traceroute.apac-tools.ovh

    • To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
    • To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server IP)
    • copy the traceroute results
    • Complete the form http://traceroute.apac-tools.ovh
    • Our Network team will investigate and get back to you

    OVH Tools:

    Thx for improving the network latency between HK and SG :smile: Also, if someone DDoS the SG server, will the system going to reroute those traffic to France for mitigation? or will it do the mitigation in the local data centre? Thanks.

    Hello @leechitat,
    OVH anti-DDoS technology is replicated in all our datacenters. The VAC (Vacuuming) is activated simultaneously in all of these datacentres, so that all regions can combine their power and absorb the traffic. They have a combined capacity of more than 4 Tbit/s.
    You can read more here: https://www.ovh.com/asia/anti-ddos/

    When is the public cloud available at Singapore?

  • OVH_APACOVH_APAC Member, Patron Provider
    edited January 2019

    @stefeman said:

    @OVH_APAC said:

    @leechitat said:

    @OVH_APAC said:
    Hello,
    We just made a big improvement with Netvigator, a residential Internet service provider in Hong Kong. --> now down to 35ms from our Singapore datacenter.

    Singapore: http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4760
    Sydney: http://syd.smokeping.ovh.net/smokeping?target=APAC.AS4760

    Would you like to see some improvements on the OVH Network from our Singapore (SGP) or Sydney (SYD) datacenter?

    Please send us your traceroute results by completing the short form available at:
    http://traceroute.apac-tools.ovh

    • To run a traceroute on Linux, enter the following terminal command: traceroute sgp.smokeping.ovh.net (or your OVH server IP)
    • To run a traceroute on Windows, enter the following command line: tracert sgp.smokeping.ovh.net (or your OVH server IP)
    • copy the traceroute results
    • Complete the form http://traceroute.apac-tools.ovh
    • Our Network team will investigate and get back to you

    OVH Tools:

    Thx for improving the network latency between HK and SG :smile: Also, if someone DDoS the SG server, will the system going to reroute those traffic to France for mitigation? or will it do the mitigation in the local data centre? Thanks.

    Hello @leechitat,
    OVH anti-DDoS technology is replicated in all our datacenters. The VAC (Vacuuming) is activated simultaneously in all of these datacentres, so that all regions can combine their power and absorb the traffic. They have a combined capacity of more than 4 Tbit/s.
    You can read more here: https://www.ovh.com/asia/anti-ddos/

    When is the public cloud available at Singapore?

    Hello @stefeman

    OVH Public Cloud solution, including cheap sandboxes (+ Pay-as-you-go, additional storage, snapshots) will be made available in Singapore and in Australia (2 new regions) early this year (few weeks from now - our tech teams are deploying this solution as we speak). I will definitely advise as soon as I can communicate a firm ETA. You can find more info: https://www.ovh.com/asia/discover/what-is-next-in-singapore.xml

  • Quick question regarding existing VPS services in the APAC region:

    Let’s say for the purpose of this example that I have 3 of the discontinued APAC VPS 1 offers which each are bundled with 1TB of monthly traffic.

    Now I would like clarification on the folliwing point:

    Is the traffic between each of these VPS servers counting towards my monthly bandwidth quota? Or is the traffic between OVH VPS servers within the same DC and probably the same physical racks considered as “free traffic”?

    Thanks.

  • Any plans to introduce cheap storage in AU?

  • OVH_APACOVH_APAC Member, Patron Provider

    @tcp6 said:
    Quick question regarding existing VPS services in the APAC region:

    Let’s say for the purpose of this example that I have 3 of the discontinued APAC VPS 1 offers which each are bundled with 1TB of monthly traffic.

    Now I would like clarification on the folliwing point:

    Is the traffic between each of these VPS servers counting towards my monthly bandwidth quota? Or is the traffic between OVH VPS servers within the same DC and probably the same physical racks considered as “free traffic”?

    Thanks.

    Hello @tcp6,
    The discontinued VPS APAC offer does not benefit from a Private Network interface (vRack), which also means you would be using the public network get these VPS to communicate between each other; as a result the traffic will be accounted in your monthly quota (only upload)
    (so if you push some data from one VPS APAC (let's call it A) to another (B) only the upload will be counted on A, the download to B is "free traffic").

    Hope this helps

  • OVH_APACOVH_APAC Member, Patron Provider

    @dahartigan said:
    Any plans to introduce cheap storage in AU?

    Hello @dahartigan,
    short answer: yes!
    long answer:
    As part of our public cloud solution opening soon in AU, you will also benefit from our OVH storage solutions. Not too sure what type of storage you are after here but to summarize:

    • If you have a Public Cloud server you will get storage included with the price of your server which can be extended (it is called additional disks)
    • We will also offer Object storage. (immediate HTTP access powered by OpenStack Swift)
    • as well as Cloud archive (Long-term archiving)

    find more details here: https://www.ovh.com.au/public-cloud/storage/

    NB: The storage price will be the same in Australia and Singapore, however please note when an outgoing (or incoming traffic) charge applies, the traffic cost in Australia and Singapore will be higher (due to the higher bandwidth cost in this part of the world), however it will remain very competitive for the region.
    Full pricing details will be revealed in a few weeks from now.

    Do not hesitate if you have further questions.

  • dahartigandahartigan Member
    edited January 2019

    @OVH_APAC said:

    @dahartigan said:
    Any plans to introduce cheap storage in AU?

    Hello @dahartigan,
    short answer: yes!
    long answer:
    As part of our public cloud solution opening soon in AU, you will also benefit from our OVH storage solutions. Not too sure what type of storage you are after here but to summarize:

    • If you have a Public Cloud server you will get storage included with the price of your server which can be extended (it is called additional disks)
    • We will also offer Object storage. (immediate HTTP access powered by OpenStack Swift)
    • as well as Cloud archive (Long-term archiving)

    find more details here: https://www.ovh.com.au/public-cloud/storage/

    NB: The storage price will be the same in Australia and Singapore, however please note when an outgoing (or incoming traffic) charge applies, the traffic cost in Australia and Singapore will be higher (due to the higher bandwidth cost in this part of the world), however it will remain very competitive for the region.
    Full pricing details will be revealed in a few weeks from now.

    Do not hesitate if you have further questions.

    Thanks for the response! Right now I've managed to get an amazing VPS deal on around 700GB of HDD that's based on one of your Sydney dedicated servers, and it costs me around $17 AUD per month - for reference. Usage is very minimal IO really, it's for a nextCloud and small 1 user Plex setup - object storage would work for me for both of these purposes. If the price is right, of course.

    I know that's a hard one to do because of the region, I'm Australian (Brisbane) so the reduced ping (normally I'd use LA servers for the price/features/ping ratio) but I certainly understand the Aussie stuff is highly premium :)

    EDIT: I forgot to mention, my bandwidth usage combined would not likely approach 1TB/month in both directions.

    Thanked by 1OVH_APAC
  • @OVH_APAC said:
    The discontinued VPS APAC offer does not benefit from a Private Network interface (vRack), which also means you would be using the public network get these VPS to communicate between each other; as a result the traffic will be accounted in your monthly quota (only upload)

    Will the upcoming Cloud/VPS offers have the vRack option activated by default or at least toggled on?

    (so if you push some data from one VPS APAC (let's call it A) to another (B) only the upload will be counted on A, the download to B is "free traffic").

    Perfectly crystal clear explanation, I’m loving it.

    One question though; Will we be able to see bandwidth usage stats from within our control panels at some point in the near future specially with the upcoming Cloud offers?

    Hope this helps

    It sure did! Perfect. Flawless.

    One last unrelated question though; let’s say that these 3 VPS servers are “saturating” their ens3 port at 100Mbit 24/7 then at 10Mbit/s once their monthly bandwidth allocation has been exhausted. Will it attract attention? Is it grounds for service suspension? Or you guys at OVH just don’t care at all?

  • OVH_APACOVH_APAC Member, Patron Provider

    @tcp6 said:

    @OVH_APAC said:
    The discontinued VPS APAC offer does not benefit from a Private Network interface (vRack), which also means you would be using the public network get these VPS to communicate between each other; as a result the traffic will be accounted in your monthly quota (only upload)

    Will the upcoming Cloud/VPS offers have the vRack option activated by default or at least toggled on?

    (so if you push some data from one VPS APAC (let's call it A) to another (B) only the upload will be counted on A, the download to B is "free traffic").

    Perfectly crystal clear explanation, I’m loving it.

    One question though; Will we be able to see bandwidth usage stats from within our control panels at some point in the near future specially with the upcoming Cloud offers?

    Hope this helps

    It sure did! Perfect. Flawless.

    One last unrelated question though; let’s say that these 3 VPS servers are “saturating” their ens3 port at 100Mbit 24/7 then at 10Mbit/s once their monthly bandwidth allocation has been exhausted. Will it attract attention? Is it grounds for service suspension? Or you guys at OVH just don’t care at all?

    Hello @tcp6,
    Public Cloud instances have the vRack Private network capability so you can build an infra. (you only need to activate the option in your Cloud control panel). This is included in the price but you'll get higher bandwidth with bigger instances.

    Traffic usage will be visible in the control panel or via API for your Public cloud instances.
    (no changes on the discontinued VPS APAC offer)

    Regarding your last question, you will definitely attract attention if you are exceeding your monthly allowance by too much and repetitively...

    Thanked by 1tcp6
  • tcp6tcp6 Member
    edited January 2019

    @OVH_APAC said:
    Public Cloud instances have the vRack Private network capability so you can build an infra. (you only need to activate the option in your Cloud control panel). This is included in the price but you'll get higher bandwidth with bigger instances.

    Higher bandwidth if you active the vRack option or just higher bandwidth on the new upcoming offers?

    Traffic usage will be visible in the control panel or via API for your Public cloud instances.
    (no changes on the discontinued VPS APAC offer)

    That’s great news for the new customers, not so much for the lasting ones though.

    Regarding your last question, you will definitely attract attention if you are exceeding your monthly allowance by too much and repetitively...

    I understand a VPS is a shared ressource, not tjere to be constantly abused. The phrasing was rather poor, the question should rather be, in terms of bandwidth usage, is there a sane threshold?

    Thanks.

  • OVH_APACOVH_APAC Member, Patron Provider

    Hello @tcp6,
    The bandwidth for vRack Private network (and also for the Public network interface) is displayed here by for each Public cloud instance: https://www.ovh.com.au/public-cloud/instances/prices/
    Regarding your last question, I'm not sure to get it but regarding the discontinued VPS APAC offer, these VPS are capped at 100Mbps (best effort) for the duration of your traffic quota included with it then it drops to 10Mbps.

Sign In or Register to comment.