Multi-CDN FAQ
Which CDN backends does Multi-CDN use?
Multi-CDN Orchestration is a consolidation edge that can deliver across multiple CDN backends (e.g. Raven CDN, Eagle CDN, Hawk CDN). One is the primary backend; you can toggle secondaries per orchestrator from Settings. Traffic distribution across active backends is handled by the load balancer.
Do I have to move my DNS to VNETWORK?
No. You keep your DNS provider and point the specific hostnames you want delivered at the edge (with the CNAME shown on the domain). Records you don't onboard are unaffected.
Can I use Object Storage as an origin?
Yes. Set your Object Storage bucket as the origin for a domain (on the Origin tab) to serve static files straight from storage through the CDN.
How do I push out an updated file?
Publish it to your origin, then purge the cached path from the domain's Purge & Warm tab. The edge refetches on the next request. You can also warm URLs so the first visitor gets a cache hit.
Why is my cache hit ratio low?
Check the Cache tab: make sure caching is enabled, TTLs aren't zero, and no rule is bypassing the cache for the paths in question. The Service Overview cache-distribution donut shows the hit/miss split.
What's the difference between the CDN WAF and WAAP?
The CDN-attached WAF protects delivered traffic with managed and custom rules. Web Application & API Protection is the dedicated product for deeper defense — AI-WAF, bot management, rate limiting and API protection — and can front the same domains.
Can I run one domain across several CDN services?
A domain lives in one orchestrator at a time, but you can move it to another same-provider orchestrator without losing analytics history — see Move a domain.
Is Multi-CDN available for self-serve activation?
Yes. Self-serve activation is one orchestrator per organization; the Activate Multi-CDN button appears on the CDN home when your org has none yet. For additional orchestrators, contact your VNETWORK account manager.