NulNet
Двадцать одна площадка — выбирайте город
Каждая карточка — отдельная площадка: кампус, аплинк, юрисдикция и наценка, если она применяется; на остальных — базовый прайс.
Юго-запад столицы, геотермальный пояс. Сначала холодный контур; дизель — резерв. FICIX в холле.
Юго-восток метро, Science Park — соседство холла AMS-IX. Два ввода, 2N, meet-me плотность.
Западное кольцо Бухареста. Два городских ввода и генератор. BIX meet-me; EU IP не только через AMS-IX.
Север Цюриха, коридор Glatt. Гидро и два ввода. SwissIX в холле, DE-CIX — короткий хоп.
Метро Сан-Паулу у IX.br. Два ввода, guarded cages. Улицу не публикуем.
Коридор Ashburn — плотность US East colo. Dual utility, meet-me. Улицу не публикуем.
Carrier-hotel пояс Гонконга с HKIX. Dual feed, badge-and-cage. Улицу не публикуем.
Кампус связности Шанхая для mainland-аудитории. Dual feed. Улицу не публикуем.
Пояс Inzai / метро Токио. JPIX, dual feed, guarded cages. Улицу не публикуем.
Carrier-пояс метро Риги. Dual feed, guarded cages, RIX. Улицу не публикуем.
Пояс плотности DE-CIX во Франкфурте. Dual utility, богатый meet-me. Улицу не публикуем.
Colo-коридор Dallas–Fort Worth. Dual feed, латентность US Central. Улицу не публикуем.
Carrier-пояс Мехико для севера LATAM. Dual feed. Улицу не публикуем.
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.
Рядом
| 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 | SG-SIN | Tier III+ / 2N | 100 Gbps | Singapore PDPA | 180 ms |
| ОАЭ — Dubai | AE-DXB | Tier III / 2N | 40 Gbps | UAE law / Dubai | 90 ms |
| ЮАР — Cape Town | ZA-CPT | Tier III / 2N | 40 Gbps | POPIA / South Africa | 170 ms |
| ЮАР — Johannesburg | ZA-JNB | Tier III / 2N | 40 Gbps | POPIA / South Africa | 160 ms |
| Казахстан — Almaty | KZ-ALA | Tier III / 2N | 40 Gbps | Kazakhstan data law | 80 ms |
| Таиланд — Bangkok | TH-BKK | Tier III / 2N | 40 Gbps | Thailand PDPA | 200 ms |
| Россия — Moscow | RU-MOW | Tier III / 2N | 40 Gbps | Russian law / Moscow | 40 ms |
| Россия — 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.