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

› › East Cost VPS with ipv6?
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.

East Cost VPS with ipv6?

dirkdirk Member
edited February 2012 in General

I'm looking for an East Coast VPS (128mb RAM) with native ipv6 support and at a max of $25/year.
Diskspace of 5gb is more then enough, bandwidth around 50gb is fine too.

Any ideas?

Comments

  • fanfan Veteran

    Hostigation?

  • miTgiBmiTgiB Member

    @fan said: Hostigation?

    No IPv6 at the new data center currently, so I'm going to bring up an HE tunnel to Miami and announce a /48 out from there. Caro is saying this year for IPv6 support, but I'm not holding my breath.

  • dmmcintyre3dmmcintyre3 Member

    @miTgiB said: so I'm going to bring up an HE tunnel to Miami

    Why Miami?

    [root@tiger ~]# ping 216.66.22.2 #(Ashburn, VA)
PING 216.66.22.2 (216.66.22.2) 56(84) bytes of data.
64 bytes from 216.66.22.2: icmp_seq=1 ttl=53 time=27.0 ms
64 bytes from 216.66.22.2: icmp_seq=2 ttl=53 time=26.3 ms
64 bytes from 216.66.22.2: icmp_seq=3 ttl=53 time=30.9 ms
64 bytes from 216.66.22.2: icmp_seq=4 ttl=53 time=26.3 ms
^C
--- 216.66.22.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3094ms
rtt min/avg/max/mdev = 26.349/27.699/30.973/1.916 ms

[root@tiger ~]# ping 209.51.161.58 #(Miami, FL)
PING 209.51.161.58 (209.51.161.58) 56(84) bytes of data.
64 bytes from 209.51.161.58: icmp_seq=1 ttl=53 time=40.9 ms
64 bytes from 209.51.161.58: icmp_seq=2 ttl=53 time=40.6 ms
^C
--- 209.51.161.58 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1884ms
rtt min/avg/max/mdev = 40.676/40.836/40.997/0.258 ms
  • yomeroyomero Member

    Funny hehe

  • miTgiBmiTgiB Member

    @dmmcintyre3 said: Why Miami?

    Cuz I'm used to crappy Cogent peering there, both look equally shitty

    [root@dns3 ~]# traceroute 216.66.22.2
traceroute to 216.66.22.2 (216.66.22.2), 30 hops max, 60 byte packets
 1  174.34.253.33 (174.34.253.33)  0.158 ms  0.293 ms  0.177 ms
 2  hostigation-gw.caro.net (174.34.252.177)  1.789 ms  1.659 ms  1.386 ms
 3  edge1-xb1-vl4.caro.net (69.59.18.11)  0.756 ms  0.741 ms  0.762 ms
 4  pos9-0.chrlncsa-rtr1.carolina.rr.com (24.93.64.102)  1.759 ms  1.745 ms  1.706 ms
 5  107.14.19.18 (107.14.19.18)  6.979 ms  7.456 ms ae-3-0.cr0.atl20.tbone.rr.com (66.109.6.82)  6.845 ms
 6  ae-0-0.pr0.atl20.tbone.rr.com (66.109.6.171)  6.090 ms 107.14.19.11 (107.14.19.11)  6.082 ms ae-0-0.pr0.atl20.tbone.rr.com (66.109.6.171)  14.226 ms
 7  TenGigabitEthernet9-2.ar1.ATL2.gblx.net (64.212.108.69)  31.412 ms  31.639 ms  31.403 ms
 8  HURRICANE-ELECTRIC-LLC-New-York.TenGigabitEthernet1-3.ar5.NYC1.gblx.net (64.209.92.98)  93.895 ms  88.209 ms  88.250 ms
 9  10gigabitethernet2-3.core1.ash1.he.net (72.52.92.86)  92.803 ms  83.474 ms  83.659 ms
10  tserv13.ash1.ipv6.he.net (216.66.22.2)  83.513 ms  82.963 ms  83.517 ms
[root@dns3 ~]# traceroute 209.51.161.58
traceroute to 209.51.161.58 (209.51.161.58), 30 hops max, 60 byte packets
 1  174.34.253.33 (174.34.253.33)  0.205 ms  0.104 ms  0.085 ms
 2  hostigation-gw.caro.net (174.34.252.177)  0.571 ms  0.556 ms  0.708 ms
 3  edge1-xb1-vl4.caro.net (69.59.18.11)  0.703 ms  0.798 ms  0.783 ms
 4  pos9-0.chrlncsa-rtr1.carolina.rr.com (24.93.64.102)  17.001 ms  16.968 ms  16.948 ms
 5  ae-3-0.cr0.atl20.tbone.rr.com (66.109.6.82)  16.945 ms  16.927 ms  16.909 ms
 6  ae-0-0.pr0.atl20.tbone.rr.com (66.109.6.171)  16.883 ms 107.14.19.11 (107.14.19.11)  16.118 ms ae-0-0.pr0.atl20.tbone.rr.com (66.109.6.171)  16.102 ms
 7  TenGigabitEthernet9-2.ar1.ATL2.gblx.net (64.212.108.69)  31.458 ms  31.448 ms  31.445 ms
 8  HURRICANE-ELECTRIC-LLC-New-York.TenGigabitEthernet1-3.ar5.NYC1.gblx.net (64.209.92.98)  84.236 ms  84.209 ms  84.209 ms
 9  10gigabitethernet2-3.core1.ash1.he.net (72.52.92.86)  84.191 ms  85.089 ms  85.074 ms
10  10gigabitethernet1-2.core1.atl1.he.net (184.105.213.110)  83.897 ms  83.343 ms  83.717 ms
11  10gigabitethernet3-2.core1.mia1.he.net (72.52.92.54)  97.220 ms  97.949 ms  97.922 ms
12  tserv12.mia1.ipv6.he.net (209.51.161.58)  97.148 ms  97.485 ms  97.416 ms
  • flam316flam316 Member

    It looks like it's less hops to Ashburn than to Miami. In fact, it's routing you through Ashburn to get to Miami. But if I were you, I would go with NY because it looks like everything is being routed through NY.

  • miTgiBmiTgiB Member

    @flam316 said: But if I were you, I would go with NY

    I just have to see where HE has BGP peers available, tunnels are easy to get at any of their locations, but to peer is another story.

  • flam316flam316 Member

    Judging by their network map, NY is a major PoP for HE. I would be surprised if they didn't peer there. But of course, you would need to contact them to get this info.

  • miTgiBmiTgiB Member

    Curiosity got the better of me, and Ashburn VA, Miami FL, and Freemont CA are the only locations HE offers BGP tunnels

  • flam316flam316 Member

    Interesting. Hopefully Caro.net gets some real IPv6 in the DC soon, but until then, that doesn't seem like a horrible option. However, I think Ashburn would make more sense than Miami because of it's central-ish location.

Sign In or Register to comment.