Rackspace Launches CDN Partnership With Industry Leader Akamai

Today, Rackspace announces our launch of Rackspace CDN (Content Delivery Network).

We’ve brought two best-in-breed technology and service companies together to offer customers a powerfully simple solution. As the #1 Managed Cloud Company, our customers tell us they want a full portfolio experience from Rackspace. They want to experience Fanatical Support with everything from cloud servers to cloud DNS, all in the same place, and all from the same support team. And they want industry leading technologies at the center of their user experience. Today’s launch of Rackspace CDN is a shining example of that – bringing Fanatical Support and managed cloud to Akamai’s industry leading content delivery network.

We know that slow websites lead to a quantifiable loss in engagement, customers and revenue. According to Akamai, an e-commerce site with a daily revenue of $100,000 will forfeit up to 2.5 million dollars in lost sales as a result of even a 1 second page load delay. In fact, 40 percent of visitors will abandon a site all together if it takes more than 3 seconds to load.

Rackspace CDN brings Akamai’s industry leading edge network to all Rackspace customers. We believe CDN is such a critical part of our customers’ application and web experience that we are removing all roadblocks to consuming it. In partnership with Akamai’s engineers, we’ve taken an onboarding processes that used to take weeks and turned it into a three-click experience in our Rackspace Control Panel. We’ve combined Akamai’s expertise running CDNs with our expertise in Fanatical Support to build a set of common configurations and reference architectures for all customers. This allows customers to cut through the jargon and configuration options and get up and running quickly. And, because Rackspace CDN is built on our managed cloud platform, we provide utility billing through an existing Rackspace account. Quite simply, we’ve made the world’s leading CDN accessible.

Rackspace CDN can be used with any server at Rackspace, whether it’s hosted on our public, private, or dedicated cloud environments. We know that our customers expect us to solve their needs on a variety of platforms and hardware, and Rackspace CDN’s flexibility is one of many steps in that direction.

This is what being the #1 Managed Cloud is about, providing Fanatical Support with industry leading, on-demand technologies for all of our customers. Our partnership with Akamai is an example of our commitment to integrate powerful third party technologies directly into our platform. We’re proud to be fulfilling our commitment with today’s launch of Rackspace CDN.

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.


    • Hello, Scott,

      Users of Rackspace CDN specify the origins that host the content, and the CDN pulls the content from these origins. Origins may refer to Dedicated Servers, Cloud Servers, Cloud Load Balancers, or even servers hosted outside of Rackspace.

      Users of Cloud Files CDN-enable a container, thereby distributing the contents of that container to the CDN’s edge nodes.

      In Rackspace CDN, it is not yet possible to specify a Cloud Files container as an origin.

      Hope this helps,
      Catherine (Rackspace Information Developer)

      • Thanks for the clarification Catherine.

        What you said in your last sentence doesn’t seem to make sense to me, because you’d theoretically have two sets of the same data in the CDN. The whole objective is to get your content out on the edge nodes and both services seem to do just that and why I didn’t understand the difference.

        If you can connect to content outside of the RS system, that could be a clear reason to use it as a standalone service. I would have to see how the pulling of content from RS’s network internally would work, to understand where that could be interesting and advantageous.

        One of the things we are looking for is a per-tenant calculation of traffic from the CDN’s to be able to charge them for that service. Do you know if that can be done with either the new CDN or the cloud file offering?


        • Good morning, Scott!
          Good observations! I’ll forward your comments and question here along to the cdn team for a response. But please feel free to email the cdn team at cdn@rackspace.com. Hope this helps.

  1. Why should we use Rackspace CDN vs Cloud Flare?

    Cloudflare doesn’t charge for bandwidth which Rackspace does. And unless I’m missing my guess, this won’t be inside Rackspace internal network. This means if you’re using a Rackspace server, you’ll be charged bandwidth to send to Rackspace CDN as well as bandwidth going out of Rackspace CDN, correct?


Please enter your comment!
Please enter your name here