OVHcloud moved its Public Cloud instances to an à la carte model from October 1, 2026. The hourly compute rate on the current B3, C3 and R3 ranges did not change. What changed is that two things that used to sit inside that rate — the local disk and the public IPv4 address — are now separate lines on the bill. For a small always-on instance that is not a rounding error: the same machine with the same resources now costs up to 21.9% more per month.
What is now billed separately
Two resources came out of the instance price on the third-generation ranges. Local low-latency storage is now charged at €0.0001458 per GB per hour, which OVHcloud rounds to about €0.11 per GB per month, or roughly €109 per TB per month. The capacity itself is still fixed by instance size — 50, 100, 200 or 400 GB — so this is not a new choice you make, it is a line that was previously folded into the headline number and is now shown on its own.
The public IPv4 address is the second line, at €0.0027 per hour, about €1.97 per month, and it is metered per second whether or not the address is attached to a running instance. That last detail matters for anyone who keeps spare addresses reserved between deployments.
Several things stayed where they were. The compute price on B3, C3 and R3 is unchanged, as is Block, Object and File Storage. Outbound traffic is still included, and network performance and anti-DDoS protection are untouched. Older generations — B2, C2, R2 and earlier — keep local storage inside the instance price, so the unbundling applies to the Gen-3 machines you would pick for a new deployment today.
What it does to the monthly number
Take OVHcloud's own worked examples. A b3-8 instance with 50 GB of local storage went from €37 to €45 a month, a 19.5% rise. A c3-4 with the same 50 GB went from €33 to €41, up 21.9%. At roughly €1.13 to the dollar that is about $51 and $46 respectively — call it eight euros, or nine dollars, added to each of those machines every month for resources they already had. Across the range OVHcloud puts the increase between 1.4% and 21.9%, and the pattern is clear: the larger the instance, the smaller the percentage, because a fixed €1.97 address and a fixed slice of disk are a bigger share of a €33 bill than of a €300 one. The small instances that run a single site, a bot or a staging box are the ones that feel it most.
There is an offset if you can commit. The Savings Plans that took effect on September 1, 2026 give 15% off compute for a 12-month commitment and 30% off for 36 months — but only on compute. The new storage and IPv4 lines are excluded from the discount, so a long commitment softens the compute side and leaves the two unbundled lines at full price.
What to do if you are choosing a server
The practical takeaway is that the instance price on OVHcloud's page is no longer the whole price. Before you compare a Public Cloud instance against a flat-rate VPS, add the IPv4 line and the local-disk line and compare the totals — which is exactly the kind of hidden line our methodology exists to surface, because a plan that looks cheaper on the compute row can lose once the address and the disk are counted.
Two concrete moves follow. First, check whether every instance actually needs a public IPv4: machines that sit behind a gateway or talk only over a private network can drop the address and the €1.97, and releasing reserved-but-idle addresses stops the per-second meter on them. Second, decide between the fixed local disk and Block Storage deliberately rather than by default, since the local tier now has a visible per-GB cost you can weigh against block volumes you can size and detach. For teams whose workloads are in Europe anyway, it is worth re-running the comparison across hosts with EU capacity — the catalog and the European VPS view make that a like-for-like check rather than a guess.
The change was announced on OVHcloud's blog on August 25, 2026 and takes effect for Public Cloud instances from October 1.