Back to plans
Hetzner CPX 22
📍 Nuremberg, Germany · $7.66
CPU type: shared
Disk: NVME
Virtualization: kvm
Plan Highlights
CPU Type
shared
Memory
3.72 GB
Best Single
1903
Best Multi
3472
Best Disk
4447.3 MB/s
Best Latency
9.1 ms
Key Specs
CPU ModelAMD EPYC-Genoa Processor
CPU Typeshared
Cores2
Memory3.72 GB
RAMunknown
Storage75 GB NVME
Geekbench Single1903
Geekbench Multi3472
Geekbench Report Open result
Plan Snapshot (Last 5 Runs)
Green = strong, yellow = medium, red = weak.
| Date | Price | Cores | Memory | Single | Multi | Disk Speed | Latency | Sysbench CPU | CPU Steal |
|---|---|---|---|---|---|---|---|---|---|
| 2026-02-20 | 💲7.66 | 🖥️ 2 | 🧠 3.72 GB | 1903 | 3472 | 💾 4447.3 MB/s | 📶 9.1 ms | 1,642 | 0.0% |
I/O Details (HDD/SSD/RAM Context)
This plan uses NVME storage and unknown RAM.
| Block Size | Read | Write | Read+Write | IOPS (RW) |
|---|---|---|---|---|
| 4k | ⬇️ 137.4 MB/s | ⬆️ 137.7 MB/s | 🔁 275.1 MB/s | 70,425 |
| 64k | ⬇️ 1258.5 MB/s | ⬆️ 1265.2 MB/s | 🔁 2523.7 MB/s | 40,378 |
| 512k | ⬇️ 2019.2 MB/s | ⬆️ 2126.5 MB/s | 🔁 4145.7 MB/s | 8,291 |
| 1m | ⬇️ 2152.0 MB/s | ⬆️ 2295.3 MB/s | 🔁 4447.3 MB/s | 4,447 |
Extended Benchmarks
Core custom metrics are summarized below. Expand details only when you need raw breakdowns.
| Group | Metric | Value |
|---|---|---|
| Sysbench CPU | Single-thread events | 1,642 events/s |
| Sysbench CPU | Multi-thread events (2 threads) | 3,299 events/s |
| Sysbench Memory | Read / Write | 53306.9 / 30790.4 MB/s |
| File I/O | Read / Write throughput | 1.5 / 1.0 MB/s |
| Overselling | CPU steal / variance | 0.0% / 0.1% |
Show detailed extended metrics
File I/O Details
| Metric | Read | Write |
|---|---|---|
| Throughput | 1.5 MB/s | 1.0 MB/s |
| IOPS | 96 | 64 |
| Fsync Avg Latency | 0.12 ms | |
| Thread Contention | 0.68 ms | |
Ping to DNS Servers
| Target | Avg | Min | Max | Loss |
|---|---|---|---|---|
| Google DNS (8.8.8.8) | 4.05 ms | 3.70 ms | 6.80 ms | 0% |
| Cloudflare DNS (1.1.1.1) | 4.14 ms | 4.01 ms | 4.43 ms | 0% |
| Quad9 DNS (9.9.9.9) | 8.92 ms | 8.75 ms | 9.05 ms | 0% |
Latency Routes (from -> to)
| Mode | Route | Provider | Send | Recv | Latency |
|---|---|---|---|---|---|
| IPv4 | Nuremberg, Germany -> 🇳🇱 Amsterdam, Netherlands | Eranium | 3.60 Gbits/sec | 4.66 Gbits/sec | 📶 9.1 ms |
| IPv6 | Nuremberg, Germany -> 🇳🇱 Amsterdam, Netherlands | Eranium | 13.0 Gbits/sec | 4.65 Gbits/sec | 📶 10.0 ms |
| IPv6 | Nuremberg, Germany -> 🇬🇧 London, United Kingdom | Clouvider | 7.27 Gbits/sec | 6.50 Gbits/sec | 📶 18.0 ms |
| IPv4 | Nuremberg, Germany -> 🇬🇧 London, United Kingdom | Clouvider | 6.66 Gbits/sec | 4.60 Gbits/sec | 📶 18.9 ms |
| IPv6 | Nuremberg, Germany -> 🇺🇿 Tashkent, Uzbekistan | Uztelecom | 1.98 Gbits/sec | 3.15 Gbits/sec | 📶 88.5 ms |
| IPv4 | Nuremberg, Germany -> 🇺🇿 Tashkent, Uzbekistan | Uztelecom | 1.78 Gbits/sec | 1.56 Gbits/sec | 📶 88.8 ms |
| IPv6 | Nuremberg, Germany -> 🇺🇸 NYC, United States | Leaseweb | 1.77 Gbits/sec | 2.51 Gbits/sec | 📶 96.3 ms |
| IPv4 | Nuremberg, Germany -> 🇸🇬 Singapore, Singapore | Leaseweb | 894 Mbits/sec | 1.27 Gbits/sec | 📶 158.0 ms |
| IPv6 | Nuremberg, Germany -> 🇸🇬 Singapore, Singapore | Leaseweb | 1.02 Gbits/sec | 1.14 Gbits/sec | 📶 159.0 ms |
| IPv4 | Nuremberg, Germany -> 🇺🇸 Los Angeles, United States | Clouvider | 1.01 Gbits/sec | 1.09 Gbits/sec | 📶 162.0 ms |
| IPv6 | Nuremberg, Germany -> 🇺🇸 Los Angeles, United States | Clouvider | 1.01 Gbits/sec | 1.11 Gbits/sec | 📶 162.0 ms |
| IPv4 | Nuremberg, Germany -> 🇧🇷 Sao Paulo, Brazil | Edgoo | 1.14 Gbits/sec | 1.29 Gbits/sec | 📶 202.0 ms |
| IPv6 | Nuremberg, Germany -> 🇧🇷 Sao Paulo, Brazil | Edgoo | 934 Mbits/sec | 1.08 Gbits/sec | 📶 202.0 ms |