NulNet
All twenty-one sites, card by card
Each card is one facility: campus, uplink, jurisdiction, and the premium that applies — or the base list where none does.
Südwestlich der Hauptstadt, Geothermie-Gürtel. Kältekreis zuerst; Diesel-Backup. FICIX in der Halle.
Südost-Metro, Science-Park-Korridor nahe AMS-IX. Dual utility, 2N, Meet-me-dicht.
Westlicher Bukarest-Ring. Dualer Stadtnetz-Feed plus Genset. BIX Meet-me; EU-IP ohne AMS-IX als einzigen Hop.
Nördlich von Zürich, Glatt-Korridor. Hydro plus Dual-Feed. SwissIX in der Halle, DE-CIX kurze Faser.
Sao-Paulo-Metro-Carrier-Gürtel nahe IX.br. Dual-Feed, bemannte Cages. Straßenadresse unveröffentlicht.
Ashburn-Korridor — US-East-Colo-Dichte. Dual utility, Meet-me-reich. Straßenadresse unveröffentlicht.
Hongkong Carrier-Hotel-Gürtel mit HKIX. Dual-Feed, Badge-and-Cage. Straßenadresse unveröffentlicht.
Shanghai-Metro-Campus für Mainland-Apps. Dual-Feed. Straßenadresse unveröffentlicht.
Tokio Inzai / Metro-Carrier-Gürtel. JPIX, Dual-Feed, bemannte Cages. Straßenadresse unveröffentlicht.
Riga-Metro-Carrier-Gürtel. Dual-Feed, bemannte Cages, RIX. Straßenadresse unveröffentlicht.
Frankfurt DE-CIX-Dichtegürtel. Dual utility, Meet-me-reich. Straßenadresse unveröffentlicht.
Dallas–Fort-Worth-Colo-Korridor. Dual-Feed, US-Central-Latenz. Straßenadresse unveröffentlicht.
Mexiko-Stadt Metro-Carrier-Gürtel für LATAM Nord. Dual-Feed. Straßenadresse unveröffentlicht.
Singapore carrier-hotel belt with SGIX reach. Dual feed, badge-and-cage. Street address is not published.
Dubai metro colo corridor with UAE-IX reach. Dual feed, manned cages. Street address is not published.
Cape Town metro carrier belt. Dual feed, genset backup. Street address is not published.
Johannesburg / Midrand colo corridor, NAPAfrica reach. Dual feed. Street address is not published.
Almaty metro carrier belt. Dual feed, manned cages. Street address is not published.
Bangkok metro colo belt with BKNIX reach. Dual feed. Street address is not published.
Moscow metro carrier belt with MSK-IX reach. Dual feed, manned cages. Street address is not published.
Saint Petersburg metro colo belt, SPB-IX reach. Dual feed. Street address is not published.
Side by side
| City | Code | Facility | Uplink | Law | RTT to AMS |
|---|---|---|---|---|---|
| Island — Reykjavik | IS-RKV | Tier IV / N+1 | 10 Gbps | No mandatory data retention | 18 ms |
| Niederlande — Amsterdam | NL-AMS | Tier III+ / 2N | 40 Gbps | EU GDPR / hosting case law | 1 ms |
| Rumänien — Bucharest | RO-BUH | Tier III / 2N | 10 Gbps | No mandatory retention (2014) | 30 ms |
| Schweiz — Zurich | CH-ZRH | Tier IV / 2N+1 | 100 Gbps | Swiss FADP / non-EU | 9 ms |
| Brasilien — Sao Paulo | BR-SAO | Tier III / 2N | 40 Gbps | LGPD / Brazil | 140 ms |
| USA — Ashburn | US-ASH | Tier III+ / 2N | 100 Gbps | US law / Virginia | 85 ms |
| Hongkong — Hong Kong | HK-HKG | Tier III+ / 2N | 40 Gbps | Hong Kong SAR | 220 ms |
| China — Shanghai | CN-SHA | Tier III / 2N | 40 Gbps | PRC law / mainland | 240 ms |
| Japan — Tokyo | JP-TYO | Tier III+ / 2N | 100 Gbps | Japan / APPI | 230 ms |
| Lettland — Riga | LV-RIX | Tier III / 2N | 40 Gbps | EU GDPR / Latvia | 25 ms |
| Deutschland — Frankfurt | DE-FRA | Tier III+ / 2N | 100 Gbps | EU GDPR / Germany | 8 ms |
| USA — Dallas | US-DFW | Tier III+ / 2N | 100 Gbps | US law / Texas | 110 ms |
| Mexiko — Mexico City | MX-MEX | Tier III / 2N | 40 Gbps | LFPDPPP / Mexico | 160 ms |
| Singapore — Singapore | SG-SIN | Tier III+ / 2N | 100 Gbps | Singapore PDPA | 180 ms |
| United Arab Emirates — Dubai | AE-DXB | Tier III / 2N | 40 Gbps | UAE law / Dubai | 90 ms |
| South Africa — Cape Town | ZA-CPT | Tier III / 2N | 40 Gbps | POPIA / South Africa | 170 ms |
| South Africa — Johannesburg | ZA-JNB | Tier III / 2N | 40 Gbps | POPIA / South Africa | 160 ms |
| Kazakhstan — Almaty | KZ-ALA | Tier III / 2N | 40 Gbps | Kazakhstan data law | 80 ms |
| Thailand — Bangkok | TH-BKK | Tier III / 2N | 40 Gbps | Thailand PDPA | 200 ms |
| Russia — Moscow | RU-MOW | Tier III / 2N | 40 Gbps | Russian law / Moscow | 40 ms |
| Russia — Saint Petersburg | RU-LED | Tier III / 2N | 40 Gbps | Russian law / Saint Petersburg | 35 ms |
How to read this table
Every row sells the same SKU ladder at the same base list; the columns that actually differ are the ones checkout cannot change - facility tier, uplink class, and the law that governs the building. Nineteen flags carry that base list. Two are published premiums: Iceland adds 20 percent and Switzerland 35, because power, staffing and judicial predictability cost real money there. Nothing hides behind a contact-sales wall. Pick a city, pick a plan, and the invoice prints the final USD figure before any coin amount is calculated at the live rate.
Matching the city to the workload
Latency decides most orders: park a game or trading box within 30 ms of its users and the rest is negotiable. Jurisdiction decides the remainder. Speech-sensitive projects route to Reykjavik or Zurich. Data-heavy archival goes wherever the storage VPS ladder prices best per terabyte - the 2.5 to 10 Gbps unmetered ports do the moving either way. When one tenant needs whole cores, out-of-band IPMI and RAID across local NVMe, that is the dedicated line: same twenty-one cities, same invoice, 2-4 hours from payment to handover. VPS and storage plans provision in roughly sixty seconds everywhere on this map.
Location questions
Does the city change my plan price?
Nineteen of the twenty-one locations bill the identical base list. Only Iceland (+20%) and Switzerland (+35%) publish a premium, shown in checkout before you pay.
Can I move a deployed server to another city?
Not in place. The clean path is a second deployment in the new city, a data sync, then a DNS flip - snapshots and a Borg or Restic target make that a routine, scripted job.
Which city for privacy-sensitive workloads?
Reykjavik and Zurich are the usual answers for speech-adjacent projects; every location bills crypto and asks for no documents, so the deciding input should be law and latency, not marketing.