← Terug naar Gids
Logo: Leaseweb CDN

Leaseweb CDN

Dutch Multi-CDN that steers traffic across four partner networks with NS1 Pulsar, plus included origin shields in Amsterdam and Washington, D.C. Sold under local Leaseweb sales entities.

cdnmulti-cdncontent-deliveryiaasnetherlandsgdprorigin-shield
Bezoek WebsiteAsk an EU migration specialistFeedback & correcties

Leaseweb CDN, sold as Leaseweb Multi-CDN, is the content delivery product of the Amsterdam-based Leaseweb group. You do not contract a single global brand company. You sign a B2B sales contract with a local Leaseweb sales entity. For the Netherlands that is Leaseweb Netherlands B.V. (Chamber of Commerce 30141839) at Hessenbergweg 95, 1101 CX Amsterdam. The public website is operated by Leaseweb Global B.V. (KvK 60593652) at the same address. Leaseweb Global B.V. states it does not itself conclude customer sales contracts.

The product is a managed multi-CDN, not a Leaseweb-only edge. Leaseweb says it combines four third-party CDN providers and more than 400 points of presence, then steers each request with NS1 Pulsar real-user metrics. Volume tier picks the cheapest partner at similar latency. Premium tier picks for latency and quality of experience. HTTP/2 is on by default across those partners.

The practical differentiator for European teams is one Dutch (or other local) contract, an included origin shield layer with nodes in Amsterdam and Washington, D.C., and a Customer Portal plus REST API. The tradeoff is explicit: edge features are limited to the common subset of unnamed partner networks, and request metadata is processed by those partners plus NS1, not only by Leaseweb.

Dutch sales entityMulti-CDN (4 partners)Origin shield (AMS + WDC)Portal + REST APIISO 27001 (company, claimed)

Shortlist when you want a Dutch (or other local Leaseweb) B2B contract that fronts four partner CDNs with NS1 Pulsar steering and included Amsterdam or Washington, D.C. origin shields. Skip when you need EU-only processors, named partner inventory up front, Cloudflare-class WAF or Workers, or signed URLs without a shield hop. Consider Cloudflare for a single global edge platform, or OVHcloud if you want a French-operated CDN attached to EU datacentres.

Key capabilities

Leaseweb sells a managed mix of four unnamed third-party CDNs and claims more than 400 points of presence. One distribution CNAME (examples in docs: di-xxxx.leasewebultracdn.com, *.pr.lswcdn.net, *.vo.lswcdn.net) fronts the mix. Features are limited to the common subset all four support. You cannot pin a user to a specific PoP.

Leaseweb says it connects partner performance to NS1 Pulsar real-user metrics. Volume tier chooses the most cost-effective partner at similar latency. Premium tier chooses on latency and quality of experience. Regional DNS logic can still send a whole region to a single partner when that path is faster.

Shield CDN distributions add a Leaseweb cache layer so partner edges do not all hit origin. Marketing states shields are included on Volume and Premium and sit in Amsterdam and Washington, D.C. Shields support multiple path policies, origin groups (up to 10 hosts, round-robin, consistent, sticky, or failover), and tokenized URLs. Wildcard invalidation is not supported on shields. A Multi-CDN invalidation does not clear the shield automatically.

Simple origins take a hostname or IP. AWS Signature Version 4 can authenticate S3-compatible buckets (Leaseweb Object Storage or AWS). Advanced origins (custom ports, subdirectory) work only behind shields and do not support Sig V4. Authenticated object storage cannot join an origin group. Each origin is HTTP or HTTPS exclusively, not mixed.

Distributions, origins, certificates, and invalidations are managed in the Leaseweb Customer Portal (CDN menu, active contract required) or via the documented REST API on developer.leaseweb.com. Raw logs from all partners can be normalized to JSON and uploaded as .gz files to a customer S3 bucket. Leaseweb states logs are informational only and may be delayed or incomplete versus billing records.

