OTT AND VOD · HLS AND DASH

VoD and OTT Streaming CDN

Pre-encoded HLS and DASH delivered from the edge, with an LL-HLS path in the 2-4 second range where standard HLS leaves viewers 20-40 seconds behind the action.

From $5/TB down to $2.50/TB, so 100 TB of streaming is about $415 a month · 14-day testing period on real traffic · $25 monthly minimum waived · Engineer reply within 3 business hours

97%+
VOD segment cache hit
2-4 s
Latency on LL-HLS live
3 regions
One rate in Europe, Asia and America
Pdfforge
Sony logo
Cityspark
xTool logo
Avanquest logo

What 100 TB of streaming costs

Progressive tiers work like tax brackets: each rate applies only to the traffic inside its range. Requests, HTTPS, custom domains and origin shield are included, and the rate is the same in Europe, Asia and America.
TIER 01

First 5 TB

$5.00 per TB
TIER 02

5 to 25 TB

$4.50 per TB
TIER 03

25 to 100 TB

$4.00 per TB
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.

Your catalogue, played from the edge

A title from a VOD library, packaged as HLS with four renditions up to 1080p, served through an Anycast pull zone. Pick a quality in the settings or let Auto follow the connection.
HLS · Anycast pull zoneCar scene clip from a VOD library streamed as HLS through BlazingCDN
1080pQuality·Bitrate·Last segmentBlazingCDNServed from

Every title, every rendition

The ladder you encode is the ladder we serve; nothing is re-encoded or capped on the way.

Cached once per region

The first viewer pulls a segment from Cloud Storage; every next viewer in that region gets it from the edge, and your origin stays idle.

Try it in your own player

Copy the manifest URL below into VLC, Safari or any HLS player. Same files, same CDN, no sign-up.
Manifest: https://cdn84906683.blazingcdn.net/car-movie/hls/master.m3u8 · Segments: 4 s · Footage: Pixabay, free licence

How chunks reach the player

Our CDN optimizes the delivery of media chunks, ensuring fast loading and smooth transitions between segments. This results in uninterrupted streaming for your viewers, with minimal delays and increased reliability.
Release-day traffic chart: the edge absorbs the download spike while origin load stays flat

What the stream runs on

Protocols, protection and players. Everything below is per zone, and none of it costs extra on any plan.

Formats we deliver

Protecting the stream

Players and devices

Network Carriers

Simple setup: just bring your media server

To get started with BlazingCDN’s Streaming CDN, all you need is your own media server. We are a delivery layer, not a processing layer: we do not transcode, re-package or generate manifests, and that is exactly why nothing we do can break your encoding pipeline.

  • Supported media servers: Wowza Streaming Engine, NGINX RTMP, FFmpeg and others that produce HLS or DASH output.

  • Flexible configuration: point the zone at your packager’s output and put the CDN hostname in your player config. Test on a temporary hostname before switching DNS.
Viewer watching video on a tablet, streamed from the nearest edge node
				
					{
  "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"
  }
}
				
			

Media Streams with Full API Support

BlazingCDN’s Streaming CDN includes an extensive API that gives you full control over your CDN configuration, allowing for automation, monitoring, and customization of your streaming delivery.

Test CDN Speed Across Top Regions

Speed data measured June 2026
Avg. Download Speed
Latency
Test link
Europe
Download Speed
1.12Gb/s
Latency
27 ms
Test link​
Asia
Download Speed
761Mb/s
Latency
47 ms
Test link​
North America
Download Speed
1.11 Gb/s
Latency
24 ms
Test link​
*Download speed and latency may vary depending on the quality of your network connection.

Streaming teams, written up in full

Each one is a full write-up in our knowledge base: what was breaking, what we changed, and what the numbers did afterwards.

OTT provider, multi-region

Playback quality drifted between regions and buffering followed the time zone. In-CDN replication put the same library in every region, so playback stopped depending on which continent the viewer sat in.

Live sports streaming

Concurrency triples at kickoff and every buffering second costs an ad break. The case covers how the edge absorbed the spike and what it did to ad delivery during the monetised moments.

Short-video platform

Millions of small clips, and the first second of each one decided whether the viewer stayed. The write-up covers what happened to startup delay once files were served from inside the CDN.

E-learning platform

Paid courses were being shared outside the paywall. Signed URLs, IP binding and referer checks closed the leak without changing the player or the checkout.
GETTING STARTED

Move without a risky migration

Nothing here asks you to switch the whole audience first and find out afterwards.

Run a 14-day testing period

14 days on real production traffic at $5/TB, with the $25 monthly minimum waived. Point a CNAME, let the cache fill, compare the numbers against your current CDN.

