VLONEEdge
LON1 · MAN1 · AMS1 edge fabric online

Edge delivery, anchored in the UK.

cdnuk is the public edge endpoint of the VLONE delivery network. Terminate TLS close to your users, serve cached objects from memory, and purge the whole fabric in under a second - with a control API that behaves like infrastructure, not a dashboard.

purge.sh
# point an origin at the edge
$ curl -X POST https://cdnuk.vlone.cloud/api/v1/zones \
    -H "authorization: Bearer $VLONE_TOKEN" \
    -d '{"origin":"origin.example.com","tls":"strict"}'

{ "zone": "z_7fd21a", "status": "active", "pops": 3 }

# invalidate everything, everywhere
$ vlone purge --zone z_7fd21a --all
purged 1 zone across 3 pops in 412ms
-Requests served
-Egress right now
-Cache hit ratio
-Edge locations

sampled from the live fabric · updated -

Platform

Built for people who read RFCs for fun

Every layer is inspectable, scriptable and boring in the way that infrastructure should be.

Memory-first caching

Hot objects are served from RAM on the edge node itself. Tiered fallback hits an NVMe layer before it ever touches your origin.

TLS 1.3 everywhere

Modern ciphers only, OCSP stapling, HTTP/2 and automatic certificate issuance and renewal for every hostname you attach.

Sub-second purge

Purge by URL, prefix, surrogate key or the entire zone. Invalidation propagates across the fabric before your deploy script finishes.

Edge rules

Rewrite paths, set headers, gate by country or method, and shape cache keys with a small, declarative rule language.

Real telemetry

Per-second counters, cache ratio by path, and origin latency percentiles - exposed as JSON and as a Prometheus scrape target.

Origin shielding

A single designated PoP fronts your origin, collapsing concurrent misses into one upstream request instead of a stampede.

Traffic

Last 24 hours across the fabric

Aggregate egress sampled every fifteen minutes from all active edge locations. The same series is available through /api/v1/stats if you would rather graph it yourself.

View raw JSON
-24hnow
Edge locations

A small network, deliberately

We run fewer, larger sites instead of hundreds of thin ones - more cache per location means a higher hit ratio and far less origin traffic.

CodeCityCountryCapacityMedian RTTStatus
Loading edge inventory…

- active locations · see network details

Put an origin behind the edge

Create a zone, point a CNAME, and the fabric starts caching. No agents, no sidecars.

Quickstart See pricing