Howdy, Stranger!

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

Sign In Register

Quick Links


Categories

In this Discussion

› › IPv6 VPS Seattle - Page 2
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.

IPv6 VPS Seattle

2

Comments

  • RobertClarkeRobertClarke Member, Host Rep

    @Nick_A Aw, I was hoping to get a Seattle VPS from Ramnode tonight :(

  • ihatetonyyihatetonyy Member
    edited April 2013

    @Nick_A said: I added test IPs and download files as a teaser

    ~50M/s from ChicagoVPS LA, ~26M/s from Catalyst Dallas, ~15M/s from NodeDeploy Atlanta.

    image

  • RobertClarkeRobertClarke Member, Host Rep

    30ms from about 10 miles away :/

    traceroute to 192.249.60.11 (192.249.60.11), 64 hops max, 52 byte packets
    (1-3)
    4 ae3---0.cor01.sttl.wa.frontiernet.net (74.40.1.153) 30.777 ms 31.185 ms 31.073 ms
    5 ae1---0.cor02.bvtn.or.frontiernet.net (74.40.1.222) 68.360 ms 30.877 ms 31.083 ms
    6 ae0---0.cor02.bvtn.or.frontiernet.net (74.40.1.186) 30.240 ms 30.468 ms 30.511 ms
    7 ae3---0.cor01.plal.ca.frontiernet.net (74.40.1.225) 30.455 ms 30.672 ms 30.118 ms
    8 ae0---0.cbr01.plal.ca.frontiernet.net (74.40.3.150) 29.894 ms 30.228 ms 29.710 ms
    9 paix.99.xe-0-1-0.cr1.pao1.us.nlayer.net (198.32.176.13) 30.250 ms 30.587 ms 30.209 ms
    10 ae1-70g.cr1.sfo1.us.nlayer.net (69.22.143.169) 31.776 ms 30.797 ms 31.129 ms
    11 xe-1-1-0.cr1.sea1.us.nlayer.net (69.22.142.34) 47.837 ms 47.510 ms 48.040 ms
    12 as3842.ae2-954.cr1.sea1.us.nlayer.net (63.141.219.78) 27.215 ms 27.744 ms 36.801 ms
    13 192.249.60.9 (192.249.60.9) 27.430 ms 26.548 ms 27.225 ms
    14 192.249.60.11 (192.249.60.11) 27.388 ms 28.447 ms 26.723 ms
    new-host-10:~ Robert$

    I guess my ISP just sucks :(

    Download from Tinet Dallas:

    wget http://test.sea.ramnode.com/1000MB.test
    --2013-04-22 06:04:42-- http://test.sea.ramnode.com/1000MB.test
    Resolving test.sea.ramnode.com... 192.249.60.11
    Connecting to test.sea.ramnode.com|192.249.60.11|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 1073741824 (1.0G) [text/plain]
    Saving to: “1000MB.test”

    100%[=============================================================================>] 1,073,741,824 47.5M/s in 26s

    2013-04-22 06:05:08 (39.2 MB/s) - “1000MB.test” saved [1073741824/1073741824]

    Trace from tinet Dallas:

    traceroute 192.249.60.11
    traceroute to 192.249.60.11 (192.249.60.11), 30 hops max, 60 byte packets
    1 10.0.0.253 (10.0.0.253) 15.830 ms 15.828 ms 15.855 ms
    2 ae2-118.dal33.ip4.tinet.net (77.67.69.249) 0.613 ms 0.626 ms 0.616 ms
    3 xe-3-3-0.sea21.ip4.tinet.net (89.149.180.53) 44.191 ms xe-0-2-0.sea21.ip4.tinet.net (89.149.182.185) 44.174 ms xe-3-3-0.sea21.ip4.tinet.net (89.149.180.53) 44.180 ms
    4 icastcenter-gw.ip4.tinet.net (173.241.128.122) 52.578 ms 52.070 ms 52.194 ms
    5 192.249.60.9 (192.249.60.9) 52.554 ms 52.540 ms 52.629 ms
    6 192.249.60.11 (192.249.60.11) 52.698 ms 52.233 ms 52.221 ms
    [root@dalssdmc3 ~]#

    Looks good, can't wait until I can buy an actual VM :)

  • nickvanwnickvanw Member

    @RobertClarke

    I'm in Seattle proper, less then 5 miles:

    $ traceroute 192.249.60.11
    traceroute to 192.249.60.11 (192.249.60.11), 64 hops max, 52 byte packets
    1 dd-wrt (192.168.1.1) 3.871 ms 1.239 ms 1.201 ms
    2 73.102.108.1 (73.102.108.1) 17.277 ms 14.970 ms 19.694 ms
    3 te-0-0-0-11-ur08.seattle.wa.seattle.comcast.net (68.85.144.181) 173.193 ms 186.611 ms 182.546 ms
    4 ae-20-0-ar03.seattle.wa.seattle.comcast.net (69.139.164.129) 13.694 ms 19.289 ms 15.350 ms
    5 he-1-6-0-0-10-cr01.seattle.wa.ibone.comcast.net (68.86.94.69) 203.042 ms
    he-1-7-0-0-11-cr01.seattle.wa.ibone.comcast.net (68.86.93.5) 244.456 ms
    te-1-3-0-4-cr01.sanjose.ca.ibone.comcast.net (68.86.93.173) 342.204 ms
    6 pos-1-11-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.87.173) 201.016 ms 221.976 ms 262.075 ms
    7 pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.78) 282.506 ms 198.209 ms 403.696 ms
    8 pos-0-9-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.88.110) 292.313 ms 244.947 ms 204.588 ms
    9 xe-9-3-0.sjc10.ip4.tinet.net (213.200.80.165) 35.330 ms 39.042 ms 68.888 ms
    10 xe-1-3-0.sea21.ip4.tinet.net (141.136.111.213) 57.341 ms
    xe-7-1-0.sea21.ip4.tinet.net (141.136.111.205) 59.095 ms 60.174 ms
    11 icastcenter-gw.ip4.tinet.net (173.241.128.122) 58.352 ms 63.222 ms 68.110 ms
    12 192.249.60.9 (192.249.60.9) 85.823 ms 55.966 ms 58.692 ms
    13 192.249.60.11 (192.249.60.11) 51.218 ms 60.683 ms 55.496 ms

    I've been assured this has something to do with nlayer and it will be fixed soon, don't worry :)

    That being said, from my desk at work:

    $ traceroute 192.249.60.11
    traceroute to 192.249.60.11 (192.249.60.11), 30 hops max, 60 byte packets
    1 ae3--1254.uwar-uwtc-1.infra.washington.edu (140.142.214.131) 18.914 ms 18.855 ms 18.794 ms
    2 irb--10.uwcr-ads-1.infra.washington.edu (10.132.1.65) 0.449 ms 0.413 ms 0.415 ms
    3 vl24.uwbr-ads-01.infra.washington.edu (10.132.1.66) 7.126 ms 7.089 ms 7.037 ms
    4 ae0--4000.iccr-sttlwa01-02.infra.pnw-gigapop.net (209.124.188.132) 1.112 ms 1.082 ms 1.064 ms
    5 137.164.131.58 (137.164.131.58) 1.206 ms 1.163 ms 1.165 ms
    6 xe-9-2-0.12.sttl0.tr-cps.internet2.edu (137.164.131.57) 1.083 ms 0.967 ms 0.936 ms
    7 * * *
    8 as3842.ae2-954.cr1.sea1.us.nlayer.net (63.141.219.78) 1.556 ms 1.492 ms 1.345 ms
    9 192.249.60.9 (192.249.60.9) 1.911 ms 1.826 ms 1.792 ms
    10 192.249.60.11 (192.249.60.11) 1.748 ms 1.484 ms 1.446 ms

  • Nick_ANick_A Member, Top Host, Host Rep

    Yeah, we haven't tweaked anything yet. That will happen over the next couple weeks once we start receiving feedback.

  • unusedunused Member

    Nice!

    wget http://test.sea.ramnode.com/1000MB.test
    --2013-04-22 02:45:56-- http://test.sea.ramnode.com/1000MB.test
    Resolving test.sea.ramnode.com... 192.249.60.11
    Connecting to test.sea.ramnode.com|192.249.60.11|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 1073741824 (1.0G) [text/plain]
    Saving to: `1000MB.test'

    100%[================================================================================================================================================================>] 1,073,741,824 110M/s in 13s

    2013-04-22 02:46:09 (78.2 MB/s) - `1000MB.test' saved [1073741824/1073741824]

  • DStroutDStrout Member

    @unused from where?

  • unusedunused Member

    @DStrout my seattle vr.org

    traceroute to test.sea.ramnode.com (192.249.60.11), 30 hops max, 40 byte packets
    1 192.73.240.1 (192.73.240.1) 0.265 ms 0.236 ms 0.196 ms
    2 63.251.175.173 (63.251.175.173) 0.589 ms 0.661 ms 0.754 ms
    3 core2.bbnet2.sea.pnap.net (63.251.160.73) 1.645 ms 1.697 ms 1.712 ms
    4 ae0-123.sea21.ip4.tinet.net (216.221.159.197) 1.669 ms 1.257 ms 1.638 ms
    5 icastcenter-gw.ip4.tinet.net (173.241.128.122) 9.764 ms 9.840 ms 9.911 ms
    6 192.249.60.9 (192.249.60.9) 0.927 ms 1.305 ms 0.900 ms
    7 192.249.60.11 (192.249.60.11) 1.007 ms 1.008 ms 0.997 ms

  • DStroutDStrout Member

    https://clientarea.ramnode.com/cart.php?a=add&pid=64
    So... close...

  • BlackoutIsHereBlackoutIsHere Member

    @DStrout said: https://clientarea.ramnode.com/cart.php?a=add&pid=64

    So... close...

    Well on the RamNode IRC we had the test ips right as the router/server went up thanks to some people stalking BGP announcements :P

  • Nick_ANick_A Member, Top Host, Host Rep

    Ok, once we get one more thing done this afternoon, we should be good to go!

  • RobertClarkeRobertClarke Member, Host Rep

    @Nick_A I hope you're enjoying the sun today, it's set to be a nice week out :)

  • Nick_ANick_A Member, Top Host, Host Rep

    I'm in Georgia and I am enjoying the sun here.

  • budingyunbudingyun Member

    Ah the option is already available in whmcs. :D

  • AlexBarakovAlexBarakov Patron Provider, Veteran

    traceroute to test.sea.ramnode.com (192.249.60.11), 30 hops max, 60 byte packets
    1 10.6.0.25 (10.6.0.25) 0.622 ms 0.873 ms 1.147 ms
    2 69.46.34.17 (69.46.34.17) 0.532 ms 0.553 ms 0.803 ms
    3 64.122.5.49 (64.122.5.49) 2.428 ms 2.795 ms 2.799 ms
    4 tg9-2.cr01.sttlwatw.integra.net (209.63.114.125) 9.509 ms 9.514 ms 9.509 ms
    5 209.63.101.2 (209.63.101.2) 3.436 ms 3.435 ms 3.428 ms
    6 ae0-128.sea21.ip4.tinet.net (173.241.129.197) 51.414 ms 51.362 ms 51.351 ms
    7 icastcenter-gw.ip4.tinet.net (173.241.128.122) 2.484 ms 2.510 ms 2.491 ms
    8 192.249.60.9 (192.249.60.9) 2.798 ms 2.766 ms 2.750 ms
    9 192.249.60.11 (192.249.60.11) 2.979 ms 2.965 ms 2.948 ms

    That's from our nodes from Seattle. @Nick_A , which DC is this?

  • DStroutDStrout Member
    edited April 2013

    @Nick_A Back in Atlanta? How long were you in Seattle?

  • BlackoutIsHereBlackoutIsHere Member

    @DStrout said: Back in Atlanta? How long were you in Seattle?

    I think it was only 2 days

  • RobertClarkeRobertClarke Member, Host Rep

    @Nick_A Aww, Seattle weather wasn't on your side while you were here :(

  • kalamkalam Member

    Really bad ping from Tacoma.

    | WinMTR statistics |

    Host - % Sent Recv Best Avrg Wrst Last
    192.168.1.1 - 0 22 22 0 1 2 1
    96.120.100.1 - 0 22 22 7 10 12 10
    te-0-0-0-15-ur06.tacoma.wa.seattle.comcast.net - 0 22 22 8 11 14 8
    ae-28-0-ar03.seattle.wa.seattle.comcast.net - 0 22 22 10 18 99 10
    he-1-6-0-0-11-cr01.seattle.wa.ibone.comcast.net - 0 22 22 13 20 26 16
    pos-2-8-0-0-cr01.sacramento.ca.ibone.comcast.net - 0 22 22 27 29 33 27
    pos-0-2-0-0-cr01.sanjose.ca.ibone.comcast.net - 0 22 22 29 31 35 32
    pos-0-5-0-0-pe01.11greatoaks.ca.ibone.comcast.net - 0 22 22 31 35 39 34
    xe-9-3-0.sjc10.ip4.tinet.net - 0 22 22 36 41 88 39
    xe-7-1-0.sea21.ip4.tinet.net - 0 22 22 58 64 111 61
    icastcenter-gw.ip4.tinet.net - 0 22 22 61 62 65 62
    192.249.60.9 - 0 22 22 57 61 64 59
    192.249.60.11 - 0 22 22 59 61 64 59
    ________________________________________________ ______ ______ ______ ______ ______ ______
  • LAKidLAKid Member

    some reason, I think Liquid solution has better connection.

  • ihatetonyyihatetonyy Member

    @LAKid said: some reason, I think Liquid solution has better connection.

    They've had time to optimize stuff. Give @Nick_A some time and I'm sure he'll be on par.

  • BlackoutIsHereBlackoutIsHere Member

    @ihatetonyy said: They've had time to optimize stuff. Give @Nick_A some time and I'm sure he'll be on par.

    Yeah he literally just got those lines up

  • DStroutDStrout Member

    Choose the 256MB SVZ here:
    https://clientarea.ramnode.com/cart.php?gid=13
    Interesting amount of stock available:
    image

  • BlackoutIsHereBlackoutIsHere Member

    @DStrout said: Interesting amount of stock available:

    SHHH, silence your hax

  • Nick_ANick_A Member, Top Host, Host Rep

    Sorry, giving out individual orders in IRC :)

    Public orders in a bit

  • ihatetonyyihatetonyy Member

    @Nick_A said: Sorry, giving out individual orders in IRC :)

    Damn! Throw me in the list if you feel so inclined..

  • BlackoutIsHereBlackoutIsHere Member

    @ihatetonyy said: Damn! Throw me in the list if you feel so inclined..

    You should probably just wait :P

  • ihatetonyyihatetonyy Member

    @BlackoutIsHere said: You should probably just wait :P

    Me? Wait?!

    No, that's not an option.

  • ihatetonyyihatetonyy Member
    edited April 2013

    beautiful

    Got a 512MB CVZ-E5.

    [root@behaviour ~]# wget http://cachefly.cachefly.net/100mb.test
--2013-04-22 16:46:32--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `100mb.test'

100%[========================================================================>] 104,857,600 48.0M/s   in 2.1s

2013-04-22 16:46:34 (48.0 MB/s) - `100mb.test' saved [104857600/104857600]

    root@behaviour ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 1.12689 s, 953 MB/s

    It's.. just so beautiful. I have no words.

  • DStroutDStrout Member
    edited April 2013

    Full stock is IN! I got mine on IRC, but they're publicly available now! Way to go @Nick_A, and the whole RamNode team! (Yeah, I know Nick does almost all the work, but he does have some help.)

Sign In or Register to comment.