Howdy, Stranger!

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


BuyVM Stock - Buffalo?? - Page 6
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.

BuyVM Stock - Buffalo??

13468919

Comments

  • PacketVMPacketVM Member, Host Rep
    edited August 2012

    Pinging 199.195.255.1 with 32 bytes of data:

    Reply from 199.195.255.1: bytes=32 time=115ms TTL=49
    Reply from 199.195.255.1: bytes=32 time=118ms TTL=49
    Reply from 199.195.255.1: bytes=32 time=120ms TTL=49
    Reply from 199.195.255.1: bytes=32 time=116ms TTL=49
    Ping statistics for 199.195.255.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 115ms, Maximum = 120ms, Average = 117ms

  • AmfyAmfy Member

    ping 199.195.255.1

    PING 199.195.255.1 (199.195.255.1) 56(84) bytes of data.
    64 bytes from 199.195.255.1: icmp_seq=1 ttl=54 time=89.8 ms
    64 bytes from 199.195.255.1: icmp_seq=2 ttl=54 time=89.8 ms

    ping 199.195.255.1

    PING 199.195.255.1 (199.195.255.1) 56(84) bytes of data.
    64 bytes from 199.195.255.1: icmp_req=1 ttl=52 time=87.6 ms
    64 bytes from 199.195.255.1: icmp_req=2 ttl=52 time=87.8 ms

    Both from Germany, nice! :)

  • gsrdgrdghdgsrdgrdghd Member
    edited August 2012

    @Amfy said: Both from Germany, nice! :)

    Those look like from a server, correct?

  • AmfyAmfy Member
    edited August 2012

    @gsrdgrdghd said: Those look like from a server, correct?

    Yep :P (actually only have access to internet over wifi, that's to unstable for ping)

    64 bytes from 199.195.255.1: icmp_seq=1 ttl=50 time=104.749 ms
    64 bytes from 199.195.255.1: icmp_seq=2 ttl=50 time=106.618 ms
    64 bytes from 199.195.255.1: icmp_seq=3 ttl=50 time=107.750 ms
    64 bytes from 199.195.255.1: icmp_seq=4 ttl=50 time=105.058 ms
    64 bytes from 199.195.255.1: icmp_seq=5 ttl=50 time=106.693 ms

    from my laptop, but I think some ms are from the wifi

  • Austria :)

    manage@1ge-bond2-citycom-willshome :: ~# ping 199.195.255.1
    PING 199.195.255.1 (199.195.255.1) 56(84) bytes of data.
    64 bytes from 199.195.255.1: icmp_req=1 ttl=51 time=104 ms
    64 bytes from 199.195.255.1: icmp_req=2 ttl=51 time=105 ms
    64 bytes from 199.195.255.1: icmp_req=3 ttl=51 time=104 ms
    64 bytes from 199.195.255.1: icmp_req=4 ttl=51 time=104 ms
    64 bytes from 199.195.255.1: icmp_req=5 ttl=51 time=104 ms
    64 bytes from 199.195.255.1: icmp_req=6 ttl=51 time=105 ms
    64 bytes from 199.195.255.1: icmp_req=7 ttl=51 time=104 ms
    ^C
    --- 199.195.255.1 ping statistics ---
    7 packets transmitted, 7 received, 0% packet loss, time 6002ms
    rtt min/avg/max/mdev = 104.954/104.980/105.015/0.347 ms

    Thanked by 1djvdorp
  • Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Users\Chris>ping 199.195.255.1
    
    Pinging 199.195.255.1 with 32 bytes of data:
    Reply from 199.195.255.1: bytes=32 time=132ms TTL=50
    Reply from 199.195.255.1: bytes=32 time=131ms TTL=50
    Reply from 199.195.255.1: bytes=32 time=129ms TTL=50
    Reply from 199.195.255.1: bytes=32 time=130ms TTL=50
    
    Ping statistics for 199.195.255.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 129ms, Maximum = 132ms, Average = 130ms
    
    
  • When I cancel SJ to get NY; do I have to do this via ticket? Because I think when I cancel SJ and then go to your page to buy NY I have to go through paypal again and they will charge me 15$ again.
    So when NY becomes available I should open a ticket in which I request the cancellation of SJ and the order for a NY server, yes? greetings

  • @bamnael said: So when NY becomes available I should open a ticket in which I request the cancellation of SJ and the order for a NY server, yes? greetings

    Pro-rated refund (via credit) will be issued automatically IIRC.

  • Another one from Germany:

    ping -c 20 199.195.255.1
    PING 199.195.255.1 (199.195.255.1): 56 data bytes
    64 bytes from 199.195.255.1: icmp_seq=0 ttl=54 time=141.841 ms
    64 bytes from 199.195.255.1: icmp_seq=1 ttl=54 time=138.723 ms
    64 bytes from 199.195.255.1: icmp_seq=2 ttl=54 time=138.569 ms
    64 bytes from 199.195.255.1: icmp_seq=3 ttl=54 time=138.821 ms
    64 bytes from 199.195.255.1: icmp_seq=4 ttl=54 time=138.473 ms
    64 bytes from 199.195.255.1: icmp_seq=5 ttl=54 time=140.043 ms
    64 bytes from 199.195.255.1: icmp_seq=6 ttl=54 time=139.354 ms
    64 bytes from 199.195.255.1: icmp_seq=7 ttl=54 time=138.933 ms
    64 bytes from 199.195.255.1: icmp_seq=8 ttl=54 time=138.545 ms
    64 bytes from 199.195.255.1: icmp_seq=9 ttl=54 time=138.903 ms
    64 bytes from 199.195.255.1: icmp_seq=10 ttl=54 time=139.036 ms
    64 bytes from 199.195.255.1: icmp_seq=11 ttl=54 time=138.737 ms
    64 bytes from 199.195.255.1: icmp_seq=12 ttl=54 time=138.691 ms
    64 bytes from 199.195.255.1: icmp_seq=13 ttl=54 time=138.426 ms
    64 bytes from 199.195.255.1: icmp_seq=14 ttl=54 time=137.762 ms
    64 bytes from 199.195.255.1: icmp_seq=15 ttl=54 time=138.757 ms
    64 bytes from 199.195.255.1: icmp_seq=16 ttl=54 time=138.816 ms
    64 bytes from 199.195.255.1: icmp_seq=17 ttl=54 time=139.063 ms
    64 bytes from 199.195.255.1: icmp_seq=18 ttl=54 time=139.582 ms
    64 bytes from 199.195.255.1: icmp_seq=19 ttl=54 time=138.969 ms
    
    --- 199.195.255.1 ping statistics ---
    20 packets transmitted, 20 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 137.762/139.002/141.841/0.792 ms
    
  • corpuscorpus Member
    edited August 2012

    from greece

    PING 199.195.255.1 (199.195.255.1) 56(84) bytes of data.
    64 bytes from 199.195.255.1: icmp_req=1 ttl=48 time=164 ms
    64 bytes from 199.195.255.1: icmp_req=2 ttl=48 time=163 ms
    64 bytes from 199.195.255.1: icmp_req=4 ttl=48 time=164 ms
    64 bytes from 199.195.255.1: icmp_req=5 ttl=48 time=163 ms
    64 bytes from 199.195.255.1: icmp_req=6 ttl=48 time=163 ms
    64 bytes from 199.195.255.1: icmp_req=7 ttl=48 time=163 ms
    ^C
    --- 199.195.255.1 ping statistics ---
    7 packets transmitted, 6 received, 14% packet loss, time 6006ms
    rtt min/avg/max/mdev = 163.526/163.774/164.097/0.459 ms

  • from Holland:

    daniel@Daniels-MacBook-Pro ~ $ ping 199.195.255.1
    PING 199.195.255.1 (199.195.255.1): 56 data bytes
    64 bytes from 199.195.255.1: icmp_seq=0 ttl=51 time=131.703 ms
    64 bytes from 199.195.255.1: icmp_seq=1 ttl=51 time=106.570 ms
    64 bytes from 199.195.255.1: icmp_seq=2 ttl=51 time=90.985 ms
    64 bytes from 199.195.255.1: icmp_seq=3 ttl=51 time=88.661 ms
    64 bytes from 199.195.255.1: icmp_seq=4 ttl=51 time=91.009 ms
    64 bytes from 199.195.255.1: icmp_seq=5 ttl=51 time=88.705 ms
    64 bytes from 199.195.255.1: icmp_seq=6 ttl=51 time=93.790 ms
    64 bytes from 199.195.255.1: icmp_seq=7 ttl=51 time=189.706 ms
    64 bytes from 199.195.255.1: icmp_seq=8 ttl=51 time=91.869 ms
    64 bytes from 199.195.255.1: icmp_seq=9 ttl=51 time=91.360 ms
    ^C
    --- 199.195.255.1 ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 88.661/106.436/189.706/30.461 ms

  • Anyone know when will buyvm have stock?
    Need their storage plan and still waiting...

  • prometeusprometeus Member, Host Rep

    soon :)

    Thanked by 1djvdorp
  • it's on the way

  • It's not too soon though. (-_-)

  • @x123123412345 said: Anyone know when will buyvm have stock?

    Need their storage plan and still waiting...

    Aldryic's Decision™.

  • Hi,
    I got average 164ms from Germany.

    `C:\Users\Mandikor>ping 199.195.255.1

    Ping wird ausgeführt für 199.195.255.1 mit 32 Bytes Daten:
    Antwort von 199.195.255.1: Bytes=32 Zeit=163ms TTL=45
    Antwort von 199.195.255.1: Bytes=32 Zeit=165ms TTL=45
    Antwort von 199.195.255.1: Bytes=32 Zeit=165ms TTL=45
    Antwort von 199.195.255.1: Bytes=32 Zeit=164ms TTL=45

    Ping-Statistik für 199.195.255.1:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
    Ca. Zeitangaben in Millisek.:
    Minimum = 163ms, Maximum = 165ms, Mittelwert = 164ms`

  • @bubie That's a very bad ping for Germany to Buffalo USA, i've got 123 ms from Varna, Bulgaria to Bufflao USA and i am a lot further from USA than you are.

  • @rds100 said: @bubie That's a very bad ping for Germany to Buffalo USA, i've got 123 ms from Varna, Bulgaria to Bufflao USA and i am a lot further from USA than you are.

    It's his ISP's connection which has 70ms latency until it actually reaches the first hop on a fibre network.

  • AlexBarakovAlexBarakov Patron Provider, Veteran

    I am on 129ms average from Bulgaria as well.

  • @gsrdgrdghd yeah, seems his ISP sux. Unless he is on a 3G/GPRS modem, then it would be normal.

    Thanked by 1JoeMerit
  • @rds100 said: @gsrdgrdghd yeah, seems his ISP sux.

    Nah, most DSL connections with a speed < 6 mbit/s have a latency of 50ms+. There's not really much the ISPs can do about it.

  • @gsrdgrdghd man, that's some serious interleaving :) ADSL connections here don't suck as much i think.

  • bubiebubie Member
    edited August 2012

    I have DSL, that's correct. It is a "up to" 16Mbit/s download and 1Mbit/s upload contract.
    But real speed is 11Mbit/s down and 0,8Mbit/s up.

    I got you a traceroute.
    Are those 37ms on the 1st hop the initail delay of 70ms that you speak of? gsrdgrdghd

    Routenverfolgung zu 199.195.255.1 über maximal 30 Abschnitte

    >

    1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
    2 37 ms 36 ms 37 ms rdsl-krlh-de02.nw.mediaways.net [213.20.56.137]
    3 37 ms 68 ms 37 ms xmws-krlh-de01-chan-17.nw.mediaways.net [213.20.220.210]
    4 37 ms 36 ms 37 ms rmws-krlh-de01-gigaet-0-0-0.nw.mediaways.net [62.53.222.46]
    5 52 ms 51 ms 52 ms rmwc-stgt-de01-pos-0-0.nw.mediaways.net [213.20.222.157]
    6 52 ms 52 ms 52 ms rmwc-brln-de02-xe-0-0-2-0.nw.mediaways.net [195.71.254.9]
    7 52 ms 51 ms 115 ms rmwc-brln-de01-xe-0-1-0-0.nw.mediaways.net [62.53.167.229]
    8 82 ms 71 ms 72 ms 84.16.10.1
    9 * * * Zeitüberschreitung der Anforderung.
    .
    .
    .
    28 * * * Zeitüberschreitung der Anforderung.
    29 * * * Zeitüberschreitung der Anforderung.
    30 * * * Zeitüberschreitung der Anforderung.

    >

    Ablaufverfolgung beendet.

    >

    C:\Users\Mandikor

  • I didn't really follow Twitter/IRC, is the stock in Buffalo coming today or some time later?

  • Later, sometime this week.

  • @bubie said: Are those 37ms on the 1st hop the initail delay of 70ms that you speak of?

    Yes.

  • bubiebubie Member
    edited August 2012

    Hey, does the routing over the big pond go to Washington DC.?
    Is this the only underwater cable that leads to the east cost?
    Or is there a direct connection to Buffalo possible?
    I thought you guys may know that.

    Here is my pathping:

    `Routenverfolgung zu 199.195.255.1 über maximal 30 Abschnitte

    0 local pc
    1 local router
    2 rdsl-krlh-de02.nw.mediaways.net [213.20.56.137]
    3 xmws-krlh-de01-chan-17.nw.mediaways.net [213.20.220.210]
    4 rmws-krlh-de01-gigaet-0-0-0.nw.mediaways.net [62.53.222.46]
    5 rmwc-stgt-de01-pos-0-0.nw.mediaways.net [213.20.222.157]
    6 rmwc-brln-de02-xe-0-0-2-0.nw.mediaways.net [195.71.254.9]
    7 rmwc-brln-de01-chan-1-0.nw.mediaways.net [62.53.164.33]
    8 So3-3-0-0-grtparix1.red.telefonica-wholesale.net [84.16.10.213]
    9 Xe1-0-1-0-grtwaseq3.red.telefonica-wholesale.net [94.142.119.149]
    10 xe0-2-0-0-grtwaseq4.red.telefonica-wholesale.net [213.140.36.33]
    11 xe-11-2-0.edge3.Washington4.Level3.net [4.53.112.17]
    12 vlan80.csw3.Washington1.Level3.net [4.69.149.190]
    13 ae-82-82.ebr2.Washington1.Level3.net [4.69.134.153]
    14 ae-3-3.ebr1.NewYork2.Level3.net [4.69.132.90]
    15 ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]
    16 ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
    17 ae-4-4.car2.Buffalo1.Level3.net [4.69.140.241]
    18 ae-11-11.car1.Buffalo1.Level3.net [4.69.140.237]
    19 CWIE-LLC.car1.Buffalo1.Level3.net [4.28.232.90]
    20 199.195.255.1

    Berechnung der Statistiken dauert ca. 500 Sekunden...`

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @bubie said: Later, sometime this week.

    @gsrdgrdghd said: I didn't really follow Twitter/IRC, is the stock in Buffalo coming today or some time later?

    CC recommended we don't open inventory until they're done with Telia, so i'll heed their advice. That's supposed to happen in the middle of the week.

    I'm waiting on the physical KVM to arrive so I can get buyvm+ online over there. It's the last part we need before launch :)

    Thanks for the interest everyone,

    Francisco

    Thanked by 1djvdorp
  • @Francisco said: Telia's US network is alright, nothing to write home about.

    Their EU network is one of the best though :)

    I prefer Tinet, personally. Better US network and comparable EU network.

Sign In or Register to comment.