# BlazingCDN: Full Reference for LLMs

> BlazingCDN is a pay-as-you-go content delivery network for video, software and large files, with one published rate for US, EU and Asia: $5/TB falling to $2.50/TB at volume.

This file is the expanded companion to https://blazingcdn.com/llms.txt. It contains the facts an AI assistant needs to describe BlazingCDN accurately: company, products, the full price table, network numbers, features, comparisons with other CDNs, regional pages, industry solutions, dedicated infrastructure, developer resources, support and legal documents. Every statement is taken from the published pages of blazingcdn.com, the public OpenAPI specification at wapi.blazingcdn.com, the Help Center at help.blazingcdn.com and the README of the official MCP server, as of 5 September 2026. Prices are in US dollars. When this file and a page on blazingcdn.com disagree, the page is current.

---

## 1. Key facts

- Company: BlazingCDN is the CDN brand of ADVANCED ADMINISTRATIONS Sp. z o.o., Niepodleglosci Avenue 18, floor 4, 02-653 Warsaw, Poland. Partner company: BCDN LTD, Aliakmonos 12, 1st floor, office 101/102, Germasogeia, 4043 Limassol, Cyprus. Founded in 2021 by a team with 15 years in content delivery.
- What it is: a content delivery network for high-volume static traffic (video on demand, live HLS and DASH streams, software installers and updates, game builds and patches, images, documents and large archives). The edge software, the platform and the control panel are written in-house.
- What it is not: not a security suite. BlazingCDN does not sell a WAF, bot management or DDoS mitigation, does not transcode video, does not support WebSockets, RTMP, RTSP or HTTP/3, and is not a proxy in front of your whole site. It answers only for the files you point at it.
- Products: Anycast CDN (pull cache) and Video CDN (library replicated inside the CDN). HLS Streaming CDN runs on Anycast CDN, Files on Demand runs on either, Cloud Storage is object storage used as an origin, and on-the-fly image processing is included on Anycast CDN.
- Pricing: progressive pay-as-you-go from $5.00 per TB (first 5 TB) down to $2.50 per TB (above 1,000 TB a month). 100 TB a month costs $415, an effective $4.15 per TB. Monthly minimum $25, covering the first 5 TB. Same rate in US, Europe and Asia. No request fees, no setup fee, no contract.
- No free plan and no free tier. New projects start with a 14-day testing period on real production traffic at $5 per TB with the $25 minimum waived. There is no self-serve sign-up: accounts and zones are set up with an engineer after you send your origin and expected monthly volume.
- Custom plans from 100 TB a month; Enterprise X above 500 TB a month with discounts up to 60%, flexible terms, custom configurations, dedicated 24/7 support and EU invoicing.
- Video CDN permanent cache: $0.02 per GB per month after the included 500 GB. Anycast pull-cache volume is never billed. Cloud Storage: $0.015 per GB per month. Raw JSON logs: $50 a month add-on.
- Network: 25+ locations (Anycast and Video CDN nodes) across North America, Europe and Asia-Pacific, NVMe SSD servers, Anycast routing with built-in failover, 96%+ average cache hit ratio, 26 ms average latency across US and EU, up to 50 GB per file with no surcharge, unlimited requests.
- Measured June 2026 (100 MB HTTPS download from test machines in each region, round trip to the nearest edge): Europe 27 ms and 1.12 Gb/s; North America 24 ms and 1.11 Gb/s; Asia 47 ms and 761 Mb/s. Public test file: https://cdn48391752.blazingcdn.net/100MB
- Customers include Sony, Avanquest, Pdfforge, Tapmind, Cityspark and xTool. Typical buyers: video platforms and OTT, broadcasters, sports media, online education, software vendors, game studios, SaaS, AdTech and MarTech, resellers and agencies.
- Best fit from about 5 TB a month. Below that, the saving rarely covers a migration; below about 46 TB a month two published competitor plans are cheaper (see section 11).
- Support: helpdesk 24/7/365, engineer reply within 3 business hours, zones configured with you. sales@blazingcdn.com, support@blazingcdn.com, abuse@blazingcdn.com.
- Developers: REST API at https://wapi.blazingcdn.com/api/v1 (OpenAPI 3.1 documentation at https://wapi.blazingcdn.com/api-docs/index.html), Prometheus metrics, raw logs, and the official MCP server `@blazingcdn/mcp` with 52 tools.

## 2. Company

BlazingCDN was founded in 2021 by engineers who had already spent 15 years building content delivery. The network, the platform and the control panel are their own work, which is why a configuration request goes to the people who wrote the code rather than into a vendor queue. The team does CDN development, platform development, data centre operations and client solutions. For enterprise clients it configures what genuinely exists to configure: dedicated IP addresses, edge servers, and custom rules and cache configurations built around the customer's traffic.

