BlazingCDN
Help Center
Login
Get Started
BlazingCDN
Contact us
Login
Get Started
BlazingCDN
BlazingCDN
Contact us
Login | BETA
Login
Get Started
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.

Check Pricing
Talk to a CDN Engineer

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
Pdfforge
Sony logo
Cityspark
xTool logo
Avanquest logo

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 27 ms in Europe and 24 ms in North America, measured June 2026. 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.
Your origin
One origin, read by both. No migration, no second copy of your library.

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.
Get the zone and CNAME steps
Calculate your share

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 27 ms in Europe and 24 ms in North America, measured June 2026. 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
Europe
Download Speed
1.12Gb/s
Latency
27 ms
Test link​
Test link (100 MB)
Asia
Download Speed
761Mb/s
Latency
47 ms
Test link​
Test link (100 MB)
North America
Download Speed
1.11 Gb/s
Latency
24 ms
Test link​
Test link (100 MB)
*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.
Get a second-CDN plan

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.
See the full pricing table

Which product to point the second route at

Globe icon representing Anycast CDN delivery from edge nodes worldwide

Anycast CDN

Classic pull cache for player scripts, posters, thumbnails and subtitle files. Files up to 50 GB, on the same progressive tiers.
Video player icon representing video delivery on BlazingCDN

Video CDN

Your catalogue is replicated inside the CDN and served from the closest server, so the origin can leave the delivery path entirely.
Play button with signal waves representing live and on-demand stream delivery

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 files imported once and served from every region

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.

Questions buyers ask about adding BlazingCDN as a second CDN

BlazingCDN runs as a second CDN next to your current provider, behind a weighted DNS split you control. Shares can start at 5% of traffic, pricing runs from $5 per TB down to $2.50 with a $25 monthly minimum, and a 14-day testing period runs on real production traffic.

Carrying 20% of a 250 TB month means 50 TB on BlazingCDN, which costs $215 (as of October 2026). There is no committed volume, so the bill follows the share you route. The tiers are progressive: $5 per TB for the first 5 TB, $4.50 up to 25 TB and $4.00 up to 100 TB. A 40% share of the same month is 100 TB, which costs $415.

The floor is the $25 monthly minimum, which buys the first 5 TB. That minimum works as standing insurance when the second route sits mostly idle. Requests are not billed, and the rate is the same in the US, Europe and Asia. For example, moving the Asia share of your traffic costs the same per TB as moving the US share. No long-term contract applies, so the share can shrink or grow from one month to the next without any penalty.

BlazingCDN joins behind your DNS or steering layer with a weighted split, and you set the share, for example 5% to start. Going live takes four steps. Create a pull zone on the origin you already use. Add the CNAME for your hostname. Start at a small weight in your steering layer. Verify logs and hit ratio, then compare the two providers on the same traffic.

The split can be set region by region and moved back at any time. BlazingCDN does not proxy your DNS, so the steering layer stays yours. A small slice starts with a lower cache hit ratio and climbs as popular objects settle; the network average is 96%+ across zones carrying full traffic. Onboarding takes about one hour with an engineer. Without a steering layer, two CDNs have nothing to choose between them, so add one before the second CDN goes live.

Usually not: BlazingCDN advises against a second CDN below about 5 TB a month, because the setup costs more attention than it saves. The $25 monthly minimum covers the first 5 TB (as of October 2026), so a tiny share pays the same as a 5 TB share. A second route also needs a steering layer, logs and monitoring on both sides.

A second CDN pays for itself in other cases. Traffic above 5 TB makes a per-TB split worthwhile. One hour of primary downtime may cost more than $25 of standing insurance. One region may be measurably slower for your users than the rest. A renewal inside six months benefits from real numbers instead of a quote. Traffic that is mostly dynamic API calls fits poorly, and so does a contract with a minimum commit you would breach. For example, a 3 TB site should stay on one CDN.

With BlazingCDN as the second CDN, failover between providers takes about 60 seconds, driven by your steering layer and the DNS TTL. When health checks mark the primary as down, the steering layer shifts weight to BlazingCDN. A short TTL on the CNAME keeps that switch quick for resolvers. Inside BlazingCDN, Anycast routing has built-in failover between edge servers, so a single node problem does not need a DNS change.

A warm second route fails over better than a cold one. Keeping a standing share, for example 5% to 10%, keeps popular objects cached on BlazingCDN before an incident. Measured June 2026 on a 100 MB HTTPS download, average latency was 27 ms in Europe, 24 ms in North America and 47 ms in Asia. The $25 monthly minimum (as of October 2026) is the standing cost of keeping the route ready.

BlazingCDN’s upstream providers use 5 transit and peering networks in North America: NTT, AT&T, Lumen (Level 3), Cogent and Comcast. In Europe the list is Deutsche Telekom, Orange, Liberty Global, Sparkle, Telefonica, Telia and Zayo. In Asia-Pacific it is KINX, PLDT, Singtel, SK Broadband, Tata Communications and Telstra. South America adds Lanautilus. The names are trademarks of their owners and imply no partnership.

Carrier diversity is the reason to add a second CDN at all. A second route only adds resilience if it reaches users over different paths than the first one. Compare this list with the carriers behind your current provider. For example, if your primary is thin in one region, route that region to BlazingCDN and compare both on the same traffic. Measured June 2026 on a 100 MB HTTPS download, Europe averaged 1.12 Gb/s and Asia averaged 761 Mb/s.