Web, live, and VoD templates set methods, TTL, compression, and stale-serve defaults. Operators can force CDN-controlled or origin-controlled cache, passthrough or static headers, geo blocking, IP-subnet blocking, and referrer allowlists. HTTP/2 is default on all partners. Gzip delivery compression applies only to files up to 20 MB. CORS Access-Control-Allow-Origin is stripped unless you passthrough or set it.

In één oogopslag

HQ
Amsterdam, Netherlands
Website operator
Leaseweb Global B.V. (KvK 60593652)
Typical NL contract
Leaseweb Netherlands B.V. (KvK 30141839)
Founded
1997 (vendor, 2023 press)
Product type
Managed Multi-CDN (not self-hosted, not open source)
Edge
Four unnamed partner CDNs, 400+ PoPs (vendor claim)
Shield locations
Amsterdam and Washington, D.C.
Steering
NS1 Pulsar (Volume: cost; Premium: QoE)
Commercial model
B2B traffic tiers, annual commitment

Best fit when

  • Teams already on Leaseweb dedicated servers, object storage, or private cloud who want delivery on the same invoice
  • Media, ads, SaaS, or gaming publishers who want multi-CDN failover without four vendor contracts
  • Origins that can sit behind an Amsterdam or Washington, D.C. shield and pull over HTTP or HTTPS (or S3 with Sig V4)
  • Operators who will live with partner-subset features (HTTP/2, geo/IP/referrer ACLs, portal and REST API) rather than Workers-style compute
  • Buyers who can accept Volume (cost) versus Premium (QoE) steering instead of pinning a single CDN

Poor fit when

  • Organizations that require an EU-only edge with a public, named subprocessor list (partners are unnamed; WDC shield and NS1 are in path)
  • Sites that need signed URLs, a WAF, bot management, or edge functions on the same product
  • Teams that must purge thousands of URLs per minute or treat invalidation as the publish pipeline
  • Buyers who want a self-serve free tier or an open-source, self-hosted CDN
  • Workloads that need MPEG-DASH Gzip, mixed HTTP and HTTPS to one origin, or per-user PoP selection

Consider instead when

  • When: You need a single global edge with WAF, bot management, Workers, and a self-serve free tier

    Consider: Cloudflare

    US company. Broader edge platform. Different jurisdiction story.

  • When: You want CDN plus compute from one European infrastructure group and can diligence that group's own PoPs

    Consider: OVHcloud

    French operator. Own datacentres. Not a four-provider multi-CDN.

  • When: You mainly need EU origin compute and will add a CDN you can inventory yourself

    Consider: Hetzner or Scaleway

    Neither replaces Multi-CDN. They keep origin in EU facilities you can name.

  • When: You wanted Swiss-branded hosting with optional Cloudflare, not a multi-CDN fabric

    Consider: Swissnode

    Different product class. Optional Cloudflare on web plans.

Jurisdictie & eigendom

Juridische entiteit
Leaseweb Netherlands B.V. (KvK 30141839, Amsterdam). Website: Leaseweb Global B.V. (KvK 60593652). Other local sales entities exist.
VS-moeder / zeggenschap
Geen bekende VS-moeder
CLOUD Act-blootstelling (indicatief)
Medium
Hosting / residentie
Delivery is a mix of four unnamed third-party CDNs (global PoPs). Leaseweb origin shields in Amsterdam and Washington, D.C. Request steering via NS1 Pulsar. Origins may be customer HTTP hosts or S3-compatible buckets (including AWS). Raw logs (including client IP) collected from partners and optionally written to customer S3. No public CDN subprocessor list naming the four partners.

No known US parent. Group includes Leaseweb USA, Inc. (Manassas, VA) and a Washington, D.C. shield. NS1 is a US-group steering/RUM dependency. Partner CDNs are unnamed and almost certainly include non-EU processors. Indicative only, not legal advice.

  • Independent security / no-logs auditNot found
  • ISO 27001Vendor claimed
  • SOC 2 / SOC 3Partial
  • GDPR / EU data protectionVendor claimed
  • +5

