Content delivery
Ship petabytes without babysitting your origin
Anycast edge with 214 Tbps of installed capacity, tuned for the unglamorous traffic nobody talks about: game patches, OS images, model weights and multi-gigabyte installers.
Platform
Built for the heavy end of the catalogue
Most CDNs are optimised for 40 KB of JSON. We optimised for the 40 GB file that 300,000 people want at the same second.
Large-object pipeline
Objects are sliced into 8 MB chunks and fetched in parallel from the shield tier, so a cold 40 GB file streams at line rate instead of trickling.
How slicing works
Origin shielding
A regional shield collapses concurrent misses into a single origin fetch. Release-day origin load stops scaling with your audience.
Shield topology
Anycast, everywhere
One address, 61 landing sites, BGP steering that reacts to congestion in under 30 seconds without touching DNS.
See the map
Edge rules
Rewrite, sign, throttle and A/B at the edge with a rule engine that deploys globally in about nine seconds.
Rule reference
Signed URLs and tokens
Time-boxed, IP-boxed and geo-boxed links, validated on the edge machine before a single byte leaves the disk.
Token formats
Logs you can actually use
Real-time log delivery to object storage or a socket, with 42 fields per line and no sampling below 10 Gbps.
Log fields
Release day
The stampede test
A 62 GB patch, published at 17:00 UTC, wanted by four million clients in the first hour. This is the traffic curve from a customer's last launch — origin egress stayed flat at 340 Mbps.
- Peak edge egress 71.4 Tbps, sustained for 22 minutes
- Origin fetched the object 61 times in total — once per shield
- No manual pre-warm: the first request in each region pulled the file
- Median completion time for the full download: 4 min 12 s
Traffic, live
Aggregate across all customers. Numbers on this page come from the same telemetry pipeline that produces your invoice.
Where the bytes go
Wire it up in a minute
Point a hostname at the edge, or drive everything through the API.
# purge a path across all 61 PoPs
curl -X POST https://api.master-c1.cdnmedia.download/v3/zones/z_8f21/purge \
-H "Authorization: Bearer $MERIDIAN_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"paths":["/releases/2026.8/client.pkg"],"soft":true}'
# → 202 Accepted, global in ~9sresource "meridian_zone" "releases" {
hostname = "dl.example.com"
origin = "origin.example.internal:8443"
shield = "eu-central"
large_object {
slice_size = "8MB"
prefetch = true
collapse_miss = true
}
}{
"match": "path glob '/releases/*'",
"actions": [
{"set_cache_ttl": "30d"},
{"require_signature": {"algo": "ed25519", "ttl": 900}},
{"rate_limit": {"per_ip_mbps": 400}}
]
}Teams that moved off a general-purpose CDN
“Our patch day used to be an incident with a calendar invite. Now the origin does not even notice.”
“We serve 9 PB a month of model weights. The per-terabyte price stopped being the thing we argue about internally.”
“The log pipeline replaced two internal services. That was worth more than the bandwidth saving.”
Questions we get in the first call
Move a terabyte and see for yourself
The trial includes 5 TB of egress, every feature, and an engineer who will look at your traffic with you.