Rackspace Delivers IPv6

At Rackspace, we’ve been busy for the last 6 months getting ready for IPv6. We’ve spoken to our customers and our partners about industry impact and what it means to be IPv6-ready. We’ve collaborated across network, product, IT, security, monitoring, supply chain, sales and support teams to make sure we’ve covered all aspects of the customer experience. 160 days after we started, we are pleased to announce that we are ready to accept customers’ IPv6 requests for the following products:

Private Cloud
Critical Sites
Dedicated server configurations (Servers, Firewalls, Load Balancers, etc)
Cloud Sites
Email & Apps
Cloud Files
Cloud Load Balancers

We’re taking some additional time to get Cloud Servers ready for IPv6 and ready for customers who need dual stack solutions to serve their customers.

What does it mean for Rackspace to be ready?

We wanted to eliminate any unnecessary trade-offs for our customers when it comes to IPv6 readiness. Starting with the network, we have enabled all of our data centers globally to handle IPv4 and IPv6 traffic. Customers don’t have to worry about being in the right data center and they don’t have to bother with tunneling.

We have also tested all of our products and services so that we can partner with our customers on the right dual-stack solutions to meet their needs and we will continue to always provide fanatical support as customers transition to dual stack solutions. These transitions may require OS upgrades, new firewalls, and new servers. So, Rackspace will help guide our customers through these decisions on their own timeframe.


For customers who may be anxious about accepting IPv6 traffic and who don’t feel that their application is compatible with IPv6 or with a new operating system needed for IPv6, Rackspace has rolled out network infrastructure to help. NAT64 allows for IPv6 traffic coming into our network to be translated to IPv4 for customers not quite ready to move to IPv6. With no additional fees or hardware required, our NAT64 solution will enable our customers to become IPv6-ready on their schedules and not be forced into an untimely migration or upgrade by Rackspace or any other circumstances.

Already Successful with World IPv6 Day

Of course it’s not enough to design and test our IPv6 solutions in a lab and then hope that our first production efforts go okay. Rackspace collaborated with and participated in World IPv6 Day on June 8th. We wanted to prove that we could get Rackspace web sites ready before asking customer to trust us with their web sites.

We’re happy to report that by June 8th, we were receiving IPv6 traffic for both Rackspace.com and Rackspace.co.uk, along with several of our customer portals, my.rackspace.com, cp.rackspace.com and apps.rackspace.com. Most importantly during June 8th, we didn’t experience any IPv6 service interruptions and no increased support ticket volume either – a great success!

Where do we go from here?

Though we’re proud of our readiness, we’re not stopping to celebrate our success of getting to the point where we can help customers with IPv6. We realize that the industry transition from IPv4 to dual stack and, eventually, IPv6-only will be a multi-year journey full of troubleshooting and tweaking, successful migrations and hard conversations. We’re not promising to be perfect out of the gate or that every feature of every product will be problem free, the industry just isn’t ready yet. What we will promise is that we will always have our customers’ needs top of mind and that we will do everything we can to help you make the right decisions for your business.

We look forward to helping you with your own IPv6 readiness and you can look forward to more updates as we keep improving and sharing what we learn along the way!

Rack Blogger is our catchall blog byline, subbed in when a Racker author moves on, or used when we publish a guest post. You can email Rack Blogger at blog@rackspace.com.


  1. It would be great to know the current status of IPv6 and your cloud servers. It is more than a year later, and as far as I can tell cloud servers still cannot use IPv6 (can’t find anything current telling me how to obtain an IPv6 address).

  2. I too would appreciate an update on this, and can confirm as per my ticket with Support earlier today that Cloud Servers are still not IPv6 ready (I was pointed to this blog post) and there is apparently no ETA.

  3. For anyone reading this looking for IPv6 : it has been delivered. I just created a “next generation” public cloud CentOS instance, and it was assigned an IPv6 address. I’m not sure if more advanced IPv6 usage is available (e.g. assign static addresses, route a subnet to a Cloud machine) but the basic IPv6 connectivity with an autoconfig address seems to be available now.

  4. I signed up for Rackspace email assuming there would be IPv6 support (as it says on this page). Then I discover that the servers don’t have AAAA records. I contact support and they say Email doesn’t support IPv6.

    What’s the deal?


Please enter your comment!
Please enter your name here