Skip to content
Media & Content Delivery

Content Delivery Network (CDN)

Video streaming, gaming downloads and web acceleration from 40+ edge PoPs on Dollu’s own backbone - with origin shield, TLS at the edge, integrated WAF and DDoS protection, real-time analytics and multi-CDN support.

Content Delivery Network (CDN) - Dollu
  • 40+

    Edge PoPs

  • 1.4 Tbps

    Backbone capacity

  • 95%+

    Typical cache-hit ratio

Overview

What is Content Delivery Network (CDN)?

Dollu CDN caches and delivers your content from more than 40 edge points of presence located inside major internet exchanges and Tier-1 carrier hubs across Europe, North America, the Middle East, India and Asia-Pacific. Because the edges are connected over our own 1.4 Tbps backbone rather than the public internet, cache fills and origin traffic take predictable, low-latency paths, and viewers, players and users get content from a node a few milliseconds away rather than from the other side of the world.

The platform is optimised for the workloads that dominate traffic. For video, we support HLS, DASH and CMAF adaptive bitrate streaming, low-latency HLS and DASH, chunked transfer, byte-range requests, token authentication, geo and referrer restrictions and DRM passthrough. For gaming and software, large-file delivery with prefetch, segmented downloads and burst capacity absorbs launch-day peaks. For web and APIs, dynamic acceleration, HTTP/2 and HTTP/3, Brotli compression, image optimisation and edge rules keep sites and applications fast.

Origin protection is built in. An origin shield layer collapses requests from many edges into a single fetch, cache-hit ratios above 95 percent are typical for video and download workloads, and cache keys, TTLs, purge and prefetch are all controllable through the portal and API. TLS certificates are issued and renewed automatically at the edge, and our WAF and DDoS mitigation can be enabled in front of the CDN so that application-layer attacks and volumetric floods are absorbed before they reach your origin.

You are never locked in. Real-time analytics show requests, bandwidth, cache efficiency, error rates and viewer geography with per-second granularity, and raw logs stream to your S3-compatible storage or SIEM. The CDN plays well with a multi-CDN strategy - DNS or client-side switching based on performance - and our team is happy to be the primary provider in some regions and the secondary in others. Pricing is per gigabyte delivered with regional tiers and committed-volume discounts.

Why Dollu

Why choose Dollu for cdn.

The advantages of buying from a carrier that owns its network, interconnects and operations - rather than a reseller.

  • Faster start-up, fewer rebuffers

    Edges close to viewers on a private backbone cut time-to-first-byte and keep adaptive bitrate ladders climbing rather than dropping.

  • Origins that stay calm on launch day

    Origin shield and high cache-hit ratios mean a game patch or live final drives edge traffic, not origin bills.

  • Security at the same edge

    WAF, bot management and DDoS mitigation share the PoPs that deliver your content, so protection adds no extra hop.

  • Numbers you can act on

    Real-time dashboards and log streaming show exactly which regions, assets and devices are struggling.

  • Freedom to mix providers

    Standard configuration, log formats and purge APIs make Dollu straightforward to run alongside another CDN.

Capabilities

Capabilities in detail.

Everything included with Content Delivery Network (CDN) - the platform features, options and controls you get from day one.

  1. 01

    Global edge footprint

    40+ PoPs at major IXPs and carrier hubs across Europe, North America, the Middle East, India and APAC, interconnected on Dollu’s backbone with anycast routing and health-based traffic steering.

  2. 02

    Video streaming delivery

    HLS, DASH and CMAF ABR delivery, LL-HLS and LL-DASH, chunked transfer, byte-range caching, manifest manipulation, token authentication, geo/referrer/IP restrictions and DRM licence passthrough.

  3. 03

    Large-file and game delivery

    Segmented downloads, prefetch and pre-warm APIs, resumable transfers, launcher-friendly headers and burst capacity for patch days and title launches.

  4. 04

    Web and API acceleration

    HTTP/2 and HTTP/3 (QUIC), Brotli and gzip, TLS 1.3, dynamic content routing, edge rules for redirects, headers and rewrites, image optimisation and WebSocket support.

  5. 05

    Origin shield and caching control

    Regional shield tier, configurable cache keys and TTLs, stale-while-revalidate, instant and wildcard purge, prefetch API, and multi-origin failover with health checks.

  6. 06

    Security integration

    Automatic TLS certificate management, WAF with managed and custom rules, bot management, rate limiting and always-on DDoS mitigation at network and application layers.

  7. 07

    Real-time analytics and logs

    Per-second dashboards for traffic, cache efficiency, status codes and geography; raw log streaming to S3-compatible storage, Kafka or your SIEM; alerts on error-rate and origin-health thresholds.

  8. 08

    API and multi-CDN support

    Full REST API and Terraform provider for configuration and purge; standard log formats; DNS and client-side switching guidance; peering with other CDNs for hybrid delivery.

