Back to plans
Hetzner CX 53
📍 Nuremberg, Germany · $20.65
CPU type: shared
Disk: NVME
Virtualization: kvm
Plan Highlights
CPU Type
shared
Memory
30.60 GB
Best Single
1427
Best Multi
10727
Best Disk
3580.4 MB/s
Best Latency
0.0 ms
Key Specs
CPU ModelAMD EPYC-Rome Processor
CPU Typeshared
Cores16
Memory30.60 GB
RAMunknown
Storage300 GB NVME
Geekbench Single1427
Geekbench Multi10727
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-21 | 💲20.65 | 🖥️ 16 | 🧠 30.60 GB | 1427 | 10727 | 💾 3580.4 MB/s | 📶 10.0 ms | 1,411 | 0.0% |
| 2025-12-15 | 💲20.65 | 🖥️ 16 | 🧠 30.60 GB | 1188 | 8571 | 💾 2564.8 MB/s | 📶 10.6 ms | - | 0.0% |
| 2025-12-13 | 💲20.65 | 🖥️ 16 | 🧠 30.60 GB | 722 | 5258 | 💾 2090.9 MB/s | 📶 27.8 ms | - | 0.0% |
| 2025-12-13 | 💲20.65 | 🖥️ 16 | 🧠 30.60 GB | 1245 | 8506 | 💾 2347.3 MB/s | 📶 10.8 ms | - | 0.0% |
| 2025-11-26 | 💲20.65 | 🖥️ 16 | 🧠 30.60 GB | 1202 | 8495 | 💾 3471.2 MB/s | 📶 0.0 ms | - | 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 | ⬇️ 103.3 MB/s | ⬆️ 103.6 MB/s | 🔁 206.9 MB/s | 52,974 |
| 64k | ⬇️ 963.5 MB/s | ⬆️ 968.6 MB/s | 🔁 1932.1 MB/s | 30,913 |
| 512k | ⬇️ 1480.0 MB/s | ⬆️ 1558.6 MB/s | 🔁 3038.6 MB/s | 6,076 |
| 1m | ⬇️ 1732.5 MB/s | ⬆️ 1847.9 MB/s | 🔁 3580.4 MB/s | 3,579 |
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,411 events/s |
| Sysbench CPU | Multi-thread events (16 threads) | 22,536 events/s |
| Sysbench Memory | Read / Write | 42194.6 / 24087.0 MB/s |
| File I/O | Read / Write throughput | 2.3 / 1.6 MB/s |
| Overselling | CPU steal / variance | 0.0% / 0.3% |
Show detailed extended metrics
File I/O Details
| Metric | Read | Write |
|---|---|---|
| Throughput | 2.3 MB/s | 1.6 MB/s |
| IOPS | 148 | 99 |
| Fsync Avg Latency | 0.08 ms | |
| Thread Contention | 2.16 ms | |
Ping to DNS Servers
| Target | Avg | Min | Max | Loss |
|---|---|---|---|---|
| Google DNS (8.8.8.8) | 3.90 ms | 3.66 ms | 5.34 ms | 0% |
| Cloudflare DNS (1.1.1.1) | 4.09 ms | 4.00 ms | 4.39 ms | 0% |
| Quad9 DNS (9.9.9.9) | 8.87 ms | 8.78 ms | 8.92 ms | 0% |
Latency Routes (from -> to)
| Mode | Route | Provider | Send | Recv | Latency |
|---|---|---|---|---|---|
| IPv4 | Nuremberg, Germany -> 🇳🇱 Amsterdam, Netherlands | Eranium | 3.23 Gbits/sec | 4.36 Gbits/sec | 📶 9.9 ms |
| IPv6 | Nuremberg, Germany -> 🇳🇱 Amsterdam, Netherlands | Eranium | 12.7 Gbits/sec | 4.19 Gbits/sec | 📶 12.6 ms |
| IPv6 | Nuremberg, Germany -> 🇬🇧 London, United Kingdom | Clouvider | 2.04 Gbits/sec | 8.27 Gbits/sec | 📶 18.7 ms |
| IPv4 | Nuremberg, Germany -> 🇬🇧 London, United Kingdom | Clouvider | 249 Mbits/sec | 7.24 Gbits/sec | 📶 18.9 ms |
| IPv4 | Nuremberg, Germany -> 🇺🇿 Tashkent, Uzbekistan | Uztelecom | 1.72 Gbits/sec | 2.02 Gbits/sec | 📶 88.4 ms |
| IPv6 | Nuremberg, Germany -> 🇺🇿 Tashkent, Uzbekistan | Uztelecom | 1.96 Gbits/sec | 2.58 Gbits/sec | 📶 88.6 ms |
| IPv6 | Nuremberg, Germany -> 🇺🇸 NYC, United States | Leaseweb | 1.96 Gbits/sec | 2.41 Gbits/sec | 📶 97.0 ms |
| IPv6 | Nuremberg, Germany -> 🇸🇬 Singapore, Singapore | Leaseweb | 1.07 Gbits/sec | 1.29 Gbits/sec | 📶 159.0 ms |
| IPv4 | Nuremberg, Germany -> 🇺🇸 Los Angeles, United States | Clouvider | 1.05 Gbits/sec | 1.29 Gbits/sec | 📶 161.0 ms |
| IPv6 | Nuremberg, Germany -> 🇺🇸 Los Angeles, United States | Clouvider | 1.02 Gbits/sec | 1.26 Gbits/sec | 📶 162.0 ms |
| IPv4 | Nuremberg, Germany -> 🇧🇷 Sao Paulo, Brazil | Edgoo | 1.02 Gbits/sec | 1.25 Gbits/sec | 📶 201.0 ms |
| IPv6 | Nuremberg, Germany -> 🇧🇷 Sao Paulo, Brazil | Edgoo | 863 Mbits/sec | busy | 📶 202.0 ms |