Summary
- Hetzner publishes one Primary IPv4 at €0.0008 per hour and €0.50 per month. My division puts the crossover at 625 hours, or 26.04 days, so the monthly figure is reached inside every calendar month.
- The rule that caps a bill at the monthly price is written about the server in all three places it appears. On the twelve Hetzner pages I read, no sentence states that it reaches the address, and the 15 June 2026 repricing expressly excluded IPs while raising cloud plan prices.
Two prices, one object
The table on Hetzner's Primary IPs overview is the whole article in one row: | IPv4 | € 0.0008 / h $ 0.0010 / h | € 0.50 / mo $ 0.60 / mo | (overview). The same page says it plainly in prose — We charge € 0.50 / $ 0.60 per month (excl. VAT) for our Primary IPv4s. — and charges nothing for the IPv6 half of the pair.
Two units, one object, one price list. That is not a contradiction. It is a quotation problem, and it is the kind a buyer can settle with a calculator rather than an opinion.
The general IP pricing page sells the same Cloud row as Cloud Primary IPv4 | € 0.50 ($ 0.60) monthly and prints no hourly rate beside it (IP pricing). Its revision label reads 2023-04-13, while the overview's reads 2022-06-28. Those labels say what the pages print today; they do not say when the amounts last changed.
The division I did
Take the two printed euro figures and divide. €0.50 ÷ €0.0008 = 625 hours. 625 ÷ 24 = 26.04 days. In dollars, $0.60 ÷ $0.0010 = 600 hours, or 25.00 days.
Both are mine, not Hetzner's. But the first result is unhelpful to the hourly rate: a 28-day February is 672 hours, a 30-day month is 720, a 31-day month is 744. All three exceed 625. At the printed hourly rate, the monthly figure is reached before any calendar month on earth ends.
Run the hourly rate across the whole month and the gap shows itself. €0.0008 × 744 = €0.5952. × 720 = €0.5760. × 672 = €0.5376. In dollars: $0.0010 × 744 = $0.7440, × 672 = $0.6720. Each is my multiplication of a printed rate by a printed month length — not an amount Hetzner says it charges.
The sentence that caps the bill
Here is where the arithmetic stops being arithmetic. Hetzner's billing FAQ states the rule: Mathematically speaking, we will bill you for the minimum amount, whether that is the monthly price cap OR the hourly price multiplied by the number of hours you used the server. (billing FAQ) The same FAQ, earlier in the run, put it as Your server's bill will never exceed its monthly price cap. And the payment overview adds: Once you reach the monthly cap, we will automatically switch from the hourly to the monthly rate. (payment overview)
Read the grammatical subject in all three places. It is the server. The Regular Performance page repeats the identical sentence — Your server's bill will never exceed its monthly price cap. — over a CPX02 listed from €5.49 a month (Regular Performance).
So the cap exists, and it is written about a machine. Whether that same minimum-of-cap-or-hours rule reaches the address is not stated on any page I read. The crossover above is therefore a documentary finding, not a bill: 625 hours is the point where the two printed figures for the address meet, and the instrument that would decide which of them applies to a bare address is the one sentence nobody has written.
An address in existence, not in use
The FAQ is explicit that the address is its own invoice line: We bill Primary IPs (IPv4, IPv6) and cloud servers separately, and we list both resources separately in invoices. And then the part that decides what the customer is buying: We will bill you for all Primary IPs that have finished the creation process, including Primary IPs that are not assigned to any cloud server.
The charge follows existence, not attachment. Deleting the Primary IP is what stops it. A cloud server's price does not include a public address at all — the European Cloud page advertises the saving directly: Primary IPv4 IPv6 only save € 0.50 per month, excl. VAT (European Cloud). The address is a line a customer adds and a line a customer must remove.
The line that has no hourly rate
Hetzner sells a second kind of address, and it does not repeat the pattern. The dedicated-server entry reads Additional single IP | € 1.70 | € 4.90 — a monthly figure and a one-off figure, with no hourly rate anywhere on that line. There is no crossover to compute there, and I do not convert the €0.50 into the €1.70: they are different products on different pages.
That difference matters for anyone comparing quotes. A cloud address is printed in two time units. A dedicated address is printed in a monthly charge plus a one-time charge, and the one-time part does not recur. Nothing in either line is an hourly rate for a dedicated IP.
What the 2026 repricing did not touch
Hetzner repriced its servers twice in 2026. The June notice is unusual for what it excluded: All dedicated servers and cloud plans at all locations are affected by this adjustment. However, web hosting products, managed servers, servers from the Server Auction, IPs, storage products, Load Balancers, Volumes, Snapshots, and Object Storage are not affected. (15 June 2026 notice) The changes applied to new orders and to rescales of existing servers.
The April statement reads: The price changes take effect on 1 April 2026 and are for both new orders and existing products. It prints no rate table and no IP figure (1 April 2026 statement).
Put the two beside each other and you have a dated asymmetry a reader can check without trusting me: the machines got repriced, and the address was expressly carved out of the June adjustment. The €0.50 survived a repricing round in which almost every other line on the invoice moved.
Hetzner's own scarcity language
The company does not hide the reason. Its dedicated Primary IPv4 FAQ says: In recent years, the prices for IPv4 addresses have steadily increased. And since not all of our customers need or want an IPv4 address, we have now introduced the new product for our dedicated root servers, the Primary IPv4 Addon. (Primary IPv4 FAQ) The same page notes that a server ordered without the add-on still receives IPv6.
How much IPv6: All servers have a /64 IPv6 subnet. That is a subnet of about 18 quintillion addresses against one, and Hetzner's IP page attaches a condition to asking for more IPv4 — allocation must conform to RIPE guidelines and requires a valid technical reason (IP addresses).
Hetzner's own explainer gives the adoption figure in its own words, from about 5% to about 36% over five years. It is the company's undated explainer number, not a current measurement, and I present it as what the page prints.
The second month
There is another quantity on these pages measured in months, and it has the same quotation trap. Included Cloud traffic is 20 TB in the EU, 0.5–5 TB in Singapore depending on plan, and 1–5 TB in the US depending on plan; Cloud traffic is calculated over calendar months and counts outgoing traffic only (traffic).
The Singapore page prints the marginal rate — $8.49 per TB beyond the allowance (the Singapore Cloud page). Because the allowance itself is a range, no single per-terabyte included divisor exists on the pages I read; one terabyte over the allowance costs what the page prints, and nothing more can be inferred.
And the perimeter is not the account, it is the zone: Traffic between two different network zones (such as Hetzner Cloud servers in Europe and USA) will be billed just as any other normal internet traffic. The same page says powered-off Cloud servers keep billing until deleted (locations).
Twelve pages, no bridge
I read twelve Hetzner pages for this article. None of the twelve prints an allocation, an address block, a member number, or any sentence connecting a customer's monthly address line to Hetzner's own registry holding. That negative finding is scoped to those twelve pages and to this date. It is not a claim about Hetzner's registry record, about RIPE NCC, or about what any contract says.
What it does establish is where the reader's question has to go. The price of an address is published in two units. The unit the registry counts in is not one of them. Between the invoice line and the block there is no document on these pages — and the honest next step is not a guess about blocks, it is the sentence Hetzner has not written: whether the monthly cap reaches an address that is not attached to a server.
What you can recompute
Multiply the printed hourly rate by your hours. Compare it with the printed monthly figure. The smaller number is what the cap rule produces for a server, in the words Hetzner uses. For an address, the two printed figures meet after 625 hours in euros and 600 in dollars, and every calendar month is longer than that — which means the monthly figure is the one that survives a full-month division.
Everything else here is a reading limit rather than a finding. The pages were retrieved, not opened in a browser by me; the revision labels are not change dates; the retrieved pricing text was partly truncated, and CPX caps vary by plan and location. No invoice, statement or ticket was read. I assert no customer's charge and no motive behind any price.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






