Doesn't seem quite that "hands down", but it does seem that it is fairly advantageous. What about number of peers? Doesn't the DC's BW blend tend to be richer than what you can drum up on your own?
Excellent! As ever, I see you are on top of things. FWIW, I did just do another test, and the speeds have not budged in either direction, in case anyone was wondering if this was a temporary issue.
Any chance of enabling users to delete their own posts? It seems like this should be possible, and it's somewhat annoying to me seeing "delete" posts since it can't be done any other way right now.
Any chance you can post a traceroute/ping output from one of your VMs to 184.105.253.10? (HE.net Dallas IPv6 tunnel server IP) I want to get an idea of how the routing is from CC to HE. If it looks good, you can count on another customer.
How is cPanel's IPv6 support? I know you guys don't support it, but when you do, I'm wondering if it can/will be implemented in your cPanel plans. Great plans, though.
A few notes in regard to configuring IPv6 in Apache:
In allowing/blocking IPv6 addresses, you just use the addresses:
Allow from 2001:db8:52::320c:ade5
Deny from 2001:db8::dead:beef
But when configuring listening addresses and ports, or in vhost configuration, you need to surround the...
On the contrary, as I said I do like the plans, and what I'm pointing out is nothing against you. It's just that it will be quite some time more before we see IPv6 on those plans. I don't know what the figure is for DC IPv6 penetration, but I'd be willing to bet it's higher than 10%. The saddest...
May I refer you to http://www.chicagovps.net/openvz.html - see about 1/4 of the way down there? No, a bit above, yeah, no, wait, there it is:
That's been there, ahem, a while.
As a die-hard DIYer, I tend to just ask for a test IP and get location/DC from that. Uptime tracking is good, but reviews will often tell you how that is. Doing your own ping and traceroute will give you a better idea than from other locations.
Ramnode Atlanta is four places since Nick has a /32. If you get a routed /48 on a HE.net tunnel, the network address section is three places, so you can allocate yourself a host identifier with one section and get four sections.
As for ip6tables, that's more than I care to write.
Version 2.0: Check last login IP and if it matches new one, simply update the timestamp of last login rather than recording a new one. After all, different IPs are where it gets interesting.
As I understand it, the biggest advantages of owning one's own IPs is portability. Move to a new DC and you can take your IPs along with you. However it seems to me there are a lot of disadvantages that would make it less than worth it for providers that aren't of a rather large size. Perhaps...
Just did some testing, and I'm glad once again that I went with this setup. Very direct routing. Four hops over IPv4 to the HE tunnel server, ping >1ms. Routes are highly efficient due to HE's great peering. Ping over IPv4 compares favorably in all instances to ping over IPv6 to native dual...