OVHcloud October 2026 Price Change: The Bill Checklist
OVH unbundles local storage and IPv4 from Public Cloud Gen3 on 1 Oct 2026. Bills rise 1.4-21.9%. Who is affected and how to cut the increase.
The short version
On 1 October 2026 OVHcloud stopped bundling local storage and a public IPv4 address into its Generation 3 Public Cloud instances. The hourly price of the virtual machine itself did not move. What changed is that two resources which used to sit inside that price now appear as their own billing lines. Same configuration, higher bill: OVH's own tables put the increase between 1.4% and 21.9% depending on instance size.
If you run B3, C3 or R3 instances, this is your event. If you run older B2, C2 or R2 instances, local storage stays included and you can stop worrying right now. The announcement came from two posts by Octave Klaba dated 25 August 2026, which left a five-week window to prepare. Plenty of teams used that window to do nothing. If that was you, here is the checklist you still need.
Who is affected and who is not
The unbundling splits cleanly by product line, and OVH was unusually specific about the boundaries:
- B3, C3, R3 (Generation 3 Public Cloud): local NVMe becomes a separate "Local Low Latency" line and the public IPv4 address becomes a separate line. Compute price unchanged.
- B2, C2, R2 and earlier generations: local storage remains included in the instance price. The October post covers Generation 3 only.
- Storage Optimized, Discovery, GPU, Metal and Gateway ranges: the IPv4 address is unbundled here too, on the same date, but without the storage change.
- Block Storage, Object Storage, File Storage: the high-availability remote storage classes keep their prices. This matters later, because they are the escape hatch.
One detail deserves its own paragraph: the IPv4 line is billed per second, including while the address is not attached to anything. A reserved-but-idle address costs the same 1.97 euros a month as one carrying production traffic. That is where the easy savings live.
The two new lines, precisely
Local Low Latency storage
€0.0001458 excl. VAT per GB per hour, which works out to roughly €0.11 per GB per month, or €109 per TB per month.
That is the entire rate card for the disk that used to be free with your instance. A 50 GB local disk adds about €5.32 a month. 100 GB adds €10.64. The 400 GB cap adds €42.57. Standard Gen3 instances carry 50, 100, 200 or 400 GB depending on size. Flex instances keep a fixed 50 GB local disk at every size, which becomes the single most useful fact in this article.
Public IPv4 address
€0.0027 excl. VAT per hour, about €1.97 per month, billed per second, attached or not.
The rate matches what OVH already charged for Floating IPs, so nothing exotic. The behavioral change is that nobody internally notices an idle IP until it shows up on an invoice. OVH built a dedicated section of the Manager for creating, attaching and releasing addresses, so the intent is clearly that you audit yours.
What your bill actually does
OVH published identical-configuration examples, ex-VAT, at 730 hours a month. The numbers for the smaller sizes:
- c3-4 (50 GB local): €33 to €41, +21.9%, the worst published percentage.
- b3-8 (50 GB local): €37 to €45, +19.5%.
- r3-16 (50 GB local): €48 to €56, +15.1%. Memory-optimized boxes get no special treatment.
- b3-64 (400 GB local): €299 to €343, +14.9%.
- b3-128 (400 GB local): €598 to €642, +7.5%.
- r3-1024 (400 GB local): €3,092 to €3,137, +1.4%, the mildest case.
The pattern is mechanical. Local storage is capped at 400 GB and the IP costs a fixed amount, so the extra euros are roughly the same across a family. On a small compute line that fixed add weighs a fifth of the bill. On a 3,000-euro instance it vanishes into rounding. If you are budgeting, do not average the range: model your exact SKUs.
Savings Plans: partial protection, read the fine print
Here is the part that surprised people. A Savings Plan subscribed before the new price list does protect two things: the instance price and the discount percentage, both locked until the commitment ends. It does not protect the two new lines. From 1 October 2026, local storage and IPv4 are billed at full rate even while your compute commitment is still running.
OVH's own worked example is worth copying into your budget spreadsheet. A c3-8 on a 12-month plan at −35%, subscribed 1 July 2026: €44 a month through September, then €56 a month from October 2026 to June 2027 while the commitment runs, then €69 a month if renewed under the new grid.
That new grid opened 1 September 2026 and it is leaner: 12 months at −15% or 36 months at −30%, applied to compute only. The 1, 6 and 24-month terms are gone. Klaba's explanation is blunt: with memory six times more expensive than a year ago and component forecasts that commit nobody beyond a few weeks, a heavily discounted three-year rate would be a bet on a market nobody can read. A modest discount you can keep beats a generous one you take back.
How to cut the increase back down
The design of the change is explicitly actionable: an IP that serves no purpose can be released, an oversized volume can be reduced. In order of savings per unit of effort:
- Release idle IPv4 addresses. Each one is about €2 a month, forever, attached or not. Go through the new Manager section and delete everything that is not serving traffic. This is free money.
- Move to Flex instances where the workload tolerates 50 GB local. Flex keeps the local disk fixed at 50 GB at every size, so the new storage line stays around €5 a month. OVH's own numbers: a b3-64 rises 14.9% as a standard instance and 2.3% as a Flex.
- Pool traffic behind a Gateway. A private-network architecture with one public IPv4 on the gateway, instead of one per instance, saves roughly €2 per instance per month. OVH's ten-instance example lands at €860.70 instead of €869.70. Honest note: that is a modest saving, but it compounds with cleanup and scales with fleet size.
- Price Block Storage against local NVMe. The high-availability Block Storage classes did not change in this round. If your data does not need low-latency local disk, moving it off Gen3 local storage converts an unpredictable line into a stable one.
What you cannot do is lock the old all-in price. Even a pre-October Savings Plan pays the new disk and IP lines from day one of the change. Anyone telling you otherwise has not read the walkthrough.
The dedicated server side of the same date
Two OVH changes share the 1 October 2026 cutoff, and the second one hits hardware. For Advance, Game, Scale and High Grade dedicated servers in Gen 2024 and Gen 2026, new-order catalog prices already moved on 11 August 2026, and existing servers pick up the new catalog rate at their next renewal on or after 1 October. Nothing changes mid-term; the bill arrives at commitment end.
The catalog moves are not subtle. GAME-1 Gen 2026 is listed at €139.99 moving to €279.99 for new orders, a doubling that OVH published row by row rather than as a single percentage. Scale and High Grade moves vary by model, so the only honest method is to open the official table for your exact SKU and map it against your invoice.
The exclusions matter just as much. Kimsufi, So You Start, Rise, and every dedicated generation before Gen 2024 are not in this reprice. If your invoice says Kimsufi, this entire event is noise for you. Do not migrate off a €10-a-month box because of a Game-range doubling you read about somewhere.
Why this is happening now
Klaba's stated reason, in one sentence from the announcement: buying memory costs six times more today than a year ago, and storage is following the same trajectory. AI datacenter buildouts have drained DRAM and NAND supply, and every provider that builds its own hardware is absorbing the same shock at the same time.
OVH is not an outlier here, and the 2026 pattern is well established. Hetzner raised CPX shared-cloud prices 144% to 154% on 15 June. netcup replaced its G12 generation with G12.5 on 22 September at 40% more on x86 VPS with half the disk. IONOS raised VPS+ regular rates on 18 September. OVH itself had already repriced its VPS range in June when the 2027 generation replaced the 2026 one. Meanwhile DigitalOcean, Linode, Vultr, AWS Lightsail and Hostwinds held every active plan at one price through the whole year, roughly 273 plans across the five of them. If your instinct says "everyone is raising prices", the data says European infrastructure builders are, and US clouds mostly are not.
Stay or leave: the actual decision
Run this sequence before your next renewal instead of guessing:
- Confirm the generation. B2/C2/R2 with included storage, or Kimsufi-class dedicated, means this reprice is not your event. Stop here.
- Count the exposed resources. Local GB per instance, Flex versus standard, public IPv4 count including unattached ones, and whether private networking is already in place.
- Apply the levers. Release idle IPs, evaluate Flex, check Block Storage pricing for data that does not need local latency.
- Map dedicated SKUs to the official tables. No single renewal percentage exists. Model your exact model number, or the math is fiction.
- Only then price the alternatives. EU builders like netcup still undercut US clouds at the same spec even after their own increase; a 2 vCPU / 4 GB netcup G12.5 costs about a third of DigitalOcean's equivalent. But migration has its own cost, and a 2% Flex increase rarely justifies it.
Bottom line: this is an unbundling, not a price hike on compute, and the levers OVH built in are real. Small Gen3 instances face 15% to 22% increases that shrink to low single digits with Flex and IP hygiene. Large instances barely notice. The people who should be actively shopping alternatives are the ones on in-scope dedicated ranges facing renewal, and only after they have read the table for their own SKU.