SECOND CDN · MULTI-CDN SETUP
BlazingCDN as Your Second CDN
Keep the provider you already run and add us behind your steering layer for redundancy, extra coverage or a cheaper share of the traffic.
From $5/TB down to $2.50/TB with no committed volume · 14-day testing period on real traffic, $25 monthly minimum waived · Engineer reply within 3 business hours
60 s
Failover to the second CDN
96%+
Average cache hit ratio
3 regions
One rate in Europe, Asia and America
Four reasons teams run a multi-CDN setup
A multi-CDN setup routes traffic across two or more CDN providers behind one steering layer. None of these four reasons require touching the provider you already have: the zone is independent, and turning it off changes nothing on their side.
One provider is a single point of failure
Outages happen to everyone, and a status page does not serve your files. A second CDN that already holds a warm cache takes the load when you shift weight to it, as fast as the TTL on your steering record allows.
The bill grew faster than the traffic
Move the price-insensitive share, static assets and large downloads, onto progressive per-TB tiers. The arithmetic is blunt: 100 TB a month costs about $415 here, against about $8,500 at a $0.085/GB list rate. Compare us with CloudFront, Cloudflare or Akamai on the same volume.
Coverage is uneven where you are growing
Europe, Asia and America run on one rate card, with 24 to 27 ms latency measured across US and EU. If a region is underserved by your primary, route that region to us and compare the numbers on the same traffic: Europe, Asia, North America.
You want leverage at renewal
A live second provider with real traffic and real numbers is a different conversation from a quote. No commitment on our side means the leverage costs you $25 a month to hold. Check your current minimum commit before you shift weight, and bring numbers from our side-by-side comparisons.
Where we sit in your multi-CDN setup
Your steering layer keeps deciding who gets what: weighted Route 53, Azure Traffic Manager, NS1, Cedexis or Cloudflare Load Balancing all work the same way here. We are a pull origin at the other end of one of those routes, filled from your origin and independent of your primary provider.
Your users
One hostname. Nothing in your player, app or page markup changes.
Your steering layer
Weighted Route 53, Azure Traffic Manager, NS1, Cedexis or your own logic. It decides the split and it stays yours.
Two routes, two caches
Route A: the CDN you already run, untouched.
Route B: a BlazingCDN pull zone, filled from the same origin and cached independently.
Route B: a BlazingCDN pull zone, filled from the same origin and cached independently.
Your origin
One origin, read by both. No migration, no second copy of your library.
A secondary CDN should cost like one
No volume commitment, a $25 monthly floor. Carrying 10% of a 100 TB month costs about $47.50, because a small share still sits in the first tiers. The rate falls as you move more over, and there is no second contract to sign.
It sits behind your steering layer
Weighted DNS, a traffic manager or your own logic decides the split. We are a pull origin at the other end: point the zone at the same origin and the CDN hostname at your steering record.
Failover in about 60 seconds, set by your TTL
Keep us warm on a small share of traffic so the cache is not cold when you need it. How fast the switch lands depends on the TTL you set in your steering layer: a 60-second record moves traffic in about a minute.
The same objects, cached independently
Our cache is filled from your origin, not from your other CDN. Nothing about your primary provider has to change, and nothing breaks if you turn us off.
Going live takes a zone and a DNS record
Four steps, usually under thirty minutes of work. Nothing changes on your current provider: it keeps its own config, its own cache and its own contract. Set the weight back to zero and your setup is exactly as it was.
01
Create a pull zone
Point it at the same origin your primary CDN already reads. One call to the API or one form in the panel. Your origin needs no change, and no data has to be moved.
02
Add the CNAME
Put the CDN hostname in your steering layer as one more answer: weighted Route 53, Azure Traffic Manager, NS1, Cedexis, Cloudflare Load Balancing or your own RUM logic. The record stays yours.
03
Start at 5% weight
Enough traffic to keep the cache warm and to produce numbers worth reading. The TTL on that record is what decides how fast a switch lands: a 60-second record moves traffic in about a minute.
04
Verify, then compare
Request the same object through both hostnames, read the cache header, then compare latency and invoice on identical traffic. Turn the weight to zero at any time and nothing on your side is left behind.
When a second CDN pays for itself, and when it does not
We would rather you read this before the zone than after the first invoice.
Worth it if
- You deliver more than about 5 TB a month, so a per-TB rate is worth splitting
- One hour of your primary being down costs more than $25 of standing insurance
- One region is measurably slower for your users than the rest of your map
- Your renewal is inside six months and you want real numbers, not a quote
Look elsewhere if
- You are below about 5 TB a month: a second setup costs more attention than it saves
- Your traffic is mostly dynamic API calls rather than cacheable objects
- You have no steering layer and no plan to add one: two CDNs need something to choose between them
- Your current contract carries a minimum commit you would breach by moving traffic
Coverage where your primary is thin
Europe, Asia and America run on one rate card, with 24 to 27 ms latency measured across US and EU. If a region is underserved by your current provider, route that region to us and compare the two on the same traffic: CDN in Europe, CDN in Asia, CDN in North America.
- Region by region: the split is yours to set, and you can move it back at any time.
- Cache stays warm where it matters: our 96%+ average cache hit ratio is a network figure across zones carrying full traffic. A 5% slice starts lower and climbs as its popular objects settle.
- Somewhere specific in mind? Tell our engineers which markets matter and they will tell you honestly what our network does there today.
Carrier diversity your primary may not have
A second CDN is only worth adding if it reaches your users over different paths than the first one. These are the transit and peering networks our upstream providers use in each region. Names are trademarks of their owners and imply no partnership.
- North America
- NTT
- AT&T
- Lumen (Level 3)
- Cogent
- Comcast
- Europe
- NTT
- Deutsche Telekom
- Orange
- Lumen (Level 3)
- Liberty Global
- Sparkle
- Cogent
- Telefonica
- Telia
- Zayo
- Asia-Pacific
- NTT
- Lumen (Level 3)
- KINX
- PLDT
- Singtel
- SK Broadband
- Tata Communications
- Telstra
- South America
- NTT
- Lumen (Level 3)
- Lanautilus
- Telefonica
Second-CDN speed in Europe, Asia and North America
Speed data measured June 2026
Avg. Download Speed
Latency
Test link
*Measured with a 100 MB object over residential connections, June 2026. Anycast answers from the nearest node, so a single test link returns a different edge for each region. Download speed and latency vary with the quality of your own connection.
What a share of your traffic costs
Progressive tiers work like tax brackets: each rate applies only to the traffic inside its range. There is no committed volume, so a month where we carry almost nothing costs almost nothing, down to the $25 floor.
TIER 01
First 5 TB
$5.00 per TB
- $25 for the whole tier
- This is also the monthly minimum
TIER 02
5 to 25 TB
$4.50 per TB
- $90 for the next 20 TB
- 25 TB in total: about $115
TIER 03
25 to 100 TB
$4.00 per TB
- $300 for the next 75 TB
- 100 TB in total: about $415
100 TB a month works out at $415
Each tier is billed only on the traffic inside it, so the tiers add up rather than replace each other. 25 TB is about $115, 500 TB is about $1,815, and above 500 TB a month we quote it for you.
Which product to point the second route at
Anycast CDN
Classic pull cache for player scripts, posters, thumbnails and subtitle files. Files up to 50 GB, on the same progressive tiers.
Video CDN
Your catalogue is replicated inside the CDN and served from the closest server, so the origin can leave the delivery path entirely.
HLS Streaming CDN
Delivery for streams you have already encoded: HLS, LL-HLS and DASH, with manifests and segments cached on separate rules.
Files on Demand
Large-file delivery for catalogues that change often: import once, serve everywhere, and let the CDN hold the copies.
Straight answers about running two CDNs
What is a multi-CDN setup?
A multi-CDN setup delivers the same content through two or more CDN providers, with a steering layer deciding which request goes where. The steering layer is usually weighted DNS or a traffic manager, and each CDN keeps its own cache, filled from your origin.
Can I run two CDNs without leaving my current provider?
Yes. Your provider keeps its own configuration, cache and contract, and never learns about the second route. Our zone reads the same origin, so there is nothing to migrate and nothing to switch off first. Check your current minimum commit before you move a large share.
How do you split traffic between two CDNs?
By weight, by region, or by workload. Weighted DNS records in Route 53, Azure Traffic Manager, NS1, Cedexis or Cloudflare Load Balancing all do this, and so does your own RUM-based logic. A common start is 5% by weight, or one region routed entirely to the second provider.
How fast is failover to the second CDN?
About a minute with a 60-second TTL on your steering record, which is the number you control, not us. Two things decide the real figure: how quickly resolvers honour that TTL, and whether the second CDN was kept warm. A zone carrying 5% of traffic already holds your popular objects; a cold zone spends the first minutes filling from origin.
What does a second CDN cost if it carries only 10% of my traffic?
On a 100 TB month, moving 10 TB to us costs about $47.50: the $25 first tier plus 5 TB at $4.50. There is no committed volume and no second contract, so the floor is $25 in a month where you send almost nothing. The rate per terabyte falls as you move more over, down to $4.00 above 25 TB.
Does running two CDNs hurt cache hit ratio?
Yes, and it is worth saying plainly. Splitting requests splits the cache: each provider sees fewer requests per object, so both fill from your origin more often than one provider would. The 96%+ figure we publish is a network average across zones carrying full traffic, not what a 5% slice will show in week one. Two things keep it sane: split by region or by workload rather than at random, and give the second zone enough weight for its popular objects to stay warm.
Get a second-CDN plan
Tell us your volume and who you run today. You get back a written rate for the share you plan to move, plus the zone and CNAME steps for your setup. An engineer replies within 3 business hours.
We use this only to price your traffic and reply to you. Prefer to read first? See the full pricing table, run the numbers in the cost calculator, or read how a CDN pull origin works. Running your own nodes as well? That is hybrid CDN.