How it works

How it works.

From first conversation to live traffic - a tracked, engineer-led onboarding with a named owner at every step.

  1. Step 01

    Configure

    Create a distribution in the portal or via API, point it at your origin or storage and choose caching, security and streaming options.

  2. Step 02

    Test

    Validate delivery from our test PoPs, check cache behaviour and headers, and run load tests against the staging hostname.

  3. Step 03

    Cut over

    Update DNS or your multi-CDN switch to send traffic; TLS certificates and origin shield are live from the first request.

  4. Step 04

    Optimise

    Use analytics to tune TTLs, purge strategy and regional weighting; your account manager reviews performance and cost each month.

Use cases

Who uses this and why.

Typical deployments across carriers, enterprises, platforms and contact centres.

  • OTT and live streaming platforms

    Deliver live and on-demand video to millions of concurrent viewers with low start-up times and steady adaptive bitrate quality.

  • Game publishers

    Distribute launches, patches and in-game assets with burst capacity and prefetch so day-one downloads do not saturate your origin.

  • Broadcasters going digital

    Extend linear channels to apps and web with CDN delivery integrated into the same media transport network.

  • E-commerce and media sites

    Accelerate pages, images and APIs for shoppers across regions, protected by WAF and bot management.

  • E-learning and enterprise video

    Serve lecture video, software downloads and portals to global audiences with token-protected access.

Specifications

Technical & commercial specifications.

Key parameters at a glance. Ask us for the full service description and SLA document.

Footprint40+ edge PoPs; Europe, North America, Middle East, India, APAC
Backbone1.4 Tbps private core between edges and origins
ProtocolsHTTP/1.1, HTTP/2, HTTP/3 (QUIC), TLS 1.2/1.3, WebSocket
StreamingHLS, DASH, CMAF, LL-HLS, LL-DASH; token auth; DRM passthrough
CachingOrigin shield, custom cache keys, TTL rules, instant purge, prefetch
SecurityAutomatic TLS, WAF, bot management, rate limiting, DDoS mitigation
AnalyticsReal-time dashboards; raw logs to S3-compatible storage, Kafka, SIEM
ManagementPortal, REST API, Terraform provider, webhooks
PricingPer GB delivered with regional tiers; committed-volume discounts
Pricing model

How Media & CDN is priced.

CDN and media delivery are priced on delivered traffic - per GB or committed Mbps; contribution circuits and live events per event or per month; processing per output minute.

We publish the model, not a public rate card - actual rates depend on destination, route class, volume and regulatory cost. See how every Dollu service is priced.

Per GB or per Mbps · per event
  • CDN per GB delivered or committed Mbps at the 95th percentile
  • Contribution circuits per event or monthly
  • Media processing per output minute
  • Committed-traffic discounts
Billing
Monthly in arrears on delivered traffic; events invoiced per booking
Commitment
None on usage; committed traffic on 12–36 month terms for the best rates
Talk to salesActual rates within one business day.
FAQ

CDN - your questions answered.

The questions customers and carriers ask us most often before they interconnect. If yours is not here, our team answers within one business day.

Still have a question?

Ask our solutions team

A designated shield PoP sits between the edges and your origin. When many edges miss on the same object, only the shield fetches from origin and then serves the edges, collapsing thousands of requests into one. This keeps origin egress low, protects it during spikes and raises the overall cache-hit ratio.

Let’s talk

Try the CDN with your traffic.

Get a trial distribution with 1 TB of delivery and see the cache-hit and latency numbers from your own origin.

Abstract globe with connected network lines