NulNetTwenty-one no-KYC locations — Iceland to Cape Town
Base list in nineteen locations. Only Iceland (+20%) and Switzerland (+35%) cost more. Amsterdam for peering; plus Romania, Latvia, Germany, Brazil, US, Mexico, Hong Kong, Shanghai, Tokyo, Singapore, Dubai, Cape Town, Johannesburg, Almaty, Bangkok, Moscow, Saint Petersburg. One SKN company. 16 crypto options.
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.
Southwest of the capital, on the geothermal campus belt. Cold-loop first; diesel is backup. FICIX in the hall.
Southeast metro, Science Park corridor — the AMS-IX hall neighborhood. Dual utility, 2N, meet-me density.
West Bucharest ring. Dual municipal feed plus on-site genset. BIX meet-me on the floor, with routing that does not hang on any single exchange.
North of Zurich, Glatt corridor. Hydro plus dual feed. SwissIX in-hall, DE-CIX a short fiber hop.
Sao Paulo metro carrier belt near IX.br density. Dual feed, manned cages. Street address is not published.
Ashburn corridor — US East colo density. Dual utility, meet-me rich. Street address is not published.
Hong Kong carrier hotel belt with HKIX reach. Dual feed, badge-and-cage. Street address is not published.
Shanghai metro connectivity campus for mainland-facing apps. Dual feed. Street address is not published.
Tokyo Inzai / metro carrier belt. JPIX reach, dual feed, manned cages. Street address is not published.
Riga metro carrier belt. Dual feed, manned cages, RIX reach. Street address is not published.
Frankfurt DE-CIX density belt. Dual utility, meet-me rich. Street address is not published.
Dallas-Fort Worth colo corridor. Dual feed, US Central latency. Street address is not published.
Mexico City metro carrier belt for LATAM north. Dual feed. Street address is not published.
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 |
|---|---|---|---|---|---|
| Iceland — Reykjavik | IS-RKV | Tier IV / N+1 | 10 Gbps | No mandatory data retention | 18 ms |
| Netherlands — Amsterdam | NL-AMS | Tier III+ / 2N | 40 Gbps | EU GDPR / hosting case law | 1 ms |
| Romania — Bucharest | RO-BUH | Tier III / 2N | 10 Gbps | No mandatory retention (2014) | 30 ms |
| Switzerland — Zurich | CH-ZRH | Tier IV / 2N+1 | 100 Gbps | Swiss FADP / non-EU | 9 ms |
| Brazil — Sao Paulo | BR-SAO | Tier III / 2N | 40 Gbps | LGPD / Brazil | 140 ms |
| United States — Ashburn | US-ASH | Tier III+ / 2N | 100 Gbps | US law / Virginia | 85 ms |
| Hong Kong — 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 |
| Latvia — Riga | LV-RIX | Tier III / 2N | 40 Gbps | EU GDPR / Latvia | 25 ms |
| Germany — Frankfurt | DE-FRA | Tier III+ / 2N | 100 Gbps | EU GDPR / Germany | 8 ms |
| United States — Dallas | US-DFW | Tier III+ / 2N | 100 Gbps | US law / Texas | 110 ms |
| Mexico — 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.