netcup vs Hetzner vs OVHcloud vs Contabo: In-Depth European Cloud Comparison
Key Facts
- netcup: Price-to-performance leader; Root Servers provide dedicated AMD EPYC 9645 (Zen 5) cores, 2.5 Gbps port, and unmetered traffic (2 TB/day fair-use threshold) with smooth invoice-based onboarding
- Hetzner: Cloud-native developer favorite with instant hourly billing and top-tier APIs, but strict automated KYC rejections and €1.00/TB overage charges above 20 TB egress
- Contabo: High paper specs at low headline prices, but heavy host oversubscription causes 20%–50% CPU Steal Time and severely throttled random 4K IOPS
- OVHcloud: Best-in-class VAC hardware DDoS mitigation capable of absorbing multi-hundred-Gbps floods, paired with complex control panels and slow standard support tickets
Table of Contents7 sections
When architects, DevOps engineers, and self-hosters evaluate European cloud and VPS infrastructure, the shortlist almost always narrows down to four major providers:
- netcup (Karlsruhe/Nuremberg, Germany — raw hardware density and dedicated-core value leader)
- Hetzner (Gunzenhausen/Falkenstein, Germany — hourly cloud agility and developer API leader)
- OVHcloud (Roubaix, France — global bare-metal scale and VAC hardware DDoS mitigation leader)
- Contabo (Munich, Germany — budget high-RAM marketing leader)
Comparing these four purely by their homepage banners ("4 vCPU / 8 GB RAM for €X") is a classic trap. Under real production load, one provider delivers dedicated Zen 5 silicon while another stalls at 40% CPU steal time; one lets you destroy instances by the hour while another binds you to a 12-month German contract with a 31-day cancellation notice.
This technical comparison strips away marketing claims and evaluates CPU isolation, storage IOPS, bandwidth policies, KYC onboarding friction, DDoS mitigation, and contract mechanics.
1. Head-to-Head Technical & Operational Matrix#
| Evaluation Metric | netcup | Hetzner (Cloud) | OVHcloud | Contabo |
|---|---|---|---|---|
| CPU Architecture & Isolation | Exceptional Root Servers: 100% dedicated AMD EPYC 9645 (Zen 5) (GB6 Single ~2100+) VPS: fast shared EPYC vCores | Exceptional Consistent shared (CX/CPX) & dedicated (CCX) vCPUs Very low noisy-neighbor impact | Moderate to High Entry VPS uses shared vCores; Dedicated bare-metal is rock solid | Low to Moderate Heavily oversubscribed hosts; Frequent 20%–50% %st CPU steal spikes |
| Storage IOPS & Throughput | High Root Servers: pure PCIe NVMe (100k+ 4K IOPS) G12.5 VPS: enterprise SSD RAID10 | Very High Fast local NVMe or Ceph network storage Highly predictable latency | Moderate Tiered by product line; Entry VPS IOPS are capped | Heavily Throttled Advertised NVMe is often rate-limited to a few thousand IOPS under load |
| Bandwidth & Traffic Policy | 2.5 Gbps Port / Unmetered (Throttled to 200 Mbps only if 24h average exceeds 2 TB/day) | 20 TB Included Egress (EU/US; billed at €1.00 / TB above 20 TB) | Unmetered Traffic (Port speed capped between 100 Mbps and 2 Gbps by tier) | Unmetered Traffic (Subject to aggressive port shaping on sustained transfers) |
| Billing & Contract Model | German Fixed-Term Contract 1 / 12 / 24-month cycles ( plus hourly on select tiers) Requires 31-day cancellation notice | Pure Hourly Cloud Per-second/hourly billing up to monthly cap Destroy anytime to stop billing | Hybrid Model Monthly rolling or 12/24-month commitments Standard auto-renewal toggles | Monthly / Annual Prepay Often charges initial Setup Fees on short terms; Monthly cancellation ticket |
| Account Onboarding & KYC | Smooth & Predictable No automated selfie/passport wall; Post-audit invoice generation via CCP | Extremely Strict Automated fraud scoring rejects VPNs/mismatched data instantly; mandatory ID/selfie | Moderate Depends on region and payment method; Occasional manual address verification | Low to Moderate Standard checkout flow with occasional email verification |
| DDoS Protection | Solid Baseline Protection Free automated L3/L4 scrubbing (~2 Tbps backbone capacity) | Standard Cloud Filtering Blocks common floods; extreme targeted attacks may trigger temporary null-routing | Industry-Leading (OVH VAC) Always-on global hardware scrubbing; Handles massive L3/L4/L7 game & UDP floods | Basic Limited mitigation visibility; Prone to null-routing during sustained attacks |
| Support Response Time | Fast on German Business Days Competent engineering tickets within hours | Very Fast Responsive ticket & phone support during business hours | Slow on Standard Tiers Community/standard tickets often take 48–96 hours | Moderate First-line responses are frequently scripted templates |
2. Architectural Trade-Offs: Where Each Provider Wins (and Loses)#
1. netcup: Unbeatable Dedicated EPYC Hardware vs. German Contract Law#
- Why engineers choose netcup: On a Root Server (RS G12.5), netcup allocates dedicated physical threads on flagship AMD EPYC 9645 (Zen 5) processors paired with DDR5 ECC RAM, pure NVMe storage, and a 2.5 Gbps network port. Unlike Hetzner's 20 TB cap, netcup includes unmetered traffic—you can push up to 2 TB per day (~60 TB/month) before temporary 200 Mbps fair-use shaping applies.
- The trade-off you must respect: netcup operates under traditional German telecommunications contract rules. Discounted 12-month and 24-month plans carry a minimum contract term (
Mindestvertragslaufzeit) and must be canceled in the CCP at least 31 days before the contract expires (Kündigungsfrist), or they automatically renew for another full term. - Best for: Long-term production workloads—Kubernetes nodes, PostgreSQL/MySQL databases, Docker stacks, mail servers, and high-bandwidth media/backup nodes where hardware density per euro matters most.
2. Hetzner Cloud: Frictionless Hourly API vs. Strict KYC & 20 TB Traffic Caps#
- Why engineers choose Hetzner: Hetzner Cloud feels like a streamlined, affordable European AWS. Its web console, CLI (
hcloud), Terraform provider, cloud-init speed, private networking, and floating IPs are best-in-class, and you can spin up 50 nodes for two hours and delete them for pennies. - The trade-offs:
- Automated KYC rejections: Hetzner's fraud-prevention filter is notoriously aggressive. Signing up with a VPN active, using a virtual card, or having a slight mismatch between your IP geolocation and billing address often triggers an immediate, non-appealable account rejection.
- Hard 20 TB egress limit: While 20 TB is plenty for web apps, high-throughput workloads (CDN edge nodes, object-storage mirrors, video streaming, or offsite backups) will incur €1.00 per additional TB, whereas netcup allows ~60 TB/month at full 2.5 Gbps speed for €0 overage.
- Best for: Autoscaling CI/CD runners, ephemeral staging environments, Terraform-managed cloud fleets, and short-lived projects.
3. Contabo: Massive Paper Specs vs. Noisy Neighbors & Throttled IOPS#
- Why buyers are tempted: Contabo's pricing table looks irresistible on paper—offering 16 GB to 32 GB of RAM at price points where competitors offer 8 GB.
- The production reality:
- High CPU Steal (
%st): Host nodes are heavily oversubscribed. During European peak hours, runningtoporhtopfrequently reveals 20% to 50% CPU Steal Time—meaning your VM is waiting in a hypervisor queue while neighboring VMs consume physical CPU cycles. - Disk I/O bottlenecks: Running
fiorandom 4K read/write benchmarks often shows IOPS throttled down to 2,000–5,000 IOPS, causing database transactions and container builds to stall.
- High CPU Steal (
- Best for: Latency-insensitive hobby workloads that need large amounts of idle RAM in memory without sustained CPU or disk I/O pressure.
4. OVHcloud: Unrivaled VAC DDoS Mitigation vs. Bureaucratic Support#
- Why engineers choose OVHcloud: OVHcloud operates its proprietary VAC (Vacuum Anti-DDoS) hardware scrubbing infrastructure across a massive global backbone. If you host public game servers (Minecraft, Rust, FiveM), VoIP gateways, or high-risk web properties that attract multi-hundred-Gbps UDP/SYN floods, OVHcloud keeps packets flowing where other hosts null-route your IP.
- The trade-off: The OVH control panel is sprawling and slow, and standard (non-Enterprise) support tickets can take several business days to receive an initial reply.
- Best for: DDoS-magnet workloads, public multiplayer game servers, and multi-region bare-metal deployments.
3. Final Decision Matrix: Which One Should You Deploy?#
- Choose netcup if you want maximum dedicated compute, NVMe speed, and bandwidth per euro:
- Opt for the Root Server G12.5 series to get dedicated AMD EPYC Zen 5 cores, DDR5 ECC memory, and up to 60 TB/month of full-speed 2.5 Gbps traffic.
- Grab a free-month or €5 voucher, order from your residential connection without a VPN (Ordering Guide), and set a calendar reminder for the 31-day contract notice window.
- Choose Hetzner Cloud if you need hourly elasticity and infrastructure-as-code:
- Ideal when you spin servers up and down daily via API/Terraform and stay well within the 20 TB monthly traffic allowance.
- Choose OVHcloud if DDoS survival is your #1 operational requirement:
- Trade away support speed and single-core price-performance in exchange for enterprise-grade VAC packet scrubbing.
- Be cautious with Contabo for production databases or latency-sensitive apps:
- Unless your workload only needs cheap idle RAM and can tolerate high CPU steal and throttled disk IOPS, netcup's VPS or Root Server lineup will deliver far more consistent latency.
Provider ComparisonHetznerContaboOVHcloudCloud Benchmarks