Keep your current CDN running

Put us behind your DNS as a second provider. Failover takes about 60 seconds, and nothing changes for viewers while you compare the two.

Start with one region or one channel

Move a single channel or a single region first. The zone is configured around whatever you decide to send it, and our team sets it up with you.

An engineer, not a ticket queue

Send your stream parameters and expected concurrency, and our team configures the zone around them. An engineer replies within 3 business hours.

Questions buyers ask about OTT and VOD streaming delivery

BlazingCDN delivers pre-encoded HLS, LL-HLS and DASH streams for OTT and VOD platforms, either as a replacement for the current CDN or as a second CDN next to it. Segments are cached once per region and served from the edge. Pricing runs from $5 to $2.50 per TB, so 100 TB of streaming costs $415 a month.

An OTT platform pays BlazingCDN $415 to stream 100 TB in a month (as of October 2026). The first 5 TB bill at $5 per TB, the next 20 TB at $4.50, and the remaining 75 TB at $4.00. The same rate covers viewers in the US, Europe and Asia.

Streaming bills grow fast, so the tiers keep stepping down. For example, 200 TB costs $765 and 500 TB costs $1,815 a month. At 1,000 TB the total is $3,315. BlazingCDN adds no request fees, which matters for HLS: every few seconds each player requests a new segment and a refreshed playlist. No setup fee and no long-term contract apply. Enterprise terms start from 100 TB a month, and a quote never raises the published price. The 14-day testing period runs on real viewers, with the $25 monthly minimum waived.

BlazingCDN pulls HLS and DASH segments from your packager once per region, caches them on NVMe SSD edge servers, and serves every later viewer from the edge. Across the network, the average cache hit ratio is 96%+.

Playlists and segments get different cache rules. Manifests change constantly, so they use short TTLs. Segments never change after encoding, so they use long TTLs and stay cached for every rendition in the bitrate ladder. Supported formats include HLS with M3U8 playlists, LL-HLS with partial segments, DASH with adaptive bitrate, HDS and Microsoft Smooth Streaming. LL-HLS keeps viewers in the 2 to 4 second range, where standard HLS often runs 20 to 40 seconds behind. Web players, iOS, Android, Apple TV, Roku and Android TV all work with your own hostname and certificate. For example, a new episode released at 8 pm is fetched from origin once per region, then served from cache.

No, BlazingCDN does not transcode, re-package or generate manifests. The service is a delivery layer for streams you have already encoded, so nothing on the CDN side can break your renditions.

You bring a media server that produces HLS or DASH output. Wowza Streaming Engine, NGINX RTMP and FFmpeg all work, as do other packagers with standard output. Encryption also stays with you: DRM-encrypted segments pass through the CDN while the keys remain yours. BlazingCDN is a good fit for platforms that already run an encoding workflow and want steadier, lower-cost delivery. A team without an encoder needs a separate transcoding service first. For example, a broadcaster can keep its FFmpeg ladder at 1080p, 720p and 480p and point a BlazingCDN zone at the packager output. Delivery then costs from $5 per TB down to $2.50 per TB (as of October 2026), with no request fees.

Yes, BlazingCDN can run next to your current video CDN behind DNS with a weighted traffic split, so a migration never has to be all or nothing. Many OTT teams start with one region or one channel.

The usual path takes a few steps. Onboarding with an engineer takes about one hour. Point a zone at your packager output and test on a temporary hostname in your own player. Then send a share of viewers to BlazingCDN, for example 10% of European traffic, and compare startup time, rebuffering and cost against the incumbent. The 14-day testing period runs on real production traffic, with the $25 monthly minimum waived (as of October 2026). A KYC check is required before production traffic. Your current CDN stays live the whole time, and the DNS weight can be moved back at any point. An engineer replies within 3 business hours, so problems go to a person, not a ticket queue.

BlazingCDN protects OTT streams with expiring signed URLs, hotlink protection, IP whitelisting, geofencing and enforced HTTPS on every zone. DRM-encrypted segments are delivered as is, and the decryption keys stay with you.

Signed URLs are the main control. Each playlist or segment link carries a signature and an expiry time, so a copied link stops working after the window closes. For example, a 3-hour signature covers a feature film plus a pause, and then the URL no longer plays. Geofencing limits playback to the countries in your license, and IP whitelisting restricts an origin or a partner feed to known addresses. Hotlink protection blocks other sites from embedding your stream. CORS is configured per zone, and each zone can use your own hostname and SSL certificate. Signed URLs, geofencing and hotlink protection are included in the per-TB price, from $5 per TB down to $2.50 per TB (as of October 2026).