Infrastructure # The network, described precisely. Bandwidth is where hosting pages are vaguest, so this one is specific: what each port is, what it costs when you saturate it, who we buy transit from, and what we do not offer. - 25 Gbit/s on an 8-GPU node, unmetered - $0 overage, at any volume - /64 IPv6 routed to every machine - 6 sites, each on two carriers plus an IX ## Port speed and traffic The port is sized with the chassis, because a node that can saturate a card can saturate a link. Every port is unmetered in both directions: there is no included volume, no overage tier and nothing to watch on a graph. **Port speed, included traffic and available upgrade, by node size** | Node | Port | Monthly traffic | Upgrade | Cost of the upgrade | |---|---|---|---|---| | 1 × GPU 128 GB RAM · 2 × 2 TB NVMe | 1 Gbit/s Full duplex, dedicated | UnmeteredNo cap, no burst billing | 10 Gbit/s | $49/mo | | 2 × GPU 256 GB RAM · 2 × 3.84 TB NVMe | 2 Gbit/s Full duplex, dedicated | UnmeteredNo cap, no burst billing | 10 Gbit/s | $49/mo | | 4 × GPU 512 GB RAM · 4 × 3.84 TB NVMe | 10 Gbit/s Full duplex, dedicated | UnmeteredNo cap, no burst billing | Already 10 Gbit/s or above | — | | 8 × GPU 1024 GB RAM · 8 × 3.84 TB NVMe | 25 Gbit/s Full duplex, dedicated | UnmeteredNo cap, no burst billing | Already 10 Gbit/s or above | — | | 10 × GPU 1024 GB RAM · 8 × 7.68 TB NVMe | 25 Gbit/s Full duplex, dedicated | UnmeteredNo cap, no burst billing | Already 10 Gbit/s or above | — | Unmetered means what it says: you may hold the port at line rate for the whole month. We reserve the right to talk to you about it only if a single machine starts degrading the shared uplink for everybody else in the suite — and that conversation has happened twice in five years, both times about a misconfigured mirror. ## Transit and peering Every site buys from at least two independent carriers and sits on the local internet exchange. A carrier failure is a re-route, not an outage — which is the only reason we are willing to write 99.9% on a contract. **Internet exchange and transit carriers, by data centre** | Data centre | Internet exchange | Transit carriers | Uplink | |---|---|---|---| | Amsterdam Netherlands · Tier III | AMS-IX, NL-ix | Cogent, Arelion, Lumen | 2 × 100 Gbit/sDiverse paths, diverse rooms | | Stockholm Sweden · Tier III | Netnod, STHIX | Arelion, GlobalConnect | 2 × 100 Gbit/sDiverse paths, diverse rooms | | Zürich Switzerland · Tier IV | SwissIX, CIXP | Init7, Cogent | 2 × 100 Gbit/sDiverse paths, diverse rooms | | Reykjavík Iceland · Tier III | RIX Reykjavík | Farice, Síminn | 2 × 100 Gbit/sDiverse paths, diverse rooms | | Montréal Canada · Tier III | QIX Montréal | Cogent, Zayo | 2 × 100 Gbit/sDiverse paths, diverse rooms | | Singapore Singapore · Tier III | SGIX, Equinix Singapore | Arelion, Singtel | 2 × 100 Gbit/sDiverse paths, diverse rooms | ## Addressing IPv4 One address, included Routed to the machine, yours for the life of the term. Additional addresses are $3/month each, up to eight. IPv6 A /64, included Routed, not bridged. That is 18 quintillion addresses per machine, at no cost, and we will never ask you to justify one. Reverse DNS Yours to set Forward and reverse records on every address you hold, changed by you, applied within a minute. No ticket. Address history Clean on delivery An address that has been listed anywhere is held out of the pool until it is delisted. You do not inherit someone else's reputation. **Outbound port 25 is closed by default.** Not to inconvenience you — a GPU rental with open SMTP becomes a spam relay within days, and the whole range gets listed. If you have a genuine reason to send mail from the machine, ask us and we will open it on that address. ## DDoS filtering Volumetric filtering is on from the moment the machine is delivered. It is not an option, it is not a tier, and it does not appear on the invoice. ### Always on, L3 and L4 Scrubbing at the edge of each site, in front of our own routers. Detection is automatic on rate and signature; nothing waits for a human. ### Mitigation in seconds Under ten seconds from the first anomalous packet to filtered traffic, up to the site's full transit capacity. Legitimate sessions are not reset. ### No null-routing your address Some hosts answer an attack by dropping your IP for 24 hours. We filter it. Your machine stays reachable, which is the entire point of paying for filtering. ## GPU interconnect Inside a node, what connects the cards to each other decides whether a large model is fast or merely possible. This is the part of the specification we are asked about most, and the part most listings leave out. **Interconnect available between GPUs, by card form factor** | Form factor | Cards | Between GPUs | Practical effect | |---|---|---|---| | SXM on an HGX board 4- and 8-GPU nodes only | A100 SXM4 80 GB, H100 SXM5 80 GB, H200 SXM5 141 GB, B200 SXM6 180 GB | NVLink via NVSwitch All-to-all, 900 GB/s per card | Tensor parallelism across the whole board without the interconnect becoming the bottleneck. | | PCIe cards 1 to 10 GPUs | L4 24 GB, RTX 4090 24 GB, RTX 5090 32 GB, RTX A6000 48 GB, L40S 48 GB, A100 PCIe 40 GB… | PCIe Gen4 ×16 or Gen5 ×16 32 to 64 GB/s per card, peer-to-peer | Fine for pipeline parallelism, batch inference and one-model-per-card serving. Slower than NVLink for tensor parallelism across many cards. | If you are unsure which of the two your workload needs: a model that fits on one card never needs NVLink, and a model split across four or more cards almost always benefits from it. The fit checker in [the configurator](https://gpuserver.io/configure) tells you which case you are in before you pay. ## Latency between sites Measured from our own routers to the named cities, as a round trip, over thirty days. They are medians, not best cases. AMS Operational ### Amsterdam Netherlands Round trip 7 ms to Frankfurt, 12 ms to London Exchange AMS-IX, NL-ix Our suite since 2021 STO Operational ### Stockholm Sweden Round trip 22 ms to Frankfurt, 31 ms to London Exchange Netnod, STHIX Our suite since 2022 ZRH Operational ### Zürich Switzerland Round trip 9 ms to Milan, 15 ms to Frankfurt Exchange SwissIX, CIXP Our suite since 2023 REY Operational ### Reykjavík Iceland Round trip 18 ms to London, 40 ms to New York Exchange RIX Reykjavík Our suite since 2024 YUL Operational ### Montréal Canada Round trip 12 ms to New York, 19 ms to Toronto Exchange QIX Montréal Our suite since 2023 SIN Operational ### Singapore Singapore Round trip 38 ms to Tokyo, 45 ms to Sydney Exchange SGIX, Equinix Singapore Our suite since 2025 ## What we do not offer Stated here rather than discovered after payment. If one of these is a requirement, we are the wrong provider and it is cheaper for both of us to know now. **Multi-node InfiniBand.** NVLink connects the cards inside one node. We do not sell a fabric between nodes, so a job that needs 32 GPUs in one training run is not something we can serve. **BGP sessions or bring-your-own-IP.** We announce our own space only. There is no way to advertise your prefix from our routers. **Layer-2 links between data centres.** A private VLAN joins your machines *within* one site. Between sites, you build the tunnel yourself. **Committed transit or a private uplink.** The port is unmetered and shared upstream. We will not sign a dedicated-capacity contract on top of it. **Open SMTP on delivery.** Port 25 outbound is closed until you ask, for the reason given above. **An anonymity network.** Filtering protects your machine from attack. It is not a proxy, it does not hide where your traffic goes, and we do not pretend otherwise. ## Every port above is on every machine. There is no networking tier to choose. Pick the GPU, pick the site, and the port comes with the chassis. [Browse the catalogue](https://gpuserver.io/#catalog) [Read the guides](https://gpuserver.io/guides) ## Related pages - [Hardware policy The twelve NVIDIA GPUs we operate, the 72-hour burn-in before a node is sold, the four-hour replacement target, and how disks are erased between tenants.](https://gpuserver.io/hardware) - [Service status Live status of every gpuserver.io component and data centre, probed every 60 seconds from five cities, with 90-day uptime and the incident log since 2022.](https://gpuserver.io/status) - [Service level agreement The 99.9% commitment: what counts as downtime, how it is measured from outside, five minutes of term back per minute lost, and the exclusions in full.](https://gpuserver.io/legal/sla) - [Documentation First SSH, verifying the hardware, CUDA containers, serving a model with vLLM, RAID, firewalling, IPMI and reinstalls — the commands, on a real machine.](https://gpuserver.io/docs) --- Source: https://gpuserver.io/network/. This file is generated from the same data as the website; if a figure here differs from a page, the page is authoritative and this file is stale — the canonical source is https://gpuserver.io/.