Nimbus
Deploy a server

SHEET 003 · NETWORK SURVEY · AS212345 · 41 SITES · 860 PEERING SESSIONS

The network

Forty-one sites, one autonomous system, one control plane. We publish the transit mix, the regional build-out and every DDoS number worth knowing — the network is the product, so it gets a spec sheet like the servers do.

AS212345our own autonomous system
18.5Tbit/sedge capacity
860peering sessions, IXes and direct
41sites in 32 countries

01 — Nearest to you

Frankfurt, usually

If you are reading this from Europe, Frankfurt is almost always the lowest-latency site — DE-CIX is next door and most of the continent is one or two hops away. For everyone else, the map above lists the next candidate.

Frankfurt — 1 ms median RTTDüsseldorf — 2 ms median RTTAmsterdam — 2 ms median RTTLondon — 2 ms median RTTParis — 3 ms median RTTZurich — 3 ms median RTTMadrid — 3 ms median RTTMilan — 3 ms median RTTStockholm — 3 ms median RTTWarsaw — 3 ms median RTTVienna — 3 ms median RTTDublin — 3 ms median RTTLisbon — 3 ms median RTTHelsinki — 3 ms median RTTPrague — 3 ms median RTTCopenhagen — 3 ms median RTTNew York — 1 ms median RTTAshburn — 1 ms median RTTChicago — 3 ms median RTTDallas — 3 ms median RTTMiami — 4 ms median RTTSeattle — 3 ms median RTTLos Angeles — 3 ms median RTTToronto — 3 ms median RTTMexico City — 5 ms median RTTSão Paulo — 5 ms median RTTSantiago — 6 ms median RTTSeoul — 2 ms median RTTTokyo — 3 ms median RTTOsaka — 4 ms median RTTSingapore — 2 ms median RTTHong Kong — 3 ms median RTTTaipei — 4 ms median RTTMumbai — 4 ms median RTTBangkok — 5 ms median RTTJakarta — 5 ms median RTTSydney — 3 ms median RTTMelbourne — 4 ms median RTTDubai — 4 ms median RTTIstanbul — 3 ms median RTTRiyadh — 5 ms median RTTPL-004 · NETWORK SURVEY · EQUIRECTANGULAR · 41 NODES

Frankfurt · FRA4

FRA4 · Tier IV

Facility
Kleyerstraße campus · Tier IV
Live since
2023 — our first site
Median RTT, in-site
2 ms
Capacity
1.6 Tbit/s
Peering
DE-CIX Frankfurt
Test IP
185.42.16.10

Median RTT from the region

Düsseldorf4 ms
Zurich6 ms
Paris6 ms
Amsterdam7 ms
London8 ms
Warsaw10 ms

02 — Transit mix

No single carrier can take us down

Six upstreams, none above 24%. The blend is re-balanced every quarter, and the numbers below are the current ones — a transit change is an operations event, not a secret.

01Arelion

24%

02Cogent

21%

03Lumen

19%

04GTT

14%

05NTT

12%

06Regional IX + direct

10%

Every site keeps at least two carriers plus its local IX. The worst single upstream failure drops about a fifth of a region's transit, and BGP does the rest within seconds.

03 — Regional build-out

18.5 Tbit/s, roughly where the continents need it

Regional numbers are egress capacity — transit plus IX — at the sites in that region. Per-site figures live on each site page; these are the totals.

Europe

8.1 Tbit/s

16 sites · Frankfurt, Düsseldorf, Amsterdam, London, Paris, Zurich, Madrid, Milan, Stockholm, Warsaw, Vienna, Dublin, Lisbon, Helsinki, Prague, Copenhagen

Americas

5.6 Tbit/s

11 sites · New York, Ashburn, Chicago, Dallas, Miami, Seattle, Los Angeles, Toronto, Mexico City, São Paulo, Santiago

Asia-Pacific

3.9 Tbit/s

11 sites · Seoul, Tokyo, Osaka, Singapore, Hong Kong, Taipei, Mumbai, Bangkok, Jakarta, Sydney, Melbourne

Middle East

0.7 Tbit/s

3 sites · Dubai, Istanbul, Riyadh

Europe runs the deepest build-out because that is where the fleet started. Asia-Pacific carries the most traffic per terabit — Seoul, Tokyo and Singapore are the busiest sites per rack on the network.

04 — DDoS

Always on. Included. No phone call required.

Volumetric filtering — L3/L4, up to 5 Tbit/s of scrubbing — runs on every plan at every site. There is no 'protection tier' on the invoice and no button to remember to press.

3.1smedian time to engage scrubbing
1.2Tbit/slargest attack absorbed
5Tbit/sscrubbing capacity
  • Engagement is automatic and per-IP; legitimate traffic is never dropped while we figure out who is who.
  • The 1.2 Tbit/s attack hit a Frankfurt tenant in January 2026. Scrubbing engaged in 3.1 seconds; the tenant saw latency, not downtime.
  • Advanced protection (€3.90/month) adds L7 scrubbing and custom rules for HTTP(S) services that volumetric filtering cannot judge.

05 — Host hardware

The metal behind the network

Every site runs the same host build, so a benchmark in Frankfurt is a benchmark in São Paulo. Sheet revision D since the Genoa refresh.

CPU

AMD EPYC 9354P · 3.80 GHz boost

Memory

384 GB DDR5-4800 ECC per host

Storage

Samsung PM9A3 Gen4 NVMe, RAID-10

Host network

2 × 25 GbE LACP to separate leaves

Edge uplink

2 × 400 GbE per site, A+B paths

Power

A+B feeds, 72 h diesel autonomy

Hypervisor

KVM on Linux 6.12 LTS

Oversubscription

3:1 fair-share · 1:1 dedicated

Same network, every plan, every site

The Nano pays for the same edge routers as the Monolith. That is a policy, not a coincidence — and it is why the price is the only number that changes between plans.

41sites
32countries
860peering sessions
18.5Tbit/sedge capacity