Contabo Review: Huge Specs, Hidden Tradeoffs

The Contabo Pitch

Open Contabo’s website and your jaw drops:

4 cores and 8GB RAM for five euros? At Vultr that’s $48/month. At DigitalOcean, same. Contabo is literally 10x cheaper on paper.

But paper specs aren’t real-world performance. Let me show you what actually happens.

The Reality: Disk IO

This is Contabo’s fatal flaw. Real benchmarks from the VPS S plan:

Sequential Write: 180 MB/s
4K Random Read: 8,500 IOPS
4K Random Write: 3,200 IOPS

For comparison, Hetzner at a similar price:

4K Random Read: 95,000 IOPS
4K Random Write: 62,000 IOPS

That’s an 11x difference in random read performance. In practice, this means:

• WordPress pages load in 3+ seconds instead of under 1 second
• MySQL queries take 3-5x longer
• System feels sluggish under any disk-intensive load

Contabo labels their storage as “SSD” but it performs nothing like modern NVMe drives.

The Reality: CPU Overselling

Those “4 cores” on paper? Here’s what Geekbench actually shows:

At peak hours, 35% of your CPU time is being stolen by other VMs on the same host. Your “4 cores” perform like 2.5 cores. This is aggressive overselling.

The Reality: Network

All Contabo plans are capped at 200Mbps. Not burst — that’s the hard ceiling.

For a personal blog, 200Mbps is fine. For anything serving concurrent users, video, or large files — it’s a bottleneck. The upside: traffic is unmetered, so no surprise bills.

Provisioning: Not Instant

Unlike Vultr (60 seconds) or Hetzner (2 minutes), Contabo uses manual provisioning. Expect 1-3 business days after payment before your server is ready. Order on a Friday? Might not get it until Tuesday.

First-time orders may also require ID verification, adding more delay.

Setup Fees

Most Contabo plans have a one-time setup fee (typically €4.99). Not a dealbreaker, but annoying if you’re used to spinning up and destroying servers frequently.

Where Contabo Actually Shines

Despite all the negatives, there are legitimate use cases:

1. Memory-hungry applications — Need 16GB+ RAM for Elasticsearch, Redis clusters, or in-memory caches? Contabo is the cheapest way to get it.

2. Cold storage / backups — Their HDD plans offer terabytes of storage for pennies. Great for offsite backups.

3. Background processing — Batch jobs, data pipelines, anything that doesn’t need fast IO or real-time response.

4. Dev/test environments — Mirror production specs without production costs.

Contabo vs Hetzner

This is the most common comparison. Both are German, both are cheap:

Bottom line: Hetzner wins in every dimension except raw RAM quantity.

Who Should Buy Contabo

• Projects where RAM is the bottleneck, not IO
• Backup/archival storage needs
• Long-running background jobs
• Budget-constrained dev environments
• Anyone who literally only cares about RAM-per-dollar

Who Should Avoid

• Web applications serving end users (IO kills page speed)
• Database-heavy workloads (IOPS are terrible)
• Anything needing quick spin-up (provisioning is slow)
• High-bandwidth use cases (200Mbps ceiling)
• Time-sensitive projects (setup delays)

Verdict

Contabo sells the illusion of powerful servers at impossibly low prices. The specs look incredible on paper but fall apart under real workloads because of crippled IO, aggressive overselling, and bandwidth caps.

If you specifically need cheap RAM and nothing else matters — Contabo works. For literally any other use case, spend a few extra euros on Hetzner and get a server that actually performs like its specs suggest.

Don’t confuse “big numbers on the spec sheet” with “fast server.” They are not the same thing.