Edge stations
Debian on bare metal, with the kernel network stack tuned per site for the traffic that site actually sees. Nothing else shares the forwarding path.
Sheet 1 · North Sea & Baltic approaches · Edition 2026.1
A network you can read off a chart.
Sixteen edge stations around the North Sea and the Baltic. One anycast address puts every European visitor inside ten milliseconds of a warm cache — and we publish the position, capacity and measured latency of every station on it.
Backbone route, private fibre
Route continued off this sheet
Edge station · figure below is p50
Soundings
The numbers we are willing to print.
Measured from probes across the ten countries we serve, aggregated over a rolling twenty-four hours. Where a figure moves, this sheet is corrected.
- Median latency
- 6ms
- 95th percentile
- 18ms
- Cache hit ratio
- 97.3%
- Edge stations
- 16
- Egress capacity
- 11.2Tbit/s
Passage plan
How a request travels.
Four hops from a browser in Tampere to your origin — and on most days it stops at the second one.
Hop 00
Anycast DNSOne address, every station
The same address is announced from all sixteen sites. The visitor's resolver returns the station nearest them, not the one nearest you. No redirect, no second lookup — 0 ms added.
Hop 01
LandfallEdge station
TLS terminates here on a session ticket the visitor already holds. On a cache hit — 97 of 100 requests — the answer never leaves the building, and the passage ends at this hop.
Hop 02
BackbonePrivate transit
A miss travels our own fibre between stations rather than the open internet. Fewer hops, no congested exchange in the middle, and a path we can see end to end when you ask us why something was slow.
Hop 03
OriginYour server
Reached once. The object is then held at every station that asked for it, so the next visitor in Riga is served from Riga.
Legend
What each symbol stands for.
Four things every station does, described the way we would describe them to an engineer who has to operate around them.
Certificates, kept current
SAN certificates are issued once your domain validates and renewed without anyone watching a calendar. Upload your own, or pin a stricter TLS profile, if policy says so.
Scrubbing at the shore
Volumetric floods are absorbed at the station that receives them, so they never reach your origin or the rest of the network. Layer 7 filtering runs inline — real requests do not queue behind an attack.
Origin balance
Health checks and geographic weighting spread requests across your origins, and pull a failing one out of rotation before your users are the ones who find it.
Register of stations
Every position, in full.
Two stations lie south of this sheet and are shown on the chart only as a route leaving the frame. Their figures are printed here all the same.
| Station | Code | Position | p50 | Egress |
|---|---|---|---|---|
| Amsterdam | AMS | 52.37°N 4.90°E | 3 ms | 1600 Gbit/s |
| London | LHR | 51.51°N 0.13°W | 4 ms | 1600 Gbit/s |
| Frankfurt | FRA | 50.11°N 8.68°E | 4 ms | 1600 Gbit/s |
| Copenhagen | CPH | 55.68°N 12.57°E | 5 ms | 800 Gbit/s |
| Paris | CDG | 48.86°N 2.35°E | 5 ms | 800 Gbit/s |
| Oslo | OSL | 59.91°N 10.75°E | 6 ms | 800 Gbit/s |
| Stockholm | ARN | 59.33°N 18.07°E | 7 ms | 800 Gbit/s |
| Dublin | DUB | 53.35°N 6.26°W | 7 ms | 400 Gbit/s |
| Prague | PRG | 50.08°N 14.42°E | 7 ms | 400 Gbit/s |
| Tallinn | TLL | 59.44°N 24.75°E | 8 ms | 400 Gbit/s |
| Vienna | VIE | 48.21°N 16.37°E | 8 ms | 400 Gbit/s |
| Helsinki | HEL | 60.17°N 24.94°E | 9 ms | 400 Gbit/s |
| Riga | RIX | 56.95°N 24.11°E | 9 ms | 400 Gbit/s |
| Warsaw | WAW | 52.23°N 21.01°E | 9 ms | 400 Gbit/s |
| Madrid · off sheet | MAD | 40.42°N 3.70°W | 14 ms | 400 Gbit/s |
| Rome · off sheet | FCO | 41.90°N 12.50°E | 15 ms | 400 Gbit/s |
Come alongside
Point a CNAME at us and watch the first cache fill.
Fourteen days, no card, no call. If the figures on this chart do not hold for your traffic, you will know inside an afternoon.