Summary

  • Since 1 October, OVHcloud lists public IPv4 separately from compute and Generation 3 local disk separately from the instance. Compute-hourly rates did not change, but the configured workload can cost more.
  • OVHcloud’s published IPv4 rate is €0.0027 per hour excluding tax, or about €1.97 for its 730-hour month. That is the provider’s retail charge for a cloud resource, not a transfer-market price for IPv4 space or evidence of the provider’s margin.
  • The invoice now rewards customers for not assigning an address or disk they do not need, while Savings Plan discounts remain limited to compute. A committed compute price is therefore not an all-in bill ceiling.

For years, a cloud server’s public address could disappear inside a single instance price. OVHcloud’s change makes the IPv4 count legible: from 1 October 2026, public addresses are a separate billing line, while local storage is also separated for B3, C3 and R3 Generation 3 instances. Compute-hourly prices stay the same. The purchase has not become one-dimensional; the bill now shows more of the components that were previously bundled.

OVHcloud lists public IPv4 at €0.0027 an hour excluding VAT, approximately €1.97 per month on a 730-hour basis. Its Local Low Latency disk is listed at €0.0001458 per GB-hour, or roughly €0.11 per GB-month. Those figures are current service tariffs. They do not reveal the price at which an IPv4 block trades, what OVHcloud pays for address capacity, or the economic value enabled by a particular customer’s workload.

That distinction matters because a provider price and an address asset price answer different questions. The first is what a customer pays for one provider-controlled public-IP service during a billing period. The second may involve a transferable block, rights, registry records, routing arrangements, counterparty diligence and duration. A €1.97 monthly line is not a spot valuation of an address, much less a price for acquiring control of one.

The change is concentrated in the configured machine

The cost effect varies with the server shape. OVHcloud’s examples show a B3-16 with 100 GB of local disk moving from €75 to €87 per month, an increase of 16.9%, and a C3-8 with 100 GB moving from €67 to €79, an increase of 18.9%. These are provider calculations for a 730-hour month, before tax and without commitment. They are not a universal customer bill. A machine with no public IPv4, or a different amount of local storage, has a different resource mix.

The change in local storage is narrower than the address change. Public IPv4 becomes separately billed across instance ranges, including earlier generations and gateways. Local disk remains bundled on earlier B2, C2 and R2 instances; OVHcloud separates it for B3, C3 and R3. A customer comparing generations therefore has to track two decisions, not one: whether a workload needs a public address, and how much local disk it needs.

That is a useful form of cost visibility. The provider’s own example places ten private B3-16 instances behind one public-facing gateway. It estimates €860.70 monthly for that design, compared with €869.70 if each of the ten private instances had its own address. The approximate €2 per address per month adds up when the count scales. But the example is not proof that the gateway design suits every system. A gateway adds a dependency and may change routing, availability, administration, latency and failure isolation. Public-facing services, customer allowlists or software that expects a stable machine address may require a different pattern.

Compute discounts leave a second bill outside the commitment

The more consequential contract boundary is between compute and its complements. OVHcloud says a Savings Plan discounts compute. Existing plans keep their covered instance price and discount during the commitment, but the separately billed IPv4 and local-disk charges are not included in that guarantee; they are charged at current rates from 1 October. New 12- and 36-month plans advertise compute discounts of 15% and 30%, respectively. The discount does not follow the address or disk line.

This is not a contradiction in the contract; it is a narrower object of commitment. A buyer has committed to a discounted stream of compute, not to a fixed total cost for the architecture that makes the compute usable. If the public-address count, disk capacity or rates change, the cloud bill can move while the core instance price remains locked. Procurement teams that compare only vCPU, memory and compute discount will miss the supporting resources that now appear beside them.

The measure to monitor after rollout is not just whether OVHcloud’s advertised compute price stays flat. It is the mix of public addresses per workload, the share of instances that can operate through private networks, local disk per instance, gateway cost, and the full invoice under each plan. No public source reviewed discloses customer-level response, migration rates, address utilization or realized savings. The provider’s examples illustrate a possible design choice, not what its customers have actually done.

There is a practical lesson for cloud buyers: separate address count, storage capacity, compute commitment and egress in the cost model before signing a term. Then test whether private networking, a gateway, Flex disk sizing, or IPv6-compatible application paths preserve the required service. Do not assume that deleting an IPv4 address is operationally neutral or that IPv6 removes every dependency. A price line can prompt a useful review; it cannot perform the architecture review for you.

OVHcloud has made a cloud input more visible. Whether customers respond by releasing unneeded addresses, changing network design, absorbing the charge or moving workloads is not yet established. The new line item may improve the information available for those decisions. It does not, on its own, prove that IPv4 is fairly priced, that all public addresses are avoidable, or that the total cost of cloud has become predictable.

Sources: OVHcloud’s rate and configuration examples; OVHcloud’s pricing-model and Savings Plan explanation; current OVHcloud Public Cloud prices.