Pick when you want the lowest credible €/spec ratio in the EU and your traffic is happy on a Falkenstein/Helsinki box. Avoid if you need managed databases/Kubernetes, US/APAC low-latency at scale, port 25 from day one, or a polished support story when account verification trips a flag.
Verified against Hetzner Cloud's pricing pages.
Deal-breaker for self-hosted mail & transactional email.
Outbound TCP/25 and TCP/465 are blocked by default on every new Cloud Server to suppress spam. The block lifts once you (a) have been a paying customer for ~30 days and at least one paid invoice has cleared, and (b) open a support ticket asking for the unblock with a stated, legitimate use case (e.g. transactional mail, MX relay). Port 587 (submission, STARTTLS) is open from day one and works fine with relay providers (SendGrid, Mailgun, Postmark, AWS SES). Once unblocked, Hetzner's PTR records are configurable from the console — making it one of the very few mainstream clouds where self-hosted mail (Mail-in-a-Box, Mailcow, Postfix) is actually practical.
Verified Apr 27, 2026 · source
What the marketing pages don't tell you.
Outbound TCP/25 and TCP/465 are blocked by default on every new Cloud Server. The block lifts only after you have paid your first invoice (typically ~30 days) AND opened a support ticket asking for the unblock with a stated use case. Port 587 (submission with STARTTLS) is open from day one for relay providers. Plan the timeline if you're standing up self-hosted mail (Mail-in-a-Box, Mailcow) — you'll be relay-only for the first month.
The single most consistent complaint on Reddit, Hacker News (Ask HN: Hetzner banned me), LowEndTalk and Trustpilot is account suspensions with terse or no explanation — typically 'violation of System Policies' or 'verification failed' — and the appeal path is the same support queue with no escalation tier. New accounts created from VPN exits, residential addresses that don't match billing, or signups that share fingerprints with a previously banned account are the most common triggers. Mitigation: sign up from a clean residential connection, complete ID verification proactively, and never run anything mission-critical without offsite backups before day 30.
Hetzner raised cloud server prices 30-37% across the board on April 1 2026, citing increased infrastructure and hardware costs. The CPX22 went from €5.99 to €7.99/mo. Hetzner is still cheaper than DigitalOcean, Vultr, and Linode at equivalent specs — but the previous 'unbeatable' margin is gone. If your last cost comparison was pre-2026, redo it before signing up.
Hetzner Cloud is unmanaged compute first, full stop. There's no managed PostgreSQL/MySQL/Redis (run it yourself on a CCX or use Aiven/Neon/Supabase), no managed Kubernetes (community uses the Kube-Hetzner Terraform module to deploy k3s on top of regular Cloud Servers), and no native CDN (front public assets with Cloudflare or BunnyCDN). If you need the full DigitalOcean-style managed-services ladder, this is the wrong provider.
EU plans uniformly include 20 TB outbound — practically unmetered. US CPX/CCX plans include only 1 TB, and Singapore plans include 0.5-8 TB depending on instance type. EU and US overage is €1/TB (cheap), but Singapore overage is €7.40/TB (~7x more). A CPX22 in SIN burning 5 TB/mo would owe €40+ in overage on top of the €7.99 instance price. If you pick ASH / HIL / SIN, model the bandwidth bill explicitly before assuming Hetzner is still the cheapest option.
Cloud-specific tickets are 24/7/365, but the general support team works Monday-Friday 8-18 CET. There is no 24/7 chat, no phone support for cloud customers (phone is dedicated-server-only), and support is English/German only. Time-zone overlap is genuinely tight if you're operating from US Pacific or APAC and need a non-cloud-ticket category answered.
Scored across six dimensions — an editorial estimate, not a guarantee.
Hetzner Cloud Console is clean and fast — server creation is genuinely under 60 seconds. The hcloud CLI is well-maintained, the REST API is straightforward, and Terraform/Pulumi/Ansible providers are first-class. One-click apps cover the core self-hosting stack (Coolify, Docker, GitLab, Nextcloud, WordPress, WireGuard). The gap vs DigitalOcean is breadth and polish — fewer Marketplace apps, no App Platform / managed PaaS layer, and the docs feel German-engineered rather than warmly conversational. Sufficient for engineers, less obvious for first-timers.
Modern AMD EPYC and Intel Xeon hardware, NVMe RAID10 storage across all tiers, ~40k IOPS at 4k random and 1.5 GB/s sequential. Geekbench 6 single-core ~939 — above DigitalOcean Basic, below Vultr High Frequency / EPYC Genoa. EU network is genuinely exceptional (8+ Gbps to Amsterdam, 10 Gbit redundant uplinks); US and Singapore latency to EU is the natural trade-off (130-180ms). For workloads pinned to a single EU region, this is one of the best-performing budget clouds available.
99.9% per-server SLA with cloud-credit compensation if missed, public status page (status.hetzner.com) with timely incident posts, mature DC operations since 1997. Localised outages happen — the 2024 NBG3 fire and several short FSN1 maintenance windows in 2025 were transparently posted — but the long-term track record is solid. The bigger reliability question is account-level: discretionary suspensions can take a service down with little warning, which is a separate dimension from infrastructure uptime.
When tickets land in the standard cloud queue, replies are typically fast (often under an hour) and technically competent. Documentation and the community.hetzner.com tutorials site are excellent. The drag is everything outside the happy path: no 24/7 chat, no phone for cloud, English/German only, and Reddit / Trustpilot / HN consistently surface stories of slow or terse handling around verification, abuse reports, and billing disputes. Trustpilot sits at 3.3/5 across ~2,700 reviews, with the bottom-third reviews clustered around exactly those failure modes.
Public pricing, public SLA, public status page, public docs site, public price-adjustment statement (with the actual reasoning), and a clear changelog on the API. The SMTP port 25 policy and 30-day unblock window are documented in the FAQ. The opacity is around account-level decisions: when an account is suspended or verification fails, the explanation is often 'system policies violated' with no specifics, and that's the consistent complaint across review platforms. Pricing itself is honest; account governance is not.
Even after the April 1 2026 price adjustment (+30-37% across most plans), Hetzner is still the best price/spec ratio in the mainstream cloud market. CPX22 (2 vCPU / 4 GB / 80 GB / 20 TB) at €7.99/mo undercuts DigitalOcean's $24/mo Basic 2/4 by ~3x at similar performance. EU traffic allowances are practically unmetered (20 TB), backups are 20% flat, and there's no first-term/renewal split. The new pricing narrowed the gap but didn't close it.
Control panel: Hetzner Cloud Console (own); hcloud CLI; full REST API; Terraform / Pulumi / Ansible providers · full root access
6 regions worldwide.
Response time: No published SLA — cloud tickets typically answered within ~1h in EU hours, sometimes minutes. No 24/7 chat. No phone for cloud (dedicated-only).
Verified Apr 27, 2026
Sentiment in 2026 is sharply bimodal. The hands-on developer crowd (r/selfhosted, r/sysadmin, Hacker News, LowEndTalk) overwhelmingly recommends Hetzner Cloud as the best price/performance in unmanaged VPS — the running joke is 'just use Hetzner' — and sees the April 1 price increase as still leaving Hetzner ~50-60% cheaper than the US-based alternatives. Trustpilot tells a different story, sitting at 3.3/5 across ~2,700 reviews where the negative cluster is overwhelmingly about account suspensions, verification failures, and abuse-handling: people who hit the happy path love Hetzner, people who trip a flag tend to write detailed angry reviews. The April 1 2026 price hike was widely discussed but mostly accepted — community framing was 'still the cheap option, just less unbeatable than before'.
Sentiment verified Apr 27, 2026
Top-rated alternatives on the board.