Hosting, ancho de banda e ingeniería de redes, escrito por el equipo que opera el AS 25198 — capacidad sin límite, peering, almacenamiento y las decisiones que hay detrás. Los artículos se publican en inglés.
One UDP port, a dozen lines of configuration and an encryption protocol built into the Linux kernel. From a fresh Ubuntu or Debian server to a working tunnel on a laptop and a phone, including the IPv6 leak most guides miss, split tunnelling, MTU fixes and keeping the server locked down.
A bond of two 10 Gbps links carries 20 Gbps in total, but no single connection runs faster than one link. Why LACP hashes each flow to one member, the default setting that sends all of a server's traffic down one port, a working netplan config, and how to test the aggregate properly.
Managed Kubernetes hides the control plane, the load balancers and the storage behind an API and bills for every gigabyte that leaves. On bare metal, compute is cheaper and egress is flat, but those pieces become yours. The decisions in order, with a costed three-server cluster at the end.
Both give you root over SSH, and on day one they feel the same. The difference shows when you load a kernel module, run Docker, tune the network or install anything that is not Linux. How KVM and containers work, what only your own kernel allows, and the one command that tells you which you have.
Low prices come from three places: paid-off hardware, a thin network, or missing essentials. Only the first is a good trade. What a 2016 dual Xeon gives up against a new EPYC, the network fine print to read, price per thread against a VPS, and four checks to run on delivery.
Port speed, guaranteed rate and traffic allowance are three different numbers, and VPS plan pages love to blur them. What a guaranteed gigabit moves in a month, why bandwidth costs CPU as well, how to test a plan with iperf3, and where a VPS stops and a dedicated server starts.
Ashburn sits next to the transatlantic cable landings and within about 15 ms of New York, Toronto, Chicago and Atlanta. How it pairs with a European primary, why one TCP flow across the Atlantic cannot fill a big port, and what the GDPR says about putting EU data there.
Poland is the EU's fifth most populous country, and every Baltic capital and Kyiv sit within 9 ms of floor from Warsaw. For game servers, regional services and patch-day delivery that distance is the whole argument. The latency table, the sizing rules and when Warsaw is the wrong pick.
Marseille faces south and east: it is where 2Africa, PEACE and AAE-1 come ashore. For North Africa it is 650 to 800 km closer than Frankfurt; for the Gulf it is the European end of the cable. The latency table, the video and regional workloads that fit, and the limits.
For users in Romania, Bulgaria, Moldova and Serbia, a server in Frankfurt adds 15 to 20 ms to every round trip. Bucharest removes it at the same price, keeps the data in the EU, and is where our 96 TB storage servers live. The latency table, the workloads and the sizing.
Amsterdam and Frankfurt are under 4 ms apart, so for most of Europe the choice is a wash. At the edges it is not: the UK, Ireland, the Benelux and the Nordics lean Amsterdam. The latency table, the VPN and delivery workloads that suit it, and a sizing rule for each.
Frankfurt is the default European location, and usually the right one: one of the world's largest internet exchanges, and no major capital in the west or centre of the continent more than about 25 ms away. The latency table, the workloads that fit, and the cases where another city wins.