Leaseweb CDN vs OVHcloud

Four-provider Multi-CDN (400+ PoPs claimed)

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.

NS1 Pulsar Volume and Premium steering

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.

Origin shields in Amsterdam and Washington, D.C.

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.

HTTP, S3, and object-storage origins

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.

Portal, REST API, and raw logs to S3

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.

Cache templates and edge ACLs

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.

Anti-DDoS Protection and Vast Network Capacity

Every OVHcloud service includes unlimited anti-DDoS mitigation, scrubbing attacks across layers 3, 4, and 7 without downtime fees. The global network exceeds 100 Tbit/s, ensuring low latency and high throughput. No charges apply to outbound traffic, unlike some rivals, which helps control costs for data-intensive apps like streaming or backups.

Sustainability with Low PUE and Resource Reuse

OVHcloud reports a power usage effectiveness (PUE) of 1.28 across its facilities, beating industry averages. It uses 7 times less water than peers and runs on 100% low-carbon energy sources. Servers get repurposed for secondary uses before recycling, targeting zero landfill waste by 2025. This approach reduces operational costs passed to customers.

OpenStack Public Cloud and Reversibility

Built on OpenStack, the public cloud supports pay-as-you-go pricing with API access for automation. Private cloud options avoid lock-in through data export tools and standard formats. Customers retain full control, with no data mining for ads. Features like vRack private networking connect services seamlessly across regions.