Provider dataset
5 collected plans. Filter below; “monthly average” helps compare, while “actual payment” gives the term and total you will be billed.
Plan database
Actual payment terms, totals, setup fees and minimum terms are shown. Monthly averages compare recurring charges only and exclude one-time fees. Filtering and sorting happen locally.
| Plan / provider | Actual payment | Monthly average | CPU | Memory | Storage | Transfer / port | Availability | Location | IPv4 |
|---|---|---|---|---|---|---|---|---|---|
| CPX22 Hetzner Cloud · Virtual machine / VPS · Shared CPU · regular-performance | US$22.99 / 1 month Regional price: eu-central | Monthly average US$22.99 | 2 vCPU | 4 GB | 80 GB SSD | 20,480 GB Port unknown | Unknown | Falkenstein (FSN), Nuremberg (NBG), Helsinki (HEL), eu-central | No IPv4 |
| CPX32 Hetzner Cloud · Virtual machine / VPS · Shared CPU · regular-performance | US$41.99 / 1 month Regional price: eu-central | Monthly average US$41.99 | 4 vCPU | 8 GB | 160 GB SSD | 20,480 GB Port unknown | Unknown | Falkenstein (FSN), Nuremberg (NBG), Helsinki (HEL), eu-central | No IPv4 |
| CPX42 Hetzner Cloud · Virtual machine / VPS · Shared CPU · regular-performance | US$81.99 / 1 month Regional price: eu-central | Monthly average US$81.99 | 8 vCPU | 16 GB | 320 GB SSD | 20,480 GB Port unknown | Unknown | Falkenstein (FSN), Nuremberg (NBG), Helsinki (HEL), eu-central | No IPv4 |
| CPX52 Hetzner Cloud · Virtual machine / VPS · Shared CPU · regular-performance | US$118.99 / 1 month Regional price: eu-central | Monthly average US$118.99 | 12 vCPU | 24 GB | 480 GB SSD | 20,480 GB Port unknown | Unknown | Falkenstein (FSN), Nuremberg (NBG), Helsinki (HEL), eu-central | No IPv4 |
| CPX62 Hetzner Cloud · Virtual machine / VPS · Shared CPU · regular-performance | US$152.99 / 1 month Regional price: eu-central | Monthly average US$152.99 | 16 vCPU | 32 GB | 640 GB SSD | 20,480 GB Port unknown | Unknown | Falkenstein (FSN), Nuremberg (NBG), Helsinki (HEL), eu-central | No IPv4 |
No plans match these filters. Try relaxing a condition.
Purchase & usage policies
Only facts explicitly extracted from official terms are shown. Missing fields remain unknown; no promises are added on a provider's behalf.
This does not mean there are no restrictions or that a use case is allowed by default. Check the provider's latest terms before ordering.
Incident & remedy evidence
Incident count, response speed, remediation and compensation are recorded separately; one incident is not converted directly into a provider score.
Coverage: Latest 10 records from the official API; oldest record in this batch 27 Jul 2026, 20:22There was a routing issue in our Europe backbone. This caused brief routing loops and packet loss. We apologize for the inconvenience. Thank you for your understanding.
Remediation: The issue has been resolved.
Object Storage service in location fsn1 is currently degraded. Requests may fail or time out. We are currently investigating the issue.
Remediation: The problem is fixed.
For a brief period, there were disruptions in traffic distribution across our authoritative DNS servers. Some DNS queries were not resolved within the expected response time, which could temporarily result in higher latency or failed DNS lookups. The root cause has been identified and the affected components are fully operational again.
Cause: For a brief period, there were disruptions in traffic distribution across our authoritative DNS servers. Some DNS queries were not resolved within the expected response time, which could temporarily result in higher latency or failed DNS lookups. The root cause has been identified and the affected components are f…
Remediation: For a brief period, there were disruptions in traffic distribution across our authoritative DNS servers. Some DNS queries were not resolved within the expected response time, which could temporarily result in higher latency or failed DNS lookups. The root cause has been identified and the affected components are f…
We are currently experiencing a fault on our cloud leaf hel1-cloud1-leaf9. Our technicians are working hard on analyzing the cause of the interruption in order to solve the issue. Please bear with us. As soon as more information is available, we shall inform you via this website. We apologize for any inconvenience. Thank you for your understanding.
Remediation: All host systems are fully accessible again, network components are fully available, and redundancy has been completely restored. The situation will continue to be monitored on an ongoing basis.
We are currently experiencing a fault on our cloud leaf nbg1-cloud1-leaf97. Our technicians are working hard on analyzing the cause of the interruption in order to solve the issue. Please bear with us. As soon as more information is available, we shall inform you via this website. We apologize for any inconvenience. Thank you for your understanding.
Remediation: All host systems are fully accessible again, network components are fully available, and redundancy has been completely restored. The situation will continue to be monitored on an ongoing basis.
In the mentioned period, we will perform maintenance work on the mirror (mirror.hetzner.com / download.hetzner.com) in the region ASH, which may briefly lead to system updates being interrupted in that region.
Remediation: We have successfully completed the maintenance work. Thank you for your understanding.
In the above-mentioned period, maintenance will be performed at the backbone connection between Frankfurt - Helsinki. This may lead to brief latency issues. We apologize for any inconvenience. Thank you for your understanding.
Remediation: Maintenance work has been completed successfully. Thank you for your understanding.
Currently there is a delay in creating or modifying resources in the Hetzner Cloud.
Remediation: The problem is fixed and creating and modifying resources works as usual.
We are currently experiencing a fault on our cloud leaf hel1-cloud1-leaf16. Our technicians are working hard on analyzing the cause of the interruption in order to solve the issue. Please bear with us. As soon as more information is available, we shall inform you via this website. We apologize for any inconvenience. Thank you for your understanding.
Remediation: Both components are now fully operational; redundancy has been fully restored.
We are currently experiencing a fault on our cloud leaf fsn1-cloud2-leaf17. Our technicians are working hard on analyzing the cause of the interruption in order to solve the issue. Please bear with us. As soon as more information is available, we shall inform you via this website. We apologize for any inconvenience. Thank you for your understanding.
Remediation: The issue has been resolved. We are continuing to monitor the system.
Community evidence
Community reports can inform incident scope, support and remedies, but remain community evidence. Authors, dates, materials and official links are shown without turning a thread title directly into a platform conclusion.
This does not mean there is no discussion or that reputation is good or bad.
This source record
Raw responses are archived with the build; the fingerprint ties this page back to the same original response.