OVHcloud Now Bills Disks and IPv4 Apart, Up to 21.9% More. New Savings Plans Lock Only the Discount

On October 1, 2026, OVHcloud stopped including two things in the price of its Generation 3 Public Cloud instances: the local disk and the public IPv4 address. The hourly price of the B3, C3 and R3 instances did not move. The disk became a storage class of its own, "Local Low Latency", billed at €0.0001458 per GB per hour, about €0.11 per GB per month. The address costs €0.0027 an hour, about €1.97 a month, billed per second, "including when the address is not attached to an instance." All prices here exclude VAT. Octave Klaba, OVHcloud's founder and CEO, outlined the change on social media on August 10. On August 25, OVHcloud detailed it in two blog posts he signed, and put the result for an identical configuration at 1.4% to 21.9% more, depending on size.
OVHcloud generates each Public Cloud project's bill on the first day of the following month. So the bill dated November 1 is the first one with the two new lines on it.
I buy infrastructure as the CTO of a LegalTech, and I ship small products as an indie developer. Small products are where this change bites, because the increase is a fixed amount in euros, and a fixed amount weighs most on the smallest machine. I read both posts and OVHcloud's billing guide line by line. The clause I would read twice is not about disks. It is about what a Savings Plan now guarantees.
A flat fee by disk size
The local disk is still fixed by instance size: 50, 100, 200 or 400 GB. In OVHcloud's words, "a B3-64 comes with 400 GB, no matter what your actual use is." It says it is working on letting customers size the disk independently, or start without one, but has no date to announce.
At 730 hours a month, the basis OVHcloud uses for its own tables, the two new lines come to:
- 50 GB of disk plus one IPv4 address: about €7.30 a month
- 100 GB plus one address: about €12.60
- 200 GB plus one address: about €23.30
- 400 GB plus one address: about €44.50
The disk stops at 400 GB, so the add-on stops growing there. OVHcloud's own table shows the effect. The b3-8, the smallest B3 in it, goes from €37 to €45 a month (+19.5%). The c3-4 goes from €33 to €41 (+21.9%), the top of the range. The b3-64 goes from €299 to €343 (+14.9%). The r3-1024 goes from €3,092 to €3,137 (+1.4%).
For a small SaaS, the first of OVHcloud's four examples is the useful one: three c3-8 front servers with public addresses and two b3-16 database servers on the private network go from €351 to €408.30 a month. That is €57.30 more a month, €687.60 a year, for the same five machines. And an address nobody uses now costs about €23.65 a year, every year.
The address line reaches older ranges too
The disk change applies to Generation 3 only: B2, C2, R2 and earlier keep their local storage included. The address is different. OVHcloud's announcement says per-second IPv4 billing applies to "all Public Cloud VM ranges and the Gateway", and OVHcloud's US blog spells it out: a separately billed, optional resource "on every instance range, including Generation 2 (B2, C2, R2) and earlier." Staying on an older generation saves you the disk line, not the address line.
None of this is exotic. AWS has charged $0.005 per hour for every public IPv4 address, attached or not, since February 1, 2024, about $3.65 a month. OVHcloud says it is "aligning our model with the market", and at €1.97 it is still cheaper per address. It also says why now: "Buying memory costs us six times more today than it did a year ago, and storage is following the same trajectory."
The gateway math
OVHcloud's suggested fix for addresses is a fully private network behind a Gateway, which pools outbound traffic behind a single address. In its second example, ten private b3-16 instances behind a Gateway M cost €860.70 a month, against €869.70 if each had its own public address. In OVHcloud's table, that is €9 a month saved across ten machines.
Run it the other way. OVHcloud's price list puts the Gateway M at about €8.10 a month, and a gateway needs a public address, now €1.97: about €10.07 in all, roughly five addresses. The example table prints €10.70, which does not match the +24% printed next to it, so I would trust the price list. Either way, on price alone, a gateway pays for itself from about six private instances that need outbound internet access. Below that, the reason to do it is the other one OVHcloud gives: fewer services exposed to the internet. A good reason. Just not a saving.
And if a server never needs to reach the internet at all, like a database that only talks to your front servers, removing its address saves the full €1.97 with no gateway in the picture.
The Savings Plan clause
The Savings Plans grid changed on September 1. Two terms remain: 12 months at 15% off and 36 months at 30% off. The 1, 6 and 24-month terms are gone. The discount applies to compute only: the disk and the address are billed at full price for the whole plan.
Plans signed before the change keep their instance price and their discount until they end, but the disk and the address are not covered. OVHcloud's fourth example is a c3-8 on a 12-month plan signed July 1, 2026, at the old rate of 35% off: €44 a month. From October 1, the disk and the address are added at full price, so €56 a month while the commitment still runs. At renewal in July 2027, at 15% off, it becomes €57 of compute plus €12 of disk and address: €69. Same machine, €44 to €69, about 57% more, against 18.9% for a customer who never committed (who now pays €79, so the plan still saves money).
Then the structural change. Under the old plans, OVHcloud guaranteed the instance price and the discount. Under the new grid, it guarantees the percentage. In its words: "The catalogue price, on the other hand, remains the current price: if it changes, your invoice will follow, but the discount is retained." A 36-month commitment is now a discount on whatever the list price becomes. It is no longer a price lock.
OVHcloud is candid about the reason. With memory six times dearer and "component forecasts that nobody commits to beyond a few weeks", it will not promise a deep three-year discount it might have to take back. It adds that its committed price remains "approximately twice as low as that of the market leader, compared to three times lower previously." That is OVHcloud's own comparison, and it does not name the leader or the configuration.
Not the first move this year
In February, Next reported that OVHcloud's VPS 2026 range would rise from April 1, the entry-level VPS 1 going from €5.39 to €7.79 a month before any commitment discount. On August 11, MacGeneration reported increases on dedicated servers for new customers from September, 51% on average on the latest generation, and wrote that Klaba did not expect a return to normal before 2029 at best. In percentage terms, the Public Cloud change is the mildest of the three. It is also the one that turns into a habit: two lines you can now manage, or forget.
What I would check before the next bill
- List every public IPv4 address in each project, attached or not. Each one is about €1.97 a month whether it serves traffic or not.
- For each instance, ask whether it must be reachable from the internet. Front servers, yes. Databases and workers that only talk to them, usually not.
- Compare the disk you pay for with the disk you use. Flex instances have a 50 GB local disk whatever their size, so the add-on stays at about €7.30. OVHcloud's table puts the b3-64 flex at +2.3%, against +14.9% for the standard b3-64. If you need more space, remote Block Storage is priced separately. I would check what moving an existing instance to flex involves before planning it.
- Do not stop instances to save money. OVHcloud's billing guide says a stopped or paused instance keeps being billed until it is deleted. When you delete one, check that its address does not stay behind on the bill.
- Open the project's billing page in the Control Panel. Under current usage, it shows an estimate of the next bill and lets you set an alert threshold. Set it at last month's total plus the add-ons from the list above.
- Before renewing a Savings Plan, price the renewal at 15% or 30% off compute, plus the disk and the address at full price. Not at the rate you signed.
OVHcloud's argument is that a bundled price hid what you were buying. Fair enough. The bill now shows exactly what nobody looked at before: the address nobody uses and the disk nobody filled.
Sources
- OVHcloud Blog, "Public Cloud: the end of the all-in-one plan" (August 25, 2026)
- OVHcloud Blog, "Public Cloud: Pricing changes as of October 1, 2026" (August 25, 2026)
- OVHcloud US, "Public Cloud: Our prices and packaging are changing" (read October 19, 2026)
- OVHcloud Help Center, "Information regarding Public Cloud billing options" (read October 19, 2026)
- OVHcloud, Public Cloud prices (read October 19, 2026)
- Forget About IT, "OVHcloud prix: les hausses de septembre et octobre 2026 sont confirmées" (August 11, 2026)
- AWS, Amazon VPC pricing (read October 19, 2026)
- AWS News Blog, "AWS Public IPv4 Address Charge + Public IP Insights" (July 28, 2023)
- Next, "OVHcloud augmente fortement le prix de ses VPS 2026 et IPv4" (February 23, 2026)
- MacGeneration, "RAMpocalypse : OVHcloud contraint d'augmenter de nouveau ses prix, jusqu'à 87 % cette fois" (August 11, 2026)
