Howdy, Stranger!

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


Lowest Ping You Get On A VPS
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.

Lowest Ping You Get On A VPS

OneTwoOneTwo Member
edited April 2012 in General

What's the lowest ping you get from your home on a vps that you own?

Mine is 86ms with XenVZ.

«1

Comments

  • 
    [root@sapphire ~]# vzlist | grep dns-ipxcore
           106         22 running   69.53.223.158   dns-ipxcore.ipxcore.com
    [root@sapphire ~]# vzctl enter 106
    entered into CT 106
    root@dns-ipxcore [/]# ping 216.224.230.136
    PING 216.224.230.136 (216.224.230.136) 56(84) bytes of data.
    64 bytes from 216.224.230.136: icmp_seq=1 ttl=64 time=0.063 ms
    64 bytes from 216.224.230.136: icmp_seq=2 ttl=64 time=0.037 ms
    64 bytes from 216.224.230.136: icmp_seq=3 ttl=64 time=0.056 ms
    64 bytes from 216.224.230.136: icmp_seq=4 ttl=64 time=0.035 ms
    64 bytes from 216.224.230.136: icmp_seq=5 ttl=64 time=0.055 ms
    ^C
    --- 216.224.230.136 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4319ms
    rtt min/avg/max/mdev = 0.035/0.049/0.063/0.012 ms
    root@dns-ipxcore [/]#
    

    216.224.230.136 is the host node :D

  • From your home to vps...

  • vldvld Member
    edited April 2012
    
    Reply from 178.157.xx.xxx: bytes=32 time=1ms TTL=57
    Reply from 178.157.xx.xxx: bytes=32 time=1ms TTL=57
    Reply from 178.157.xx.xxx: bytes=32 time=1ms TTL=57
    
    Ping statistics for 178.157.xx.xxx:
        Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 2ms, Average = 1ms
  • BassHostBassHost Member
    edited April 2012

    Oh how you should not be posting your ips.

    Reply from 2XX.1X0.XX.1: bytes=32 time=35ms TTL=50

    Reply from 2XX.1X0.XX.1: bytes=32 time=37ms TTL=50
    Reply from 2XX.1X0.XX.1: bytes=32 time=38ms TTL=50
    Reply from 2XX.1X0.XX.1: bytes=32 time=35ms TTL=50

    Ping statistics for 2XX.1X0.XX.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 35ms, Maximum = 38ms, Average = 36ms

    Not shabby ... east coast to kansas, city.

    Reply from X9X.X2.09.X: bytes=32 time=24ms TTL=52

    Reply from X9X.X2.09.X: bytes=32 time=23ms TTL=52
    Reply from X9X.X2.09.X: bytes=32 time=25ms TTL=52
    Reply from X9X.X2.09.X: bytes=32 time=23ms TTL=52

    Ping statistics for X9X.X2.09.X:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 23ms, Maximum = 25ms, Average = 23ms

    North east coast to secret location. You guys will find out soon.

  • Ash_HawkridgeAsh_Hawkridge Member
    edited April 2012

    @BassHost said: Oh how you should not be posting your ips.

    Yep, you do realize your on LET don't you?, it was only a few weeks back that providers were getting DDoS'd left, right and center.

  • dmmcintyre3dmmcintyre3 Member
    edited April 2012

    From Hostigation NC to my home PC (over OpenVPN). I live ~30 miles from the datacenter and my ISP has connections to the DC.

    ping 10.8.0.26 -c 4
    PING 10.8.0.26 (10.8.0.26) 56(84) bytes of data.
    64 bytes from 10.8.0.26: icmp_seq=1 ttl=64 time=22.5 ms
    64 bytes from 10.8.0.26: icmp_seq=2 ttl=64 time=22.7 ms
    64 bytes from 10.8.0.26: icmp_seq=3 ttl=64 time=19.6 ms
    64 bytes from 10.8.0.26: icmp_seq=4 ttl=64 time=19.8 ms
    
    --- 10.8.0.26 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3024ms
    rtt min/avg/max/mdev = 19.661/21.223/22.760/1.460 ms

    It changes often, last week I was able to get 10ms for a day or two.

  • yomeroyomero Member
    edited April 2012
    64 bytes from 208.X.X.X: icmp_req=2 ttl=46 time=45.2 ms
    

    At Dallas,TX

  • netomxnetomx Moderator, Veteran
    edited April 2012
    Haciendo ping a whocares [67.x.x.x] con 32 bytes de datos:
    Respuesta desde 67.x.x.x: bytes=32 tiempo=107ms TTL=43
    Respuesta desde 67.x.x.x: bytes=32 tiempo=93ms TTL=43
    Respuesta desde 67.x.x.x: bytes=32 tiempo=117ms TTL=43
    Respuesta desde 67.x.x.x: bytes=32 tiempo=440ms TTL=43
    

    Shitty WiMax connection (2mbps) and 25 computers hooked into it. haha

  • From my home to old DC in SC and new in NC, mad cuz cable company dumped Level3 for Cogent

    tim@openfiler:~$ ping -qnc 5 hot
    PING hot.hostigation.com (216.189.*.*) 56(84) bytes of data.
    
    --- hot.hostigation.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4003ms
    rtt min/avg/max/mdev = 16.570/19.215/23.093/2.267 ms
    tim@openfiler:~$ ping -qnc 5 dns3
    PING dns3.hostigation.com (69.85.*.*) 56(84) bytes of data.
    
    --- dns3.hostigation.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4005ms
    rtt min/avg/max/mdev = 33.493/36.480/46.287/4.925 ms
    
  • Daniels-MacBook-Pro:~ daniel$ ping landofdaniel.com
    PING landofdaniel.com (178.79.160.198): 56 data bytes
    64 bytes from 178.79.160.198: icmp_seq=0 ttl=50 time=34.029 ms
    64 bytes from 178.79.160.198: icmp_seq=1 ttl=50 time=33.429 ms
    64 bytes from 178.79.160.198: icmp_seq=2 ttl=50 time=33.621 ms
    --- landofdaniel.com ping statistics ---
    3 packets transmitted, 3 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 33.429/33.693/34.029/0.250 ms
    

    LinodeUK.

  • gianggiang Veteran

    Lowest ping I got is about 65ms, from Bien Hoa, Viet Nam to Singapore VPS :D

  • gsrdgrdghdgsrdgrdghd Member
    edited April 2012
    10 packets transmitted, 10 received, 0% packet loss, time 9013ms
    rtt min/avg/max/mdev = 13.248/16.031/22.649/2.680 ms

    To my misterhost.de VPS

  • vedranvedran Veteran
    Ping statistics for x.x.x.x:
        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 31ms, Maximum = 33ms, Average = 31ms

    Not bad for ~800km. Also, windows ftw

  • SteveSteve Member
    edited April 2012
    Pinging 109.169.**.*** with 32 bytes of data:
    Reply from 109.169.**.***: bytes=32 time=22ms TTL=116
    Reply from 109.169.**.***: bytes=32 time=23ms TTL=116
    Reply from 109.169.**.***: bytes=32 time=22ms TTL=116
    Reply from 109.169.**.***: bytes=32 time=22ms TTL=116
    
    Ping statistics for 109.169.**.***:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 22ms, Maximum = 23ms, Average = 22ms

    From Northern Ireland to Maidenhead in UK, which according to Google is 408.8 miles away from me.

  • JTRJTR Member

    Do I win?

    [root@Skynet ~]# ping -c 5 localhost
    PING localhost (127.0.0.1) 56(84) bytes of data.
    64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.038 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.046 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.053 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.059 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.053 ms
    
    --- localhost ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4001ms
    rtt min/avg/max/mdev = 0.038/0.049/0.059/0.011 ms
  • InfinityInfinity Member, Host Rep
    edited April 2012

    @JTR If you want to play that game, I win! Just about from a VM on my computer. :P

    [root@jupiter ~]# ping -c 4 localhost
    PING localhost (127.0.0.1) 56(84) bytes of data.
    64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.026 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.039 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.044 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.044 ms
    
    --- localhost ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2999ms
    rtt min/avg/max/mdev = 0.026/0.038/0.044/0.008 ms
    

    Even better from my Hostigation, the best out of my VPSs.

    root@alpha:~# ping -c 4 localhost
    PING localhost (127.0.0.1) 56(84) bytes of data.
    64 bytes from localhost (127.0.0.1): icmp_req=1 ttl=64 time=0.020 ms
    64 bytes from localhost (127.0.0.1): icmp_req=2 ttl=64 time=0.019 ms
    64 bytes from localhost (127.0.0.1): icmp_req=3 ttl=64 time=0.019 ms
    64 bytes from localhost (127.0.0.1): icmp_req=4 ttl=64 time=0.019 ms
    
    --- localhost ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2997ms
    rtt min/avg/max/mdev = 0.019/0.019/0.020/0.003 ms
    
  • JTRJTR Member

    @Infinity

    [root@a304 ~]# ping -c 5 localhost
    PING localhost (127.0.0.1) 56(84) bytes of data.
    64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.027 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.033 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.036 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.037 ms
    64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.034 ms
    
    --- localhost ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 3999ms
    rtt min/avg/max/mdev = 0.027/0.033/0.037/0.006 ms
  • InfinityInfinity Member, Host Rep

    @JTR :( At least my Hostigation beats that..

  • JTRJTR Member

    @Infinity To be fair, it's a dedicated box :P

    [root@a304 ~]# ping -c 5 google.com
    PING google.com (74.125.225.69) 56(84) bytes of data.
    64 bytes from ord08s07-in-f5.1e100.net (74.125.225.69): icmp_seq=1 ttl=57 time=14.5 ms
    64 bytes from ord08s07-in-f5.1e100.net (74.125.225.69): icmp_seq=2 ttl=57 time=13.8 ms
    64 bytes from ord08s07-in-f5.1e100.net (74.125.225.69): icmp_seq=3 ttl=57 time=14.3 ms
    64 bytes from ord08s07-in-f5.1e100.net (74.125.225.69): icmp_seq=4 ttl=57 time=14.2 ms
    64 bytes from ord08s07-in-f5.1e100.net (74.125.225.69): icmp_seq=5 ttl=57 time=14.1 ms
    
    --- google.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4018ms
    rtt min/avg/max/mdev = 13.861/14.226/14.524/0.226 ms
    
    [root@a304 ~]# ping -c 5 lowendtalk.com
    PING lowendtalk.com (108.174.48.101) 56(84) bytes of data.
    64 bytes from host.colocrossing.com (108.174.48.101): icmp_seq=1 ttl=54 time=16.9 ms
    64 bytes from host.colocrossing.com (108.174.48.101): icmp_seq=2 ttl=54 time=18.4 ms
    64 bytes from host.colocrossing.com (108.174.48.101): icmp_seq=3 ttl=54 time=17.3 ms
    64 bytes from host.colocrossing.com (108.174.48.101): icmp_seq=4 ttl=54 time=17.6 ms
    64 bytes from host.colocrossing.com (108.174.48.101): icmp_seq=5 ttl=54 time=16.8 ms
    
    --- lowendtalk.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4017ms
    rtt min/avg/max/mdev = 16.872/17.464/18.482/0.577 ms
    
    [root@a304 ~]# ping -c 5 cachefly.net
    PING cachefly.net.net (174.132.240.146) 56(84) bytes of data.
    64 bytes from 92.f0.84ae.static.theplanet.com (174.132.240.146): icmp_seq=1 ttl=118 time=54.6 ms
    64 bytes from 92.f0.84ae.static.theplanet.com (174.132.240.146): icmp_seq=2 ttl=118 time=54.9 ms
    64 bytes from 92.f0.84ae.static.theplanet.com (174.132.240.146): icmp_seq=3 ttl=118 time=56.0 ms
    64 bytes from 92.f0.84ae.static.theplanet.com (174.132.240.146): icmp_seq=4 ttl=118 time=54.9 ms
    64 bytes from 92.f0.84ae.static.theplanet.com (174.132.240.146): icmp_seq=5 ttl=118 time=55.4 ms
    
    --- cachefly.net.net ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4060ms
    rtt min/avg/max/mdev = 54.605/55.189/56.001/0.523 ms
    
    [root@a304 ~]# ping -c 5 proof.ovh.net
    PING proof.ovh.net (188.165.12.106) 56(84) bytes of data.
    64 bytes from proof.ovh.net (188.165.12.106): icmp_seq=1 ttl=55 time=88.9 ms
    64 bytes from proof.ovh.net (188.165.12.106): icmp_seq=2 ttl=55 time=88.1 ms
    64 bytes from proof.ovh.net (188.165.12.106): icmp_seq=3 ttl=55 time=88.7 ms
    64 bytes from proof.ovh.net (188.165.12.106): icmp_seq=4 ttl=55 time=87.8 ms
    64 bytes from proof.ovh.net (188.165.12.106): icmp_seq=5 ttl=55 time=88.1 ms
    
    --- proof.ovh.net ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4094ms
    rtt min/avg/max/mdev = 87.857/88.369/88.997/0.542 ms
  • tuxtux Member
    edited April 2012
    tux@S205:~$ ping -c 5 4x.xxx.208.xxx
    PING 4x.xxx.208.xxx (4x.xxx.208.xxx) 56(84) bytes of data.
    64 bytes from 4x.xxx.208.xxx: icmp_req=1 ttl=55 time=13.5 ms
    64 bytes from 4x.xxx.208.xxx: icmp_req=2 ttl=55 time=14.2 ms
    64 bytes from 4x.xxx.208.xxx: icmp_req=3 ttl=55 time=14.0 ms
    64 bytes from 4x.xxx.208.xxx: icmp_req=4 ttl=55 time=13.8 ms
    64 bytes from 4x.xxx.208.xxx: icmp_req=5 ttl=55 time=14.3 ms
    
    --- 4x.xxx.208.xxx ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4006ms
    rtt min/avg/max/mdev = 13.528/14.013/14.389/0.344 ms
  • AbhishekAbhishek Member
    edited April 2012

    From work(Bay area) to Hostigation LAX

    abhishek@abhishek:~$ ping 69.85.xxx.xxx
    PING 69.85.xxx.xxx (69.85.xxx.xxx) 56(84) bytes of data.
    64 bytes from 69.85.xxx.xxx: icmp_req=1 ttl=52 time=11.1 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=2 ttl=52 time=11.0 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=3 ttl=52 time=22.0 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=4 ttl=52 time=11.2 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=5 ttl=52 time=11.1 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=6 ttl=52 time=11.0 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=7 ttl=52 time=11.4 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=8 ttl=52 time=11.0 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=9 ttl=52 time=11.0 ms
    64 bytes from 69.85.xxx.xxx: icmp_req=10 ttl=52 time=11.0 ms
    --- 69.85.xxx.xxx ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9011ms
    rtt min/avg/max/mdev = 11.061/12.238/22.065/3.279 ms
    
  • My ISP has weird peering, so my pings depend on the day of the week, weather, how itchy Sir Richard Brandson's foot is, and several other factors.

    On a quick ping test from my home connection on WiFi,
    TinyKVM -> 26ms (Weird routing from Manchester, to Amsterdam then back to London)
    XenVZ -> 28ms
    MiniVPS -> 28ms

    I presume if I switched to a different ISP, I could get pings of ~10ms to TinyKVM.

  • InfinityInfinity Member, Host Rep

    @ElliotJ said: My ISP has weird peering, so my pings depend on the day of the week, weather, how itchy Sir Richard Brandson's foot is, and several other factors.

    Couldn't have said it better, Virgin Media has terrible routing.

  • NickWNickW Member
    edited April 2012

    15ms from Manchester to Linode London. ISP is BT.

  • SrvisLLCSrvisLLC Member
    edited April 2012

    bytes=32 time=13ms TTL=55

    13ms from home to errantweb.

  • tommytommy Member

    lowest ping

    380 ms

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    30ms to FT from over here. I think it was lower when we had highwinds still.

    Seattle is close by though at ~10ms.

    Francisco

  • InfinityInfinity Member, Host Rep

    Oy @liam stealing my words. KMT

  • InfinityInfinity Member, Host Rep
    edited April 2012

    @liam That's Virgin Media's great routing for you..

  • My house to my VPS in Chicago.

    icmp_req=2 ttl=49 time=21.9 ms
    
Sign In or Register to comment.