Originally published on , directly if historical uptime matters to your decision. All three are generally regarded as 99.9%+ providers in practice, but I'm not going to copy-paste a claim I can't verify.
Latency — probed from Helsinki
All tests run from the Hetzner CPX22 in Helsinki. Results are 50-packet ICMP probes (ping -c 50 -q). The "jitter" column is the mdev value — standard deviation of round-trip times, which matters for real-time workloads.
| Provider | Datacenter | Avg latency | Jitter (mdev) | Packet loss |
|---|---|---|---|---|
| Linode/Akamai | Frankfurt | 22.8 ms | 0.23 ms | 0% |
| Hetzner | Helsinki (local) | 23.6 ms | 0.21 ms | 0% |
| Vultr | Frankfurt | 27.1 ms | 1.08 ms | 0% |
| Vultr | Amsterdam | 27.9 ms | 0.14 ms | 0% |
| Contabo | Germany (our server) | 34.1 ms | 2.83 ms | 0% |
| DigitalOcean | Frankfurt | — | — | ICMP blocked |
Tested 2026-05-10. Probe source: Hetzner Helsinki. All providers probed via publicly documented test endpoints.
Three things stand out:
1. Linode Frankfurt is marginally faster to Helsinki than Hetzner Helsinki. Not by much — 22.8 ms vs 23.6 ms — and the jitter is essentially identical (0.23 vs 0.21 ms). Both routes are stable and consistent. If you're building a latency-sensitive service and your users are in Northern/Central Europe, Linode Frankfurt is a legitimate option.
2. Vultr's jitter varies by datacenter. Frankfurt (27.1 ms avg, 1.08 ms jitter) is noticeably bumpier than Amsterdam (27.9 ms avg, 0.14 ms jitter), even though the average round-trip times are close. For most self-hosting workloads this won't matter. For anything that cares about consistency (WebRTC, real-time APIs, game servers), pick Amsterdam if Vultr is your provider.
3. Contabo has the highest jitter by a wide margin. At 2.83 ms mdev, the round-trip times to our Contabo server swing considerably more than the other providers. This matches what the self-hosting community generally observes about Contabo's shared CPU architecture — they pack more tenants per host, which introduces scheduling noise. The absolute latency (34.1 ms) is also higher than the others, partly because our Contabo server is in Germany rather than Finland, and partly because of the higher jitter floor.
DigitalOcean: their Frankfurt datacenter blocks ICMP from external hosts and doesn't run an HTTP speedtest endpoint. This isn't unusual for large providers, but it does mean I have no latency numbers for them from Helsinki. If you need to benchmark DO, you'll need to spin up an instance and test from there.
Pricing (verified May 2026)
Closest equivalent plans across all five providers — chosen for comparability, not cherry-picking:
| Provider | Plan | vCPU | RAM | Storage | Bandwidth | Price/mo |
|---|---|---|---|---|---|---|
| Hetzner | CPX22 | 3 AMD | 8 GB | 80 GB NVMe | 20 TB | €8.98 |
| Contabo | Cloud VPS 10 | 4 | 8 GB | 75 GB NVMe | Unlimited* | €4.50 |
| Linode/Akamai | Linode 8GB | 4 | 8 GB | 160 GB SSD | 5 TB | $48 |
| Vultr | Regular 4GB† | 2 | 4 GB | 80 GB SSD | 3 TB | $20 |
| DigitalOcean | Basic 8GB | 4 | 8 GB | 160 GB SSD | 5 TB | $48 |
Contabo "unlimited" = fair use policy, 200 Mbit/s port. Check their current ToS.
†Vultr's 8 GB shared-CPU plan runs $120/mo — their pricing tier jumps sharply above 4 GB. The 4 GB plan is shown as the practical entry point. Verified May 2026.
The Hetzner/Contabo pricing gap vs the US-headquartered providers is stark. Linode and DigitalOcean both land at $48/month for 8 GB — more than 5× Hetzner's €8.98. Vultr's shared tier is cheaper but the RAM ceiling is lower before the price jumps significantly. The European providers have the pricing advantage for a reason: Hetzner and Contabo own their hardware and run their own datacenters, while Vultr/DO/Linode tend to mark up leased capacity. You pay for the global footprint and polished API/dashboard experience with the US providers.
Provider summary
Hetzner — best for most self-hosters in Europe
Thirty-three days of real production data gives me something useful to say about this one: it just works. The uptime numbers speak for themselves. The dashboard is clean, provisioning takes under a minute, the console doesn't require JavaScript gymnastics, and the €8.98/month CPX22 is genuinely hard to beat on price-to-performance for European users.
The one gap: limited non-European coverage. If your users are in Asia-Pacific or you need multiple regions, Hetzner's reach (Germany, Finland, US-East, US-West, Singapore) is narrower than the US providers.
What I run on it: Ghost blog, Nginx Proxy Manager, Uptime Kuma, three FastAPI subdomains. All in Docker. No issues.
Contabo — best for secondary infrastructure on a budget
At €4.50/month for 4 vCPU and 8 GB RAM, Contabo offers a spec sheet that nothing else at this price comes close to. The tradeoffs are real: higher latency (34 ms from Helsinki vs 23 ms from Hetzner), noticeably more jitter (2.83 ms mdev), and an older CPU generation that benchmarks lower on compute-intensive tasks.
For automation workloads, VPNs, or anything that's not handling real-time user traffic, the jitter doesn't matter. My N8N instance runs fine on it. I'd buy it again for the same use case. I'd reach for Hetzner first for anything user-facing.
Affiliate link: . Built them for this kind of audit work.
Questions or different numbers from your own setup? I'm enim on the usual channels — always interested in seeing what the same benchmark looks like from a different origin.
SOCIAL SHARE CARD GENERATOR