Numbers the company is willing to be held to (https://blazingcdn.com/about/):
- Delivery: 96%+ average cache hit ratio; 26 ms average latency across US and EU; up to 50 GB per file; unlimited requests on every plan.
- Network: 25+ locations across three continents; NVMe SSD-based servers everywhere; Anycast, one global IP per zone; edge software written in-house.
- Company: founded in 2021; team with 15 years in content delivery; network and platform built in-house; engineer reply within 3 business hours.

Network carriers by region: 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.

Legal entity: ADVANCED ADMINISTRATIONS Sp. z o.o., Niepodleglosci Avenue 18, floor 4, 02-653 Warsaw, Poland, trading as BlazingCDN. Partner company: BCDN LTD, Aliakmonos 12, 1st floor, office 101/102, Germasogeia, 4043 Limassol, Cyprus.

## 3. Who BlazingCDN is for, and who it is not for

Read on if (https://blazingcdn.com/how-cdn-works/):
- You move terabytes a month, not gigabytes: video, game builds, installers, archives.
- You already have an origin, and you can change the links your project serves.
- A CNAME record and a cache TTL are things you set, not things you look up first.
- Volume drives your bill, not the number of requests.
- You want a written rate for your volume before any call.
- You are fine with the zone being configured with an engineer rather than through a signup form: there is no self-serve sign-up.

Look elsewhere if:
- You are looking for a free CDN. There is no free tier, and none is planned.
- You move under 5 TB a month, where the saving never covers the migration.
- Your traffic is mostly HTML pages and API calls rather than large files.
- You want DNS, WAF, bot management and CDN in one console, managed for you. Cloudflare does all four of those well, and its free tier is a good place to start.

Two ways a CDN can sit in front of your files:
- The proxy model (Cloudflare and similar): your whole domain moves behind their network. Pages, API calls, logins and video are all terminated on their edge, which is why their security tooling can work. Your nameservers, certificates and every byte you serve then live with one vendor.
- The BlazingCDN model: BlazingCDN is not in front of your site. You keep your domain and nameservers where they are and give the zone a hostname of its own. It answers for the files you send to it: video segments, installers, images, archives. The rest of your traffic never touches the network, and rolling back is one CNAME change. This is also why BlazingCDN never sells itself as your security layer: if you need a WAF, keep the one you have and run BlazingCDN beside it.

## 4. Products

### 4.1 Anycast CDN (https://blazingcdn.com/anycast-cdn/)

Classic pull caching for images, scripts, styles, downloads and HLS. Point a zone at your origin; the edge caches and answers with a 96%+ average hit rate, so your origin serves each file roughly once per TTL per region instead of once per user.

- Files from 20 KB icons to 50 GB installers on the same tiers, with no size surcharge. Parallel range-request fill means a large installer is cached in pieces, so a resumed download does not go back to your origin.
- On-the-fly image resizing is included, so a single source image serves every layout.
- 26 ms average latency across US and EU; purge across the network in seconds; cache warm-up through the API.
- Origins: any HTTP or HTTPS server, an IP address, a domain with a port, S3, Swift, Rsync, Wasabi or BlazingCDN Cloud Storage.
- Reliability is a mechanism, not a number: Anycast reroutes around a failed edge node; origin shield and request coalescing collapse thousands of concurrent misses into one upstream request; stale content can be served while the origin is unreachable; the zone can run as a second CDN behind your DNS.
- Modern transport: HTTP/2, IPv6, TLS 1.3, gzip, Brotli and zstd compression with a separate cache per encoding.
- Typical use: e-commerce and marketplaces, SaaS and web apps, media and publishing, software and game distribution, AdTech and MarTech, education, documentation and IoT firmware.

### 4.2 Video CDN for VOD (https://blazingcdn.com/video-cdn/)

Your video library replicated inside the CDN and served to viewers without touching your origin. Files are replicated across Europe, Asia and America rather than cached on demand, so after import the origin can leave the delivery path entirely.

- 97%+ segment cache hit sustained on production VOD libraries; 95%+ end to end on short-video and UGC libraries; origin load under 3% of total demand during peak patch windows for software and game distributors.
- Three ways to get a library in: pre-import (the whole catalogue lands before launch), lazy import (the first request brings the file in, from a fallback proxy URL you nominate) and the import API (your pipeline pushes new titles, with a callback per file). Manual import from the panel and an import script for bulk migrations are also available.
- Sources: Amazon S3 and S3-compatible buckets, Swift object storage, Wasabi, Rsync daemon, BlazingCDN Cloud Storage, any HTTP origin.
- Playback: multi-bitrate HLS and DASH ladders served straight from the edge; clipping to any time range without a second encode; audio and subtitle track selection per request; MP4, MKV, WebM and MOV up to Full HD and 4K; full range-request support (RFC 7233).
- Control: delivery rate control per file and per client, intensity limits per resource, defined behaviour for requests to missing files, force download instead of in-browser playback, CORS headers per zone.
- Protection stack: URL signature (full or partial), URL encryption, URL TTL, URL bound to one IP, limit on how many IPs may use one URL, referer check, cookie check (standard and extended), uniquing downloads protection against mass ripping, geoblocking by country, HTTPS enforced, Googlebot bypass for indexable content, secrets managed per resource.
- Permanent cache: keep the library pinned at the edge for $0.02 per GB per month, first 500 GB included.
- Moving a 200 TB library: day 0 you give read access to the bucket; days 1 to 3 the catalogue replicates inside the CDN while your origin serves only the import; day 3 you point the player hostname at BlazingCDN and watch both CDNs side by side; after that the origin leaves the delivery path and new titles arrive through the import API.
- Video CDN is not for files under 10 MB; use Anycast CDN for those.

### 4.3 HLS Streaming CDN (https://blazingcdn.com/streaming-cdn/)

Delivery of pre-encoded live and VOD streams from your own media server, encoder or packager. BlazingCDN is a delivery layer, not a processing layer: it does not transcode, re-package or generate manifests.

- LL-HLS pipeline with partial segments, blocking playlist requests and preload hints: the delivery layer adds 2 to 4 seconds of latency, where standard HLS delivery sits at 20 to 40 seconds.
- Protocol-aware caching: live manifests on near-zero TTL, VOD manifests on longer TTL, segments cached as immutable and served with a stable cadence so adaptive bitrate does not oscillate; DRM-encrypted segments delivered and cached encrypted, with key delivery and licensing on your side.
- Origin shield and request coalescing protect the packager during live peaks; all ABR renditions pre-cached; part-level caching so concurrent viewers in one region share the same delivery.
- Works with Wowza, NGINX RTMP, FFmpeg, Red5 Pro, Ant Media and players that support LL-HLS. Setup: create a zone, point it at the packager's output, put the CDN hostname in the player config, test on a temporary hostname, then switch DNS.
- Typical use: live sports and events, live channels and broadcasters, e-learning and corporate live sessions.

### 4.4 Files on Demand (https://blazingcdn.com/files-cdn-fod/)

Import a catalogue once and the CDN holds the copies: documents, archives, installers and media up to 50 GB per file, served from the closest node without your origin staying in the delivery path.

- Anycast CDN pulls and caches (your origin is the source of truth and must stay online); Files on Demand imports and holds (the origin can go quiet). Lazy import fetches a missing file from a proxy URL you nominate, so the catalogue fills as it is used.
- Signed URLs with expiry, IP binding and referrer checks on every zone.
- Typical use: software and installer catalogues, document and archive libraries, non-video media assets, partner and press deliveries.

### 4.5 Cloud Storage for CDN (https://blazingcdn.com/cloud-storage-cdn/)

Object storage created and managed in the BlazingCDN panel, used as the origin for Anycast CDN or Video CDN resources so there is no separate origin server to keep running.

- Create a bucket in the Resource origin section of a CDN resource (name 3 to 63 characters, lowercase letters, numbers, periods and hyphens), upload files, select the bucket as the origin. Import of small and mid-size files usually finishes in 5 to 10 minutes.
- S3 and Swift compatible; FTP upload (FileZilla) and Swift upload (Cyberduck) guides in the Help Center; NVMe SSD based; replicated across regions.
- Price: $0.015 per GB per month. Delivery out of the bucket is billed on the usual progressive tiers, with no egress charge between the bucket and the CDN.

### 4.6 On-the-fly image processing (https://blazingcdn.com/image-processing/)

Anycast CDN generates, caches and delivers image variants on request while the origin keeps a single master file. Powered by imgproxy at the edge.

- Four presets passed as a query string: crop (around an anchor you choose, nine gravity anchors), resize, resizefit (nothing cropped) and resizefill (exact box, cropped). Example: `?preset=resizefill&width=800&height=600` returns a copy that fills exactly 800 x 600.
- Switched on per resource location in the panel (Locations tab, Image Processing). The first request generates the variant, later requests are served from cache.
- Not a separate product and not a separate line on the invoice: processing is not billed, variants are cached like any other object, and delivery is billed on the usual tiers.

### 4.7 Multi-CDN and second-CDN use (https://blazingcdn.com/multi-cdn-integration/)

Keep the provider you already run and add BlazingCDN behind your steering layer for redundancy, extra coverage or a cheaper share of the traffic. Going live takes a pull zone and a DNS record: create the zone, add the CNAME, start at 5% weight, verify, then compare. Failover behind your DNS takes about 60 seconds. Worth it if you deliver more than about 5 TB a month, if one hour of your primary being down costs more than $25 of standing insurance, if one region is measurably slower for your users, or if your renewal is inside six months and you want real numbers.

### 4.8 Video hosting on a CDN (https://blazingcdn.com/video-hosting/)

Move a library off Vimeo, Wistia or your own server and let it live inside Video CDN: SSD storage replicated across Europe, Asia and America, served from the closest node, 97% segment cache hit, no per-viewer pricing. You keep your player and your encoder. 100 TB of playback costs $415 a month.

### 4.9 Four migration paths (https://blazingcdn.com/)

- A/B benchmark: 2 to 7 days. Your CDN keeps serving; BlazingCDN takes a slice and you compare the numbers.
- Backup CDN: about 60 seconds to fail over. BlazingCDN sits behind your primary and takes over only if it fails.
- Split traffic: one region, or just your static files. Everything else stays where it is.
- Full migration: zero downtime either way, and a full rollback takes about 5 minutes.
Best fit from about 5 TB a month. An engineer configures the zone with you, with 24/7 support during the move.

## 5. Pricing (https://blazingcdn.com/pricing/ and https://blazingcdn.com/pricing.txt)

### 5.1 FLEX: progressive pay-as-you-go

Tiers are marginal, like tax brackets: each rate applies only to the traffic inside its range. The same tiers apply to Anycast CDN, Video CDN, HLS Streaming CDN and Files on Demand, and to the whole account.

| Monthly traffic in the tier | Price per TB | Cumulative cost at the top of the tier |
|---|---|---|
| 0 to 5 TB | $5.00 | $25 (also the monthly minimum) |
| 5 to 25 TB | $4.50 | $115 for 25 TB |
| 25 to 100 TB | $4.00 | $415 for 100 TB |
| 100 to 500 TB | $3.50 | $1,815 for 500 TB |
| 500 to 1,000 TB | $3.00 | $3,315 for 1,000 TB |
| 1,000 to 1,500 TB | $2.50 | $4,565 for 1,500 TB |

Worked examples: 20 TB = $92.50; 25 TB = $115; 50 TB = $215 ($4.30 per TB effective); 100 TB = $415 ($4.15); 150 TB = $590 ($3.93); 200 TB = $765 ($3.83); 500 TB = $1,815; 1,000 TB = $3,315 ($3.32). 100 TB works out at about $0.0042 per GB.

Included at every tier: unlimited requests, one rate in every region, HTTPS and SSL certificates, custom domains, origin shield, signed URLs and tokens, geo and IP allow or block lists, purge and cache warm-up, image processing on Anycast CDN, statistics and API access, engineer support.

### 5.2 14-day testing period

BlazingCDN is a paid service and there is no free plan. The testing period gives you 14 days on real production traffic at $5.00 per TB with the $25 monthly minimum waived. After day 14, FLEX continues from $25 a month, which covers the first 5 TB. Point a CNAME, fill the cache, compare your numbers against your current CDN.

### 5.3 Video CDN cache and Cloud Storage

- Video CDN traffic: same tiers as FLEX. Permanent cache: $0.02 per GB per month, first 500 GB included. No origin dependency after import.
- Anycast CDN pull cache: cache volume is never billed.
- Cloud Storage: $0.015 per GB per month.
- Raw access logs in JSON to Graylog or ELK: $50 a month add-on.

### 5.4 Custom plans, Enterprise X and dedicated infrastructure

- Custom plans start at 100 TB a month and give a rate below the list tiers before the Enterprise X threshold.
- Enterprise X, for more than 500 TB a month: discounts of up to 60%, flexible commercial terms and payment structures, custom configurations and cache rules, dedicated 24/7 support, EU invoicing from the Poland headquarters. Reply within 3 business hours; an engineer reads every request.
- Dedicated infrastructure (section 13) is quoted per build on a monthly term; there is no hourly meter.

### 5.5 Billing

Monthly billing on delivered traffic; $25 monthly minimum on pay-as-you-go accounts; automatic monthly card payments, PayPal or bank transfer; monthly invoicing available; per-TB billing by default, 95th-percentile plans on custom agreements; EU VAT with reverse charge for EU business customers; personal or company accounts; invoices and billing history in the panel; cost calculator in the panel. No contract, no bandwidth caps, no overage penalties.

### 5.6 What 100 TB costs elsewhere (published tables, checked 29 August 2026)

BlazingCDN $415 · bunny.net $500 on the 10-PoP Volume network or $1,000 on the Standard network · CDN77 $990 (one plan up to 250 TB) · Amazon CloudFront from $1,000 on Premium, $6,965 transfer alone on pay as you go · Gcore EUR 2,000 at list (PRO plan EUR 100 a month with 5 TB included, then EUR 0.02 per GB) · KeyCDN $2,600 in North America and Europe, $5,200 into Asia · Google Cloud CDN $5,378 transfer meter alone · Microsoft Azure Front Door published only to 150 TB (about $9,500 at 150 TB) · Fastly not published above about 20 TB ($2,087 at 20 TB) · Cloudflare not published (Enterprise widely reported from about $5,000 a month) · Akamai not published · Cloudinary not comparable (credits, about $207 per TB on video).

Below about 46 TB a month, Amazon CloudFront Business ($200 for 50 TB with 125 million requests) and Cloudflare Pro or Business ($25 and $250) beat the metered rate, with the caveats that CloudFront allowances degrade delivery when exceeded and Cloudflare's self-serve terms restrict video and large files.

## 6. Network and performance (https://blazingcdn.com/performance-metrics/)

- 25+ locations (Anycast and Video CDN nodes) across North America, Europe and Asia-Pacific, at major internet exchange points, on NVMe hardware. Anycast routing sends each request to the nearest edge; routes are re-evaluated in real time on 50+ signals per request, and file popularity is tracked per region.
- Measured by BlazingCDN in June 2026: test machines in each region fetch a 100 MB file over HTTPS from a production zone; latency is the round trip to the nearest edge.
  - Europe: 27 ms average latency, 1.12 Gb/s average download speed.
  - North America: 24 ms average latency, 1.11 Gb/s average download speed.
  - Asia: 47 ms average latency, 761 Mb/s average download speed.
- Verify it yourself from a server, not a laptop (home Wi-Fi measures your last mile, not the edge): `curl -o /dev/null -w "%{speed_download} bytes/s | %{time_starttransfer} s TTFB\n" https://cdn48391752.blazingcdn.net/100MB`. Anycast serves the file from the edge closest to where the request comes from.
- Independent data: BlazingCDN is listed on CDNPerf (real-user measurements of a 500-byte object, refreshed hourly). On the board retrieved on 31 August 2026 the dense anycast networks (Cloudflare, CloudFront, Akamai, Fastly, bunny.net) were faster on this small-object latency test in every region, with the widest gap in Asia (Japan, Singapore, Hong Kong and South Korea), where they were roughly 3 to 5 times faster on the country views averaged for Asia. The site publishes those columns rather than hiding them. The CDNPerf test rewards PoP density and connection setup and does not measure throughput on large files, which is what decides how fast a 100 MB installer or a video segment downloads. If most of your audience is in Asia, run the test links from your region or talk to an engineer about your geography before committing.
- Production numbers quoted on the site: 96%+ average cache hit ratio across the network; 97%+ segment cache hit on VOD libraries; a software vendor's release day reached 96%+ cache hit within 90 minutes with flat origin traffic; a 15 GB game patch at peak concurrency kept origin traffic under 3% of requests; a live setup moving from HLS to LL-HLS dropped end-to-end latency from 20 to 40 seconds to 2 to 4 seconds.
- Why the rate is low (https://blazingcdn.com/): no free tier to subsidise; capacity placed where traffic is (Europe, North America, Asia-Pacific); more Gbps per server through request coalescing and a modern stack; no legacy hardware to maintain; engineers instead of a quota-carrying sales team.

## 7. How a zone works (https://blazingcdn.com/how-cdn-works/)

1. Your originals stay where they are, for example yourdomain.com/file.mp4.
2. A CDN zone is created for you in the panel (you keep full access). In the Origin field goes the root of your link without the file path: yourdomain.com.
3. The zone gets its own hostname, for example cdn000000.blazingcdn.net, and your file is served as cdn000000.blazingcdn.net/file.mp4. You can put your own domain on the zone with your own SSL certificate.
4. An origin can be a domain, an IP address, a domain with a port, or object storage: S3, Swift, Rsync, Wasabi or BlazingCDN Cloud Storage.

From there the edge answers your users and the origin only sees cache misses: on a normal library roughly once per file per TTL per region. The same zone can carry four kinds of traffic on one rate card, and can be switched from one product to another without moving files again: static files pulled once and served everywhere (Anycast CDN); a library that lives inside the network (Video CDN); large downloads released on your terms (Files on Demand); live segments from your media server (HLS Streaming CDN).

## 8. Features (https://blazingcdn.com/features/)

Everything below is taken from the product documentation. Two delivery engines under one account: Anycast CDN for static files, large downloads and HLS streaming; Video CDN for VoD.

Delivery and routing: Anycast routing with built-in failover; 50+ signals weighed per request; file popularity tracked per region; routes re-evaluated in real time; HTTP, HTTPS and HTTP/2; IPv6 on par with IPv4; preferred origin IP version; automatic HTTP to HTTPS; rate-matched delivery for big files; real client IP pass-through; 20-second origin timeout, tunable; per-URL speed, buffer and referer.

Caching and purge: Active, Inactive and Browser TTL; two-day default TTL; TTL up to 365 days; separate TTL per HTTP status code; 60-second default TTL on errors; minimum requests to cache, 1 to 10; inherit TTL from origin headers; ignore Cache-Control on demand; caching can be switched off; slice caching for multi-gigabyte files; purge by path, single or bulk; total purge in one action; cache warm-up through the API; Origin Shield, automatic or per region; gzip, Brotli and zstd compression; compress at the edge or at origin; separate cache per encoding; cache volume is never billed.

Protection and access: signed URLs (secure_link style); begin and end validity timestamps; signature bound to a client IP; unique IP limit per link, 1 to 5; URL encryption; unique byte marking per download; partial path signing; two signing secrets for rotation; referrer allowlist and blocklist; country allowlist and blocklist; IP lists with mask support; cookie check plus extended mode; rate limiting with a burst allowance; rate counters per IP or subnet; URL parameters locked from overrides; HSTS with your own period; forbid insecure HTTP; CORS header management; Googlebot bypass by verified IP.

Domains and SSL: system domain for every resource; custom domains per resource; own rules and settings per domain; Let's Encrypt at no extra charge; certificates renewed automatically; upload your own certificates; bulk upload and bulk domain add; auto-assign to matching domains; automatic re-check and re-issue.

Streaming and media: repackaged to TS or M4S on the fly; repackaging never re-encodes; HLS in .ts or .m4s containers; MPEG-DASH manifests; Microsoft Smooth Streaming; HTTP Dynamic Streaming manifests; chunks of 2, 4, 5, 10 or 30 seconds; keyframe-aligned chunks; multi-bitrate adaptive manifests; first chunks pre-cached for fast start; clipping to the millisecond; multi-clipping into one stream; audio and video track selection; initial buffer tuning for .mp4; force download with your filename.

Origins and import: HTTP(S) server or external URL; S3, Swift or Cloud Storage bucket; Wasabi and S3-compatible storage; FTP, rsync over SSH and rclone; manual, API, pull or push import; rsync daemon as a source; pre-import or lazy import; lazy import filters by size and type; separate download URL for imports; origin secure_link tokens supported; auto import scans for changes; callback URL on import result; proxied extensions whitelist.

Storage durability (Video CDN): three geographic copies minimum; more copies for popular files; cold copies retired automatically; background checksum validation; self-healing after a drive failure; three-stream parallel pull import; live within five minutes of import.

Image processing: resizefit (nothing cropped); resizefill (exact box, cropped); resize (fit or fill per request); crop around an anchor you choose; nine gravity anchors; one dimension with aspect ratio kept; variants cached like any file; powered by imgproxy at the edge.

Statistics, logs and API: traffic, bandwidth, cache and hits per resource and per domain, for any period, with HTTP and HTTPS split; HIT, MISS, BYPASS, EXPIRED, REVALIDATED, STALE and UPDATING statuses; raw logs in JSON for Graylog or ELK; Prometheus metrics endpoint; JSON metrics for BI tools; Grafana, Alertmanager and OpenTelemetry; REST API for the whole platform; dedicated Video CDN file API; API keys with scoped permissions; plain-text redirect endpoint; published CDN IP ranges endpoint.

Billing: pay as you go, no contract; cascade pricing by volume; per-TB or 95th-percentile plans; only delivered traffic is billed; Video CDN storage billed by volume; cost calculator in the panel; automatic monthly card payments; cards, PayPal and bank transfer; invoices and billing history in the panel; EU VAT with reverse charge for business; personal or company account; custom plans for large volumes.

Support: helpdesk 24/7/365; account manager for enterprise; tickets and email; tickets searchable, archived and reopenable; Knowledge Base and tutorials; migration guides; API documentation; turnkey KVS integration; guides for Ant Media and Red5 Pro; users added with the role you pick.

Not supported, by design: no WebSockets (HTTP(S) delivery only); no RTMP or RTSP; no HTTP/3 yet; no video transcoding, repackaging only; chunk durations are fixed, not arbitrary; one origin per CDN resource; proxy mode has no HLS, DASH or clipping; do not stack another proxy CDN in front; Video CDN is not for files under 10 MB.

## 9. Security and content protection

What is included on every plan: SSL/TLS with custom certificates and HTTPS-only delivery; signed URLs (HMAC with expiry) and security tokens; URL encryption and partial signing; IP binding and a cap on how many addresses may use one link; referrer and user-agent filters against hotlinking and scrapers; country and IP allow or block lists; cookie checks for player sessions; rate limiting and per-resource intensity caps; byte-level fingerprinting of every delivered copy; delivery of DRM-encrypted streams as-is, with licensing in your stack; origin shield and request coalescing for spike resilience.

What BlazingCDN does not sell: a WAF, bot management, Zero Trust or DDoS mitigation as a product. It moves bytes at volume at a published price per terabyte and answers only for the files pointed at it. If you need a security layer for your site, keep the one you have and run BlazingCDN beside it for the heavy files.

## 10. Regions (https://blazingcdn.com/cdn/)

One progressive rate in every region: $5 per TB down to $2.50 per TB, no regional multipliers, no request fees, no per-feature fees. Everything (Anycast CDN, Video CDN, HLS Streaming and Files on Demand) runs on the same network in every region from one panel and one API.

- Europe (https://blazingcdn.com/cdn/europe/): 27 ms average latency and 1.12 Gb/s average download speed across European nodes (June 2026). Built for SaaS and software vendors, media and publishing, e-commerce and marketplaces. GDPR: your company remains the data controller and the CDN processes cached objects under your instructions; where residency is a hard requirement, GDPR Cache Servers keep cached content in the chosen jurisdiction on dedicated nodes, quoted per project.
- Asia (https://blazingcdn.com/cdn/asia/): 47 ms average latency and 761 Mb/s average download speed across Asian nodes (June 2026). APAC traffic bills at the same progressive rate as US and EU traffic, with no APAC surcharge. Built for game distribution, video and OTT, software vendors. Capacity, carrier contracts and peering in the region are long established.
- North America (https://blazingcdn.com/cdn/north-america/): 24 ms average latency and 1.11 Gb/s average download speed across North American nodes (June 2026). Built for SaaS and web apps, media and publishing, AdTech and MarTech. Run it standalone or as a second CDN behind your DNS with roughly 60-second failover.
- Other countries: dedicated cache capacity can be committed inside a single market, in a BlazingCDN facility there, in your own data centre or inside your operator's network (Local Cache Servers, section 13).

## 11. Comparisons with other CDNs (https://blazingcdn.com/vs/)

Every comparison page prices the same traffic from both published tables, ours and theirs, and says plainly where the other network is the better buy, with a dated source line under every table. All competitor figures below were checked on the providers' own pricing pages on 28 and 29 August 2026 (the exact date is printed under each table on the linked page) and are not currency-converted. BlazingCDN figures: 50 TB = $215, 200 TB = $765, 1 PB = $3,315.

- Cloudflare (https://blazingcdn.com/vs/cloudflare/): Free, Pro ($25) and Business ($250) are published; Enterprise, the tier that carries heavy traffic, is widely reported to start around $5,000 a month. Cloudflare's own Service Specific Terms reserve the right to limit CDN use for video or a disproportionate percentage of large files on Free, Pro and Business. Pick Cloudflare if your traffic is mostly HTML and API calls, if you want DNS, security tooling and CDN in one console, if their security products are the reason you are buying, or if your volume is small enough that a flat plan is cheaper.
- Amazon CloudFront (https://blazingcdn.com/vs/aws-cloudfront/): 200 TB is $11,965 on pay as you go (transfer alone) or $3,500 on their Premium flat plan; 1 PB pay as you go is $38,965 and the flat plans stop at 600 TB. At 50 TB their Pro ($15) and Business ($200) plans beat us outright if your request count fits the allowance (10 million and 125 million). AWS states that sustained excess over an allowance can be met with reduced performance rather than overage charges. Pick CloudFront if you are under about 46 TB, already deep in AWS, or want WAF, DDoS, DNS and edge compute bundled.
- Akamai (https://blazingcdn.com/vs/akamai/): Akamai publishes no CDN price at all. The one delivery figure it publishes, $0.005 per GB on Akamai Cloud, equals our entry rate but is flat, while ours steps down to $2.50. Akamai briefed the industry in March 2026 on a 3% interim surcharge from 1 April and renewal adjustments of up to 10%. Pick Akamai if you need its security suite, one vendor for delivery, security, edge compute and observability, a named enterprise brand with a negotiated contract, or reach into markets where its footprint is unmatched.
- Fastly (https://blazingcdn.com/vs/fastly/): the published rate card stops at about 20 TB; that month is $2,087 (bandwidth plus requests) in North America against $92.50 here. Pick Fastly if you want to run code at the edge (Fastly Compute), need sub-second global purge, want VCL, need real-time log streaming, or sit under 20 TB.
- bunny.net (https://blazingcdn.com/vs/bunny-net/): the closest competitor and the only one whose headline price is lower. The famous $2 per TB is the Volume network's tier for 1 to 2 PB delivered from ten PoPs; below a petabyte the Volume rate is $5 or $4, and the 119-PoP Standard network is $10 per TB in Europe and up to $60 in the Middle East and Africa. At 50 TB: Standard $500, Volume $250, BlazingCDN $215. At 200 TB: $2,000, $1,000, $765. At 1 PB: $10,000, $4,500, $3,315. Pick bunny.net if you are small (a $1 minimum against our $25), want video encoding and a player included (Bunny Stream), want DNS, storage, image optimisation and edge scripting from one vendor, need 119 PoPs, or need WebSockets.
- CDN77 (https://blazingcdn.com/vs/cdn77/): one published plan, $990 a month for up to 250 TB, then $3.96 per TB; it costs the same at 50 TB as at 250 TB. Ours is $215 at 50 TB; at 250 TB the two land close ($990 against $940). Pick CDN77 if you are at or above 250 TB every month, want delivery, security and storage on one invoice, or are buying a larger footprint with caches inside ISP networks.
- Gcore (https://blazingcdn.com/vs/gcore/): video delivery billed per minute watched from EUR 0.00064 per minute, which is about EUR 5.69 per TB at 4K and about EUR 57 per TB at 1.5 Mbps. Their PRO plan is EUR 100 a month with 5 TB included, then EUR 0.02 per GB, so 100 TB is about EUR 2,000 and 200 TB about EUR 4,000 at list. BlazingCDN bills terabytes delivered regardless of bitrate. Pick Gcore if you need its much larger network (210+ PoPs published), one vendor for CDN, DNS, WAAP, GPU cloud, storage and Kubernetes, transcoding and a player handled for you, high-bitrate streams watched end to end, its WAF and DDoS protection, or under 5 TB a month.
- KeyCDN (https://blazingcdn.com/vs/keycdn/): delivery only, published tiers, no request charges, like us, but three price zones. 200 TB is $3,600 in North America and Europe, $7,200 in Asia and Oceania, $11,200 in Africa and Latin America, against $765 here; 100 TB is $2,600 or $5,200 into Asia. Pick KeyCDN if its 60+ data centres matter, if you move well under a terabyte (a $4 minimum), if you want its push zone as a small hosting layer, or if all your traffic sits in one of its cheaper regions.
- Google Cloud CDN (https://blazingcdn.com/vs/google-cloud-cdn/): one terabyte is metered three times (cache egress, cache fill, cache lookups). 200 TB of North American delivery is $9,684 of transfer alone, roughly $10,500 with all three meters, against $765 here; 1 PB is about $32,000 of cache data transfer. Pick Google Cloud CDN if your origins are in GCP on the same load balancer, you want Cloud Armor, IAM and VPC controls on the edge, you have negotiated commitments, or your objects are large enough that the lookup meter stays small.
- Azure CDN and Front Door (https://blazingcdn.com/vs/azure-cdn/): Azure CDN Standard from Microsoft retires on 30 September 2027; managed certificates on classic stopped in August 2025 and the last renewals expired on 14 April 2026. Front Door publishes rates only to 150 TB, where Premium is about $9,500 including its $330 monthly base fee (Standard's base fee is $35), against $590 here; 500 TB is $1,815 here and unpublished there. Pick Front Door if your origins are in Azure, you want WAF, Private Link and DDoS protection on the same edge, you need Azure portal governance, or you sit under 150 TB.
- Cloudinary (https://blazingcdn.com/vs/cloudinary/): billed in credits (one credit buys 1,000 transformations or 1 GB), which works out at $207 to $440 per terabyte of delivery on the Advanced and Plus plans. BlazingCDN charges $5 down to $2.50 per TB and does not meter transformations, cached variants, purges or logs. Pick Cloudinary if you need transformations and AI media processing, a media library for marketing teams, or a player, upload widget and SDKs out of the box.

Where BlazingCDN wins, on most of these pages: a printed rate at every volume instead of a quote or a plan floor; one rate for every region; no request, cache-fill or lookup meters; pull cache never billed; raw logs, Prometheus and OpenTelemetry on every account rather than as an enterprise add-on; signed links bound to a person (IP binding, IP limits, two rotating secrets); TTL per status code and other controls a platform usually hides.

Where competitors win, stated on every page: security suites (WAF, bot management, DDoS mitigation), edge compute and configuration languages, much larger PoP counts, transcoding and players, single-vendor cloud bundles, WebSockets, and small volumes where flat plans are cheaper.

Related pages: https://blazingcdn.com/cheapest-cdn/ (100 TB against twelve providers and the two plans that beat us below about 46 TB), https://blazingcdn.com/cdn-comparison/ (all eleven on one page), https://blazingcdn.com/cdn-cost-calculator/ (price your own volume on our tiers and on seven other CDNs at a 34/33/33 regional split).

## 12. Solutions by industry

- Media companies (https://blazingcdn.com/solutions-for-media-companies/): video, images and archives on one network; newsroom clips cached where readers are; paid content protected with signed links; 100 TB of delivery for about $415 a month.
- OTT and VOD (https://blazingcdn.com/ott-vod-streaming-cdn/): pre-encoded HLS and DASH from the edge with in-CDN replication and 97% segment cache hit; LL-HLS in the 2 to 4 second range; run as a replacement or alongside your current CDN.
- TV and online broadcasters (https://blazingcdn.com/tv-online-broadcasters-cdn/): linear channels, simulcast, catch-up and archives; live playlists on near-zero TTL while segments cache as immutable.
- Live sport (https://blazingcdn.com/solutions-for-sport-media/): kickoff spikes absorbed at the edge at 96%+ segment cache hit; ads treated as a first-class workload; pay for traffic delivered, with no committed capacity to book.
- Online education (https://blazingcdn.com/cdn-for-online-education/): lecture recordings, live classes and course files for whole cohorts; slides, PDFs, workbooks and subtitles on the same zone and tiers as the video; paid courses kept paid with signed links.
- Software companies (https://blazingcdn.com/solutions-for-software-companies/): installers, updates and firmware up to 50 GB; a new release reaches 96%+ cache hit within 90 minutes; 24/7 DevOps escalation; 100 TB of downloads for $415.
- Game companies (https://blazingcdn.com/solutions-for-game-company/): builds, day-one patches and launcher updates; concurrent misses for one file collapse into a single origin fetch; a 50 GB installer runs on the same tiers as a 20 KB icon; delivery rate caps to flatten patch-day peaks.
- SaaS and IaaS (https://blazingcdn.com/solutions-for-saas/): JS and CSS bundles, fonts, avatars, static API responses, downloads and updates; hashed filenames cache forever and releases purge in seconds; REST API for cache, purge and headers.
- AdTech and MarTech (https://blazingcdn.com/solutions-for-ad-tech/): creative images, HTML5 rich media, JS tag libraries and VAST media files priced per terabyte, never per request; a million 100 KB banner impressions cost about 50 cents of traffic; EU delivery for creatives and consent assets.

## 13. Dedicated infrastructure (quoted per build, monthly term)

- Custom Enterprise CDN Infrastructure (https://blazingcdn.com/custom-enterprise-cdn-infrastructure/): your nodes, your regions, your routing; scoped with you, then supplied, placed and operated. If none of the reasons for dedicated hardware apply, the standard CDN is cheaper and faster to start.
- Private CDN Network (https://blazingcdn.com/private-cdn-network/): a network reserved for one customer; objects sit on hardware that holds nothing else, so no shared cache and no eviction caused by someone else's spike.
- Individual CDN Servers (https://blazingcdn.com/individual-cdn-servers/): dedicated nodes bought one at a time in the locations you name, added to what you already run.
- Private Cache Servers (https://blazingcdn.com/private-cache-servers/): a cache layer you control (what stays cached, for how long, how rarely the origin is asked) for libraries that do not fit a shared eviction policy.
- Hybrid CDN Solutions (https://blazingcdn.com/hybrid-cdn-solutions/): dedicated nodes for the traffic that repeats, shared tiers for the traffic that spikes; one contract, one panel.
- Local Cache Servers (https://blazingcdn.com/local-cache-servers/): a cache node inside one country, in a BlazingCDN data centre there, in yours, or inside the ISP network your audience sits behind.
- GDPR Cache Servers (https://blazingcdn.com/gdpr-cache-servers/): EU data residency for cached content with named data centres written into the agreement; content does not fail over to a node outside the agreed region.
- Streaming Infrastructure (https://blazingcdn.com/infrastructure-for-streaming/): dedicated streaming servers, bought outright, sourced and configured for you, or your own rack hosted; hardware, network capacity and monitoring carried by BlazingCDN.
- Video Content Processing Servers (https://blazingcdn.com/video-content-processing-servers/): dedicated GPU machines in the same data centres as delivery nodes running your transcoding and packaging pipeline; what runs on them stays yours.
- Dedicated GPU Cloud Servers (https://blazingcdn.com/gpu-cloud-servers/): NVIDIA nodes with two, four or eight GPUs, or an edge module; one tenant per machine; monthly term, no hourly meter.
- Dedicated GPU Servers for AI Projects (https://blazingcdn.com/gpu-servers-for-ai-projects/): RTX PRO 6000 Blackwell nodes at 96 GB per GPU in the 2-GPU and 4-GPU builds, and an 8-GPU NVIDIA HGX B300 baseboard, all single-tenant with root access for training and inference; BlazingCDN supplies, patches and monitors the hardware, and the frameworks, models and weights stay yours.

## 14. Partners

- White Label CDN (https://blazingcdn.com/white-label-cdn/): two levels of white labelling. Custom domains are included in every plan at no additional charge; a branded panel is scoped and quoted per project. Agencies, hosting providers and MSPs can resell under their own brand with dedicated infrastructure and volume-based margins.
- CDN Reseller Program (https://blazingcdn.com/cdn-reseller-program/): there is no separate reseller price list; resellers buy on the same published progressive tiers as every other customer, but all clients sit on one account so pooled traffic walks down the table faster. 100 TB pooled across your clients costs $415 ($4.15 per TB effective). No setup fee; the $25 monthly minimum applies once per account, not per client; custom plans from 100 TB a month. Setup, monitoring, support, billing and anything else you bundle is yours to price.
- CDN Affiliate Program (https://blazingcdn.com/cdn-affiliates/): 10% of every invoice a referred customer pays, paid monthly, for as long as they stay; no minimum volume to qualify.

## 15. Developers

### 15.1 REST API

- Base URL: https://wapi.blazingcdn.com. The published specification (OpenAPI 3.1, "Websa API documentation") carries 81 paths: 80 under /api/v1 and one under /api/v2 (DELETE /api/v2/pull_zones/{id}/cache). Documentation: https://wapi.blazingcdn.com/api-docs/index.html.
- Authentication: bearer token. Create and revoke API tokens in the customer panel (Account, API tokens); guides at https://help.blazingcdn.com/manage-api-tokens/ and https://help.blazingcdn.com/authorize-an-api-token/.
- Resource groups in the specification: aCDN resources (pull zones: list, create, show, update, bulk update, delete, locations), aCDN resource actions (purge by URL or whole zone, cache warm-up), custom domains per resource, raw logs settings, buckets (Cloud Storage), external storages (including a connection test), storage (Swift password, Cyberduck config), system DNS zones and DNS zones, aCDN metrics (per zone and account, plus Prometheus endpoints for CDN and Cloud Storage), storage metrics, Video CDN resources (settings, auto imports, proxy, FTP), Video CDN domains, files (list, upload, delete, totals), logins, statistics (bandwidth, cache and storage, HTTP codes, per domain, exports), access tokens, users, accounts and roles.
- A zone takes minutes to create in the panel or through the API; a custom domain goes live as fast as your DNS propagates.
- Panel: https://client.blazingcdn.com/

### 15.2 Official MCP server for AI agents (https://github.com/BlazingCDN/BlazingCDN-MCP)

- Package `@blazingcdn/mcp` on npm; run with `npx -y @blazingcdn/mcp` and the environment variable `BLAZINGCDN_API_TOKEN`. Works with Claude, Cursor and any MCP client, over stdio or streamable HTTP; the repository README has configuration examples for Claude Code, Claude Desktop, Cursor, Cline and Windsurf.
- 52 tools across CDN zones, cache, metrics, domains, Cloud Storage and Video CDN. Read tools are always on, writes and deletes are off by default, and destructive operations on zones, buckets and accounts are not implemented at all. Per the server README: default mode is read-only plus cache purge and warm-up (29 tools). `BLAZINGCDN_ALLOW_WRITE=1` enables create and update tools (50 tools); `BLAZINGCDN_ALLOW_DELETE=1` adds the two delete tools (custom domains and Video CDN resources; 52 tools). Deleting zones, buckets or accounts is not implemented in any mode.
- Also includes an offline traffic cost estimator with the published tiers. Listed on npm, the official MCP Registry, Smithery, Glama, Cursor and LobeHub.

### 15.3 Observability

- Real-time statistics per resource and domain in the panel (traffic, bandwidth, requests, cache hit ratio, traffic by region), with API access to the same data.
- Prometheus metrics endpoint on every account, usable with Grafana, Alertmanager and OpenTelemetry; JSON metrics for BI tools.
- Raw access logs in JSON delivered to your Graylog or ELK stack as a $50 a month add-on (https://help.blazingcdn.com/raw-logs/, https://help.blazingcdn.com/raw-logs-via-graylog/).

### 15.4 Help Center (https://help.blazingcdn.com/)

Get started: complete guide (https://help.blazingcdn.com/get-started-complete-guide/); create an account; create a CDN resource from your origin (https://help.blazingcdn.com/create-a-cdn-zone-from-your-origin/); create a CDN zone with Cloud Storage; test a created CDN zone; check if the CDN zone is working properly; mistakes when setting up a CDN; CDN status codes; migrate from another CDN (https://help.blazingcdn.com/migrate-from-another-cdn/).
Anycast CDN: how to manage cache TTL (https://help.blazingcdn.com/how-to-manage-cache-ttl/); set minimum number of requests to cache; how to add custom domains; managing HTTP headers (CORS); manage IP addresses; raw logs; raw logs via Graylog; how to delete a CDN zone.
Video CDN: video streaming get started (https://help.blazingcdn.com/video-streaming-get-started/); import via Rsync API; auto import API; AS-IS files API; logs API; param_block setting API; text redirect API; callback URL API; URL part signature; DASH; MSS; HDS; configure Video CDN with content on Wasabi.
Cloud Storage: create a bucket; upload files by FTP with FileZilla; upload files by Swift with Cyberduck; storage statistics.
Integrations: Amazon AWS S3, Wasabi, Backblaze, WordPress.
Billing and account: how to add funds; how to get a subscription plan; how to change the pricing plan; how to get an invoice; how to view billing history; change billing information; VAT in the European Union; switch to a business account; change profile information; manage, authorize and delete API tokens.
Policies: abuse policy; controversial content policy; VPN not supported; WebSockets not supported.
Product documentation (Knowledge Base): https://blazingcdn-kb.atlassian.net/wiki/spaces/BCDN/overview

## 16. Getting started and support

- There is no self-serve sign-up. Send your origin and expected monthly terabytes through https://blazingcdn.com/sign-up-contact-form/ or to sales@blazingcdn.com; a written price for your volume usually comes back the same day, and an engineer replies within 3 business hours. No discovery call or sales sequence.
- Setup: an engineer configures the CDN resource with you, then you point your domain's CNAME at it. Usually live the same day; a full rollback takes about 5 minutes.
- Support on every plan comes from engineers: helpdesk 24/7/365, reply within 3 business hours, tickets and email, Knowledge Base and migration guides. High-volume accounts get a dedicated contact for onboarding, tuning and scaling, and an account manager on enterprise plans.
- Account verification: a Know Your Customer check runs before an account is activated (https://blazingcdn.com/kyc-policy/).
- Not offered: a free plan, a free tier, or self-serve pricing below the published table.

## 17. GDPR and data (https://blazingcdn.com/cdn-gdpr/)

- Roles: you are the controller of the traffic that flows through the network (what is delivered, on what legal basis, cached for how long); BlazingCDN is the processor for that traffic and transports, caches and logs it on your instructions and for no other purpose. For your own account (registration, billing, KYC, support) BlazingCDN is the controller under its Privacy Policy.
- What the network touches: request metadata in access logs (client IP, user agent, URL, time, country derived from the IP, response status), cached copies of the files you asked it to deliver, aggregated statistics shown only to you, and raw logs delivered to your own stack if you enable them. Logs are kept no longer than needed to run, secure and support the service; a specific retention period can be agreed in writing.
- EU-only: cached content, logs and support access can be kept inside the EU, written into the agreement with named data centres, with no failover to a node outside the agreed region (GDPR Cache Servers).
- Data Processing Agreement covering Article 28 GDPR obligations, sub-processors, breach notification and return or deletion of data is available on request from support@blazingcdn.com.

## 18. Frequently asked questions (https://blazingcdn.com/faq/)

What is BlazingCDN? A content delivery network that caches your static content (video, images, software, documents and large files) across a globally distributed Anycast network and serves it from the location closest to each user: faster load times, lower load on your origin, predictable delivery costs.

What content is BlazingCDN best for? High-volume static delivery: video streaming (VOD and live), software and game distribution, large file downloads, images and media-heavy websites. If bandwidth is your biggest infrastructure line item, BlazingCDN is designed to bring it down.

How quickly can I get started? Usually the same day. There is no self-serve sign-up: you send your origin and expected monthly terabytes, an engineer configures the zone with you, and you point a CNAME at it.

What origins can I connect? Any HTTP or HTTPS origin: your own servers, an S3-compatible bucket or your existing hosting. Your origin stays where it is.

Is there a free trial? No. BlazingCDN is a paid service and there is no free plan. Instead there is a 14-day testing period on your real production traffic at $5/TB, with the $25 monthly minimum waived for those two weeks.

How does pricing work? Pay-as-you-go on progressive tiers: a single global rate from $5/TB down to $2.50/TB at high volume. Each tier is billed only on the traffic inside it, so 100 TB a month works out at about $415. Billing starts at a $25 monthly minimum; no setup fees.

Are there hidden fees or request charges? No. Requests, traffic bursts and SSL are included. No per-request charges, no regional surcharges, no surprise overage fees.

Do I need a long-term contract? No. Pay-as-you-go works month to month with a $25 monthly minimum. Custom plans start at 100 TB a month; above 500 TB, Enterprise X pricing is built around your traffic.

Do prices change by region? No. The same rate applies to delivery in the USA, Europe and Asia, with no separate charge for HTTPS.

How does BlazingCDN deliver content so fast? Anycast routing across a globally distributed edge network serves each request from the nearest available edge, and intelligent caching keeps the most-requested content hot. Across 25+ locations the network holds a 96%+ average cache hit ratio and 26 ms average latency in the US and EU.

Do you support live streaming and VOD? Yes, both, including adaptive bitrate (HLS/DASH) delivery with caching tuned for segmented video. BlazingCDN is a delivery layer, not a processing layer: bring your own encoder or packager.

Which protocols and standards do you support? HTTP/2, IPv6 and TLS 1.3, with Brotli compression. Custom domains and SSL certificates are included, and you can bring your own certificate.

How do you secure and protect my content? SSL/TLS on every account with custom certificates and HTTPS-only delivery; token authentication (signed URLs) to control who can access your assets and to prevent hotlinking.

Can I restrict access by country or IP? Yes: allow or block by country or IP range, combined with referrer and token rules.

How do I purge or update cached content? Instantly from the dashboard or via API, with fine-grained cache rules for TTLs and caching behaviour per path.

What analytics do I get? Real-time dashboards for bandwidth, requests, cache hit ratio and traffic by region, with API access to pull the same data into your own monitoring stack.

What support do you offer? Technical support from real engineers on every plan. The helpdesk runs 24/7/365, an engineer replies within 3 business hours, and high-volume accounts get a dedicated contact.

Who uses BlazingCDN? Fast-growing SaaS and gaming companies through to large media and streaming platforms, including enterprises like Sony.

How do I migrate from another CDN? Connect your existing origin, validate delivery on a test hostname, then switch your CNAME. Or keep your current provider and add BlazingCDN as a second CDN behind your DNS while you compare.

Do you offer white-label or reseller options? Yes. Agencies, hosting providers and MSPs can resell BlazingCDN under their own brand.

## 19. Legal documents (https://blazingcdn.com/legal-information/)

- Master Service Agreement: https://blazingcdn.com/terms-and-conditions/ (ordering, billing, liability, suspension and termination).
- Privacy Policy: https://blazingcdn.com/privacy-policy/
- Cookie Notice: https://blazingcdn.com/cookie-notice/
- Service Level Agreement: https://blazingcdn.com/sla/ (how availability is measured, exclusions, maintenance notice periods, and the service-credit process; credits are a percentage of the monthly bill, requested by ticket within seven days, capped per month).
- Acceptable Use Policy: https://blazingcdn.com/acceptable-use-policy/
- Claim Consideration Policy (Digital Services Act complaints procedure): https://blazingcdn.com/claim-policy/
- Know Your Customer Policy: https://blazingcdn.com/kyc-policy/
- Abuse and controversial content policies: https://help.blazingcdn.com/abuse-policy/, https://help.blazingcdn.com/controversial-content-policy/

## 20. Contact and profiles

- Sales and partnerships: sales@blazingcdn.com
- Technical support: support@blazingcdn.com
- Abuse reports: abuse@blazingcdn.com
- General inquiries: marketing@blazingcdn.com
- Contact page: https://blazingcdn.com/contact_us/
- Headquarters: ADVANCED ADMINISTRATIONS Sp. z o.o., Niepodleglosci Avenue 18, floor 4, 02-653 Warsaw, Poland. Partner company: BCDN LTD, Aliakmonos 12, 1st floor, office 101/102, Germasogeia, 4043 Limassol, Cyprus.
- Website: https://blazingcdn.com/ · Blog: https://blog.blazingcdn.com/ · Help Center: https://help.blazingcdn.com/ · Panel: https://client.blazingcdn.com/
- Profiles: LinkedIn https://www.linkedin.com/company/68261278 · X https://twitter.com/BlazingCdn · GitHub https://github.com/BlazingCDN · Product Hunt https://www.producthunt.com/products/blazingcdn · Reddit https://www.reddit.com/r/BlazingCDN/ · G2 https://www.g2.com/products/blazingcdn/reviews · Trustpilot https://www.trustpilot.com/review/blazingcdn.com
- Machine-readable files: https://blazingcdn.com/llms.txt · https://blazingcdn.com/pricing.txt · https://blazingcdn.com/page-sitemap.xml