Considerations & known limitations

  • HighUnnamed partner CDNs and NS1 in the data path

    Delivery and RUM leave Leaseweb facilities. The four partners are not named on public product or legal pages. NS1 Pulsar steers requests. Treat as a multi-processor design until sales produces a current list and DPA schedule.

  • MediumWashington, D.C. origin shield

    Included shields are in Amsterdam and Washington, D.C. Enabling a shield can place origin-pull traffic in the United States even when the sales entity is Dutch. Live streaming docs also advise against shields for latency reasons.

  • MediumISO / SOC reports do not list CDN

    Published ISO 27001 and SOC 1 service lists omit CDN. SOC 2 is Canada colocation only. Do not assume Multi-CDN inherits those reports without a scoped letter.

  • MediumFeatures limited to partner intersection

    No Multi-CDN URL tokens, no PoP pin, Gzip-only compression with a 20 MB cap, no MPEG-DASH Gzip, mixed origin HTTP/HTTPS unsupported, invalidation rate-limited. SSL and stats propagate on partner clocks.

  • LowRaw logs not billed as complete

    Partner logs shipped to S3 are informational. Leaseweb states they may be late or missing versus invoice counters. Do not use them as a legal completeness record.

Open questions for due diligence

  • What are the current four partner CDN legal names, and can they be listed in the DPA?
  • Can routing be constrained to EU (or named) partners and the Amsterdam shield only?
  • Is Multi-CDN in the current ISO 27001 statement of applicability?
  • Will Leaseweb sign a standalone DPA that covers NS1 Pulsar and each partner?
  • What is the current annual-commitment commercial offer (confirm on the official Multi-CDN page or with sales)?
Request vendor DPA / enterprise contact
Ask an EU migration specialist
Bezoek WebsiteCompare similar toolsView alternativesFeedback & correcties

Veelgestelde Vragen

Not from the public docs. You cannot pin a PoP. Partner CDNs are global, NS1 Pulsar steers on latency or cost, and included origin shields exist in both Amsterdam and Washington, D.C. Geo blocking can deny delivery to listed countries. That is an access control, not a residency guarantee. If EU-only processors are mandatory, ask Leaseweb to name the four partners and whether any EU-only routing SKU exists. If they cannot, this product is a poor fit.

No. The knowledge base states URL protection (URL tokens) is not available on Multi-CDN distributions because it is not in the common feature set of all partner CDNs. Tokenized URLs (simple shared secret or AES/SHA pair, optional client-IP binding) are a Shield distribution feature. Plan an extra shield hop if hotlink protection must be cryptographic rather than referrer-based.

Invalidations are intended for exceptions, not the normal publish path. Multi-CDN allows at most one invalidation request per minute, up to 75 URLs per request (wildcard paths such as /dir/* are supported on Multi-CDN, not on shields). Completion can take minutes because each partner must be notified. If you use a shield origin, invalidate the shield separately. Pending requests can expire and be re-submitted.

Leaseweb claims ISO 27001:2022 via EY CertifyPoint for multiple entities, including Leaseweb Netherlands B.V. The published certified-services list is corporate infrastructure, bare metal, VPS, private cloud, hybrid cloud, colocation, web hosting, and domain names. CDN is not listed. Treat company ISO as a supporting control for the group, then ask for the current statement of applicability and whether Multi-CDN and named partners are in scope.

You contract a local sales entity, not Leaseweb Global B.V. (the website operator). Netherlands customers typically sign with Leaseweb Netherlands B.V. Other listed entities include Leaseweb Deutschland GmbH, Leaseweb UK Ltd., and Leaseweb USA, Inc. A DPA is incorporated as Clause 8 of the local sales terms. Leaseweb says a separate DPA can be issued on request when appropriate for the service. Confirm that the DPA names Multi-CDN partners and NS1.

Neither. There is no public self-host or open-source edge. Access to the CDN portal requires an active B2B contract. Volume and Premium are traffic-based tiers with an annual commitment. On-demand is described as coming soon. Shared TLS certificates only cover Leaseweb CNAME targets, not your own hostname. Custom hostnames need an uploaded SNI certificate.