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.
首都西南地热园区。冷循环优先，柴油备用。厅内 FICIX。
东南城区 Science Park 走廊 — AMS-IX 周边。双路市电、2N、meet-me 密集。
布加勒斯特西环。双市电 + 现场发电机。BIX meet-me；欧盟 IP，不必只经 AMS-IX。
苏黎世以北 Glatt 走廊。水电 + 双路供电。厅内 SwissIX，短纤到 DE-CIX。
圣保罗城域运营商带，靠近 IX.br。双路供电、有人值守。不公布街道地址。
Ashburn 走廊 — 美东托管密度。双路市电、meet-me 丰富。不公布街道地址。
香港运营商酒店带，可达 HKIX。双路供电、门禁机笼。不公布街道地址。
上海城域互联园区，面向内地应用。双路供电。不公布街道地址。
东京印西/城域运营商带。JPIX、双路供电、有人值守。不公布街道地址。
里加城域运营商带。双路供电、机笼、RIX。不公布街道地址。
法兰克福 DE-CIX 密度带。双路市电、meet-me 丰富。不公布街道地址。
达拉斯–沃斯堡托管走廊。双路供电、美中延迟。不公布街道地址。
墨西哥城运营商带，面向拉美北部。双路供电。不公布街道地址。
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 |
|---|---|---|---|---|---|
| 冰岛 — Reykjavik | IS-RKV | Tier IV / N+1 | 10 Gbps | No mandatory data retention | 18 ms |
| 荷兰 — Amsterdam | NL-AMS | Tier III+ / 2N | 40 Gbps | EU GDPR / hosting case law | 1 ms |
| 罗马尼亚 — Bucharest | RO-BUH | Tier III / 2N | 10 Gbps | No mandatory retention (2014) | 30 ms |
| 瑞士 — Zurich | CH-ZRH | Tier IV / 2N+1 | 100 Gbps | Swiss FADP / non-EU | 9 ms |
| 巴西 — Sao Paulo | BR-SAO | Tier III / 2N | 40 Gbps | LGPD / Brazil | 140 ms |
| 美国 — Ashburn | US-ASH | Tier III+ / 2N | 100 Gbps | US law / Virginia | 85 ms |
| 香港 — Hong Kong | HK-HKG | Tier III+ / 2N | 40 Gbps | Hong Kong SAR | 220 ms |
| 中国 — Shanghai | CN-SHA | Tier III / 2N | 40 Gbps | PRC law / mainland | 240 ms |
| 日本 — Tokyo | JP-TYO | Tier III+ / 2N | 100 Gbps | Japan / APPI | 230 ms |
| 拉脱维亚 — Riga | LV-RIX | Tier III / 2N | 40 Gbps | EU GDPR / Latvia | 25 ms |
| 德国 — Frankfurt | DE-FRA | Tier III+ / 2N | 100 Gbps | EU GDPR / Germany | 8 ms |
| 美国 — Dallas | US-DFW | Tier III+ / 2N | 100 Gbps | US law / Texas | 110 ms |
| 墨西哥 — 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.