Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

Rackspace Technology’s operating history begins in 1998. Its CDN documentation covers two different services:

  • Rackspace CDN: origin-pull delivery from publicly accessible servers, including external origins.
  • Cloud Files CDN: publication of objects stored in CDN-enabled containers.

Both use Akamai delivery infrastructure. Rackspace’s managed Cloudflare security offering is separate. Confirm onboarding and the specific service on your account before planning a new deployment.

Network

Rackspace’s documented CDN uses a custom map on Akamai’s delivery infrastructure. A Rackspace storage or managed-cloud data center is not automatically a CDN cache location.

Current cache-city locations are unconfirmed, so no map is shown. Published geography lists define delivery/access-control regions rather than physical PoPs. Confirm the locations available to your account and test delivery from your audience’s networks.

Features

FeatureSupported
Web application firewallNot listed
Bot protectionNot listed
DDoS protection◐ Partial
Rate limitingNot listed
HTTP/3 (QUIC)Not listed
TLS 1.3Not listed
Tiered cachingNot listed
Origin shieldNot listed
Instant cache purge◐ Partial
Serve stale while refreshingNot listed
Serve stale on origin errorsNot listed
Image optimizationNot listed
On-demand videoNot listed
Live videoNot listed
Digital rights managementNot listed
HLS / DASH packagingNot listed
WebSocketsNot listed
Signed URLsNot listed
Edge computeNot listed
Edge functionsNot listed
Key-value storageNot listed
Configuration API✓ Supported
Real-time logsNot listed
Log export◐ Partial
Terraform providerNot listed

✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.

Caching and access

Rackspace CDN supports path-based TTLs, multiple origins and referrer, geographic and IP restrictions. Review default caching before serving personalized content; set non-cacheable paths to bypass caching.

Cloud Files CDN objects are public. Storage authentication does not protect published URLs, and CORS is not an authorization mechanism. Shared HTTPS and custom-domain options differ between products.

Refreshing content and logs

Purging is supported, but Cloud Files has a documented daily limit and propagation delays. Use versioned files for predictable releases. CDN logs can be delivered daily to Cloud Files; this is not realtime streaming.

Product boundaries

Cloud Files’ special streaming URLs retired on July 31, 2022. For a media project, ask how live ingest, packaging and DRM will be supplied. Protocol upgrades, serverless functions, managed WAF and bot protection need product-specific confirmation rather than inheriting all Akamai or Cloudflare capabilities.

Pricing

Separate delivery from storage

Cloud Files documentation describes storage capacity and outbound CDN bandwidth billing, with no per-request CDN charge. Request the rates for your specific CDN or managed Cloudflare contract.

Rackspace CDN does not add an edge-cache storage charge; your origin’s storage and transfer can still cost money. Custom certificate options and managed services can have separate fees. The linked public CDN pricing destination now opens a general cloud page, so confirm current unit rates and account minimums.

Use the calculator with a confirmed delivery quote. For Cloud Files, set request fees to zero only when your account terms agree, and add storage, retained logs, support and other fixed costs as extras.

Developer tools

Origins and publication

Rackspace CDN accepts public web origins, including Cloud Servers, load balancers, Cloud Files and external hosting. Cloud Files exposes REST APIs and SDKs for storing objects and enabling container delivery.

Operations

Use the control panel or service-specific API for caching, origin rules and refreshes. Test permissions and Host-header handling before changing DNS. Cloud Files and Rackspace CDN have different purge limits.

Observability and security

Enabled CDN logs arrive daily in a Cloud Files container; include storage retention in your bill. Managed Cloudflare security is a separate service with its own contract terms. Check the supported CDN resources before planning Terraform automation.

When it fits

  • Existing Rackspace customers publishing static Cloud Files objects.
  • Origin-pull delivery with documented caching and access controls.
  • Teams able to confirm service availability, rates and product-specific limits.

Before you choose

  • Cloud Files CDN URLs are public; use a different access-control design for private files.
  • Check custom HTTPS and purge limits for the particular CDN product.
  • Arrange any required live logs, edge code or media processing separately.
  • Get current account rates before budgeting a new deployment.

History

Rackspace’s predecessor began operating in 1998; that date describes the company’s history, not the launch of its CDN. Rackspace Technology returned to public listing in August 2020 and trades as RXT on Nasdaq.

Cloud Files’ streaming and iOS streaming URLs were decommissioned on July 31, 2022. For another Cloud Files or CDN workflow, check its current service documentation and account support.

Sources