Overview

Leaseweb is an infrastructure provider founded in 1997 and headquartered in Amsterdam. Its managed Multi-CDN service places several third-party CDN networks behind a single configuration and traffic-steering layer. Leaseweb publishes separate Volume and Premium service tiers.

Network & Architecture

Leaseweb’s Multi-CDN service routes requests across multiple third-party CDNs. In correspondence dated 2026-08-10, Leaseweb identified CacheFly, CDNetworks, Fastly, and Gcore as examples of current providers and stated that Edgio is not part of the service. Leaseweb does not publish a provider-by-provider point-of-presence list; its product page states that the combined service reaches more than 400 PoPs. Volume routing considers measured latency and cost, while Premium routing considers latency and throughput. Optional Leaseweb shield nodes in Amsterdam and Washington, D.C. add an intermediate cache between the delivery CDN and the origin.

Features

FeatureSupported
waf
bot_mitigation
ddosPartial
rate_limit
http3_quic
tls13
tiered_cache
origin_shield
instant_purge
stale_while_revalidate
stale_if_error
image_optimization
video_vod
video_live
drm
hls_dash_packaging
websockets
signed_urls
edge_compute
functions
kv_storage
api_first
realtime_logs
log_push
terraform

Legend: ✓ = Supported, Partial = Partially supported, ✗ = Not supported

Pricing

Leaseweb publishes committed-volume pricing for two annual-contract tiers: Volume and Premium. At 50 TB, the listed rates are EUR 6.60 per TB and EUR 8.50 per TB, respectively. At 3 PB or more, the rates are EUR 4.20 per TB and EUR 5.80 per TB. The minimum commitment is EUR 150 per month. The pricing page states that on-demand service is planned but is not currently available. Prices were checked on 2026-08-10.

Integrations & DevEx

Distributions are configured through Leaseweb’s customer portal and CDN API. The public documentation describes unified reporting, real-time analytics, cache invalidation, and log delivery. Leaseweb publishes a Terraform provider for other products, but no Multi-CDN resource is documented; Terraform is therefore not listed as a Multi-CDN integration.

When it fits

  • Organizations that want one contract and control plane for traffic delivered through several CDN providers.
  • High-volume delivery where an annual traffic commitment is acceptable.
  • Architectures that benefit from optional origin shielding and provider switching.

When it doesn’t

  • Deployments that require a usage-based plan without an annual commitment.
  • Workloads that depend on built-in image optimization.
  • Requirements that need a fully documented DDoS scope or a fixed underlying CDN in every region.