PULL CDN · STATIC ASSETS
Anycast CDN
Classic pull caching for images, scripts, styles and downloads. Point a zone at your origin: we cache at the edge and answer with a 96%+ average hit rate, so your origin serves each file roughly once per TTL per region instead of once per user.
From $5/TB down to $2.50/TB at volume · 14-day testing period on real traffic · $25 monthly minimum waived · Engineer reply within 3 business hours
26 ms
Average latency across US and EU
96%+
Average cache hit ratio at the edge
50 GB
Largest single file, no surcharge
Small files by default. Large ones too, up to 50 GB.
Anycast CDN does not care what the file is. A 20 KB icon and a 50 GB installer go through the same pull cache and the same progressive tiers. Most of the web lives in the first two columns.
Under 1 MB
- WebP and AVIF images
- JS bundles and chunks
- CSS and WOFF2 fonts
- JSON and API responses
- SVG icons and sprite sheets
- Map tiles
- Subtitles and VTT files
1 to 10 MB
- Full-size product and article photos
- Short MP4 or WebM loops
- MP3 and AAC audio, voice notes
- PDF price lists and manuals
- ZIP, APK and patch files
- Game textures and sound banks
- ONNX, TFLite and WASM modules
10 MB to 50 GB
- Installers, disk images, asset packs and large archives, up to 50 GB per file
- Same pull cache, same progressive tiers, no separate plan and no size surcharge
- Pick Video CDN instead when files must live inside the CDN and your origin should not have to stay online
Six businesses, the same pull cache
Ordered by how often we see it. Every file below is static, and the sizes run from a few kilobytes to 50 GB.
E-commerce and marketplaces
Product photos and thumbnails, category banners, seller logos, PDF invoices. Thousands of small files, each requested by thousands of people.
SaaS and web apps
JS and CSS bundles, WOFF2 fonts, icon sprites, JSON config and localisation, user avatars. Hashed filenames cache forever.
Media and publishing
Article images and galleries, short MP4 loops in place of GIFs, audio previews, podcast clips. Traffic arrives in spikes when a story lands.
Software and game distribution
Patches, APKs, plugin updates and manifests, game textures, atlases and sound banks, plus full installers up to 50 GB. Release day is one cold cache, then everything is warm.
AdTech and MarTech
Banner creatives, HTML5 ad units, VAST documents, tag scripts, tracking pixels. Small files where tens of milliseconds decide whether the ad renders.
Education, docs and IoT
Course PDFs and slides, short lesson clips, subtitle files, map tiles, firmware and OTA updates for devices in the field.
Twelve kinds of file, ordered by how much of the web they are
Images alone are the single heaviest thing the web ships. Everything in this list is static and cacheable, and sizes run from a 5 KB pixel to a 50 GB installer.
Most of the traffic
- Images: JPEG, PNG, WebP, AVIF, SVG. The heaviest thing the web ships.
- JavaScript bundles, chunks and polyfills.
- CSS and web fonts in WOFF2.
- JSON, API responses, localisation and config files.
Common, growing fast
- Short MP4 and WebM loops, the format that replaced the GIF.
- Audio: MP3 and AAC previews, notification sounds, voice messages.
- PDFs: invoices, manuals, price lists, catalogues.
- User uploads: avatars, listing photos, chat attachments.
Specialised, still static
- Archives and installers: ZIP, APK, patches, disk images, up to 50 GB per file.
- Game assets: textures, atlases, sound banks, level packs.
- Browser ML models and WASM modules: ONNX, TFLite.
- Map tiles, ad creatives with VAST, IoT firmware updates.
Plain files, cached at the edge
Six MP4 files of the same clip, from 3.8 MB to 87.3 MB, sit in Cloud Storage behind an Anycast pull zone. Pick a rendition in the player settings: each one is an ordinary HTTP object, cached once per region and served from the closest node.
MP4 files · Anycast pull zone
1080pQuality·Bitrate·File size
Served from
Served fromOne file, one URL
No manifests, no packaging. The browser requests the MP4 with range requests and the edge answers from cache.
Small or large, same cache
The 4K file here is 87.3 MB; the same pull cache handles installers, images and archives up to 50 GB per file.
Try it with curl
Fetch any rendition below twice: the second request is answered by the edge, not by storage.
Files:
https://cdn84906683.blazingcdn.net/ny-street/mp4/360p.mp4 … https://cdn84906683.blazingcdn.net/ny-street/mp4/2160p.mp4 · Footage: Pexels, free licence Release day, measured
On a software-distribution launch the cache fills as the first requests arrive in each region, then the edge answers the rest. Parallel range-request fill means a large installer is cached in pieces, so a resumed download does not go back to your origin.
Once the edge hit ratio passes 95%, download availability stops depending on origin capacity: your server sees roughly one request per file per region, not one per user.
Figures come from our own edge measurements, not from a vendor benchmark. Ask us for the raw numbers behind your workload. Latency benchmarks →
What's in the box
Every control below is available from the panel and the API, on every plan, with no per-feature fees.
Cache control
TTL per path and file type, query-string rules, instant purge API.
Content protection
Signed URLs, referrer whitelisting, UA filters, geo restriction.
Spike resilience
Request coalescing, burst absorption, origin shield.
Modern transport
HTTP/2, Brotli, IPv6, TLS 1.3.
API & automation
Zone management and purge from CI/CD.
Multi-CDN ready
Run us as a secondary or backup CDN with ~60 s DNS failover.
Pull caching, explained in one pass
One pass through the request path: what happens on the first hit, and what happens on every hit after it.
You create a CDN zone
You create a CDN zone and point it at your origin (server or object storage).
First request per region pulls the file from origin
First request per region pulls the file from origin; every following request is answered from edge cache.
You control behavior per file type and path
You control behavior per file type and path: default and max TTL, query-string handling, cache key rules.
Purge propagates across the network within seconds
Purge propagates across the network within seconds; stale-while-revalidate keeps responses fast while content refreshes.
HTTP/2, Brotli and Gzip, full range-request support, free Let's Encrypt or custom SSL, custom domains.
What happens when something breaks
Reliability is a mechanism, not a number
Four failures that happen to every CDN. Here is what ours does in each one.
An edge node goes down
BGP withdraws the route and the next node answers the same IP. No DNS change, no TTL to wait out.
Your origin is unreachable
Cached objects keep serving. On paths you mark, stale content goes out while we revalidate in the background.
Ten thousand people hit a cold file at once
Concurrent misses collapse into one origin fetch. Your server answers once, the edge fans it out to everyone else.
You want us as a second CDN
Run BlazingCDN as backup behind your DNS. Failover takes about 60 seconds, and you keep your current CDN running.
Test CDN Speed Across Top Regions
Speed data measured June 2026
Avg. Download Speed
Latency
Test link
*Download speed and latency may vary depending on the quality of your network connection.
{
"pull_zone": {
"name": "string",
"source": "origin",
"origin": "string",
"origin_ssl": true,
"origin_url": "string",
"bucket_id": "8f7ac8aa-ed2b-4e16-81e0-0766bdb092b8",
"folder_name": "string",
"cache_gzipped": true,
"domain": "string"
}
}
Powerful API & DevOps Integration
BlazingCDN plugs into the stack you already run: a REST API for zones, cache, certificates and metrics, an official MCP server for AI agents, and a Prometheus endpoint for Grafana or Alertmanager.
Purge and warm up cache from your CI, pull traffic data into your own dashboards, and keep the panel for the rare manual change.
Reliable Network Carriers You Can Trust
- North America
- NTT
- AT&T
- Lumen (Level 3)
- Cogent
- Comcast
- Europe
- NTT
- Deutsche Telekom
- Orange
- Lumen (Level 3)
- Liberty Global
- Sparkle
- Cogent
- Telefónica
- Telia
- Zayo
- Asia-Pacific
- NTT
- Lumen (Level 3)
- KINX
- PLDT
- Singtel
- SK Broadband
- Tata Communications
- Telstra
- South America
- NTT
- Lumen (Level 3)
- Lanautilus
- Telefónica
Anycast CDN
For small static assets: mp4, images, installers, API responses. Classic pull cache, where your origin stays the source of truth, we cache on demand and serve from the edge closest to the user.
Video CDN | VOD
For large media files. Files replicate inside the CDN, so your origin doesn't have to carry the load, or even stay online for delivery. Permanent cache: $0.02/GB, first 500 GB included.
HLS Streaming CDN
Delivery of pre-encoded HLS/LL-HLS streams from your media server. Typical glass-to-glass latency with LL-HLS: 2-4 seconds. We deliver streams, we don't transcode them.
Simple math
$5/TB down to $2.50/TB as volume grows. 100 TB/month ≈ $415. One rate across regions, HTTPS included, no request fees.
Full pricing → · Delivering large files? Compare with Video CDN →
Custom Configs