Add support for IPv6 on http://*.hs-sites.com/
I'm a network engineer whose company has decided to start a technology blog. One of the technologies I work a lot with and would like to blog about, is the next-generation Internet Protocol, IPv6. However, our http://*.hs-sites.com page does not support IPv6, only the legacy version IPv4. Indeed, this is the case for all of http://*.hs-sites.com/.
Now, blogging about the next-generation protocol IPv6 on a site which does not support it would obviously be rather embarrassing. Therefore I would like to see http://*.hs-sites.com support IPv6 before I get started with the blogging, so it would be nice if you could implement that.
This might actually be a very easy thing for you to implement, as I see that you are using Akamai for content distribution. Akamai happens to support IPv6, so in all likelihood all you would have to do is simply to ask Akamai to enable it for you. You can find more information about Akamai and IPv6 on their homepage: http://www.akamai.com/ipv6
Thank you for the feedback, we are planning to implement this. Making this change entails significant work on the Product level and we want to ensure continued development and success for all of our customers on all technologies.
Urko Wood commented
We also need to be able to add IPv6 addresses to the analytics filter. Even when I'm working from home on a residential internet connection from AT&T U-Verse, the IP address is IPv6, so I can't filter it.
Paul Vinciguerra commented
We've been asking Hubspot for this for a year now. It really sucks when you bring someone to your IPv6 enabled website and your hubspot content is missing. Its like one of those IPv6 Easter eggs, but in reverse.
I saw your native IPv6 datacenter work on ipspace. Great job!
Ross Chandler commented
Also talk to whoever in your company that decides on hosting provider about moving to a provider that supports IPv6.
Lee Howard commented
I see that blogger.com and blogspot.com both run IPv6.
I see that hubspot.uservoice.com does not.
Elvis Daniel Velea commented
these days, IPv6 support should be offered by default by a site/blog hoster.
Sander Steffann commented
Ouch, embarrassing! I was talking to Jan the other day about updating RIPE-554 and including requiring IPv6 support for services. I guess this is a good example on why something like that is necessary.
Carlos Friacas commented
You should really consider adding IPv6 reachability to your content. IPv6 is essential for continued Internet growth.
Phillip Remaker commented
It also seems that you are serviced from the AT&T network - most AT&T commercial connections offer IPv6 connectivity on request. This should be a no brainer for you guys.
Jason Fesler commented
Akamai I'm told charges the same for IPv4 and IPv6. This should be trivial.
Tore Anderson commented
Hans Petter, we do have such a policy, but sometimes the marketing folks simply go «Oooh! Shiny!» .. :-)
Seriously though, the lack of IPv6 has spurred a discussion as to the possibility of finding an alternative blog platform.
Hans Petter Holen commented
You should also ask your company to implement a policy to only take services from Ipv6 capable providers...
Alain Fiocco commented
Rather embarrassing indeed. I went through a similar request at Cisco to make sure blogs.cisco.com was IPv6 reachable. We successed to get Wordpress / Rackspace to turn it on :-)