London
LON1Primary core, split across two halls in separate buildings. The original rack from 2017 is still here, now surrounded by rather better hardware.
- Power
- N+1, A+B feeds
- Cooling
- N+1
- Transit
- 2 × 10G
- Peering
- LINX + 3 private
- Floor space
- 340 m²
Infrastructure
Our own routing, our own addressing plan, and enough redundancy to lose a site without losing the service. Here is what sits behind the status page.
Core sites
Compute and storage run in three facilities we operate ourselves. Each has independent power, cooling and transit paths before a customer workload is allowed through the door.
Primary core, split across two halls in separate buildings. The original rack from 2017 is still here, now surrounded by rather better hardware.
European peering hub with direct routes to London and Frankfurt. Two new racks came online here in October 2026.
EU core for data-residency workloads, with separate power paths and a strictly separated management network.
Network
We announce our own prefixes, filter with RPKI and keep a live map of every circuit. Traffic takes the path with the best latency, not the cheapest one.
DDoS scrubbing is always on, not an add-on. Volumetric traffic is redirected to a scrubbing cluster and analysed; legitimate flows come back through a clean path. We publish a monthly summary of what we saw.
Median latency, sampled every 60 seconds
Routing changes are logged and reviewed. Customer-visible changes are announced on the status page.
Locations
Three core sites host compute and storage. Nine edge PoPs extend private network attachment and regional ingress, without pretending to be full facilities.
| Location | Code | Route from London | Role |
|---|---|---|---|
| Manchester, United Kingdom | MAN1 | 5 ms | Northern ingress |
| Dublin, Ireland | DUB1 | 9 ms | EU west ingress |
| Paris, France | PAR1 | 8 ms | Peering |
| Amsterdam, Netherlands | AMS2 | 7 ms | Core site |
| Frankfurt, Germany | FRA1 | 11 ms | Core site |
| Zurich, Switzerland | ZRH1 | 15 ms | DR capacity |
| Milan, Italy | MXP1 | 19 ms | Southern peering |
| Madrid, Spain | MAD1 | 24 ms | Iberian ingress |
| Copenhagen, Denmark | CPH1 | 17 ms | Nordic peering |
| Stockholm, Sweden | ARN1 | 20 ms | Nordic ingress |
| Vienna, Austria | VIE1 | 21 ms | Central Europe ingress |
| London, United Kingdom | LON1 | — | Core site |
Latencies are median round-trip times from LON1, measured in September 2026. Edge PoPs are network attachment points; compute and storage live in the core sites.
The physical layer
Cloud pages tend to skip the doors, cables and diesel. We think those are the interesting parts.
Biometric entry, mantraps and 24/7 staff. Cabinets are individually locked, CCTV is retained for 90 days, and every visit is logged.
N+1 UPS and generators with 48 hours of fuel. Hot-aisle containment, raised floors and a design PUE of 1.25 across the core estate.
Renewable electricity across all core sites, refrigerant leak monitoring and an annual waste and water review. Boring, measurable, audited.
Change management
Customer-impacting work happens Tuesday to Thursday, between 01:00 and 04:00 UTC. We publish the window at least five working days ahead and keep the previous configuration on the shelf until the new one has survived a full business day.
Emergency security work follows a shorter path, but not a quieter one: the status page still gets an entry, and the incident review still gets written.
Expected impact: brief failover, no customer action required.
Expected impact: none; redundancy reduced during the window.
Full history and updates: System status.
We will send the version with real latencies and the mistakes left in. Useful for architecture reviews, due diligence, or deciding whether we are a fit.