Where the bytes actually live
Three anycast sites carry the fabric today. Each one terminates TLS locally, keeps a memory tier plus an NVMe tier, and peers directly with the transit mix listed below.
| Code | City | Country | Capacity | Median RTT | Status |
|---|---|---|---|---|---|
| Loading edge inventory… | |||||
Anycast routing
A single address is announced from every site. BGP picks the closest healthy PoP, and drains are a routing change rather than a DNS change - no TTL to wait out.
Tiered cache
Edge RAM absorbs the hot set. Misses fall through to a local NVMe tier, then to the shield PoP, and only then to your origin.
Transit & peering
Blended transit at each site with direct sessions at LINX and AMS-IX, so UK and Benelux eyeball traffic stays one AS hop away.
Per-site profile
| Site | Facility type | Memory tier | NVMe tier | Uplink | Role |
|---|---|---|---|---|---|
| LON1 | Carrier-neutral colo | 192 GB | 7.6 TB | 2 × 25G | Shield + edge |
| MAN1 | Carrier-neutral colo | 96 GB | 3.8 TB | 2 × 10G | Edge |
| AMS1 | Carrier-neutral colo | 128 GB | 7.6 TB | 2 × 25G | Edge + overflow |
Capacity figures describe provisioned hardware per site, not a contractual commitment.
Health checks
Every site answers an unauthenticated liveness probe. Point your own monitoring at it if you want an independent signal.
$ curl -s https://cdnuk.vlone.cloud/api/v1/health { "status": "ok", "pop": "LON1", "uptime_s": 918442 }