Headlines say 87 percent. OVHcloud's own tables say up to 158 on servers and 652 on memory. What rises, what does not, and why 1 October matters.
What OVHcloud Announced
OVHcloud is repricing its dedicated servers, and the reason is the one everybody in hosting has been watching since last autumn. In their own words, "DDR5 RAM now costs six times as much as it did a year ago", because the three companies that make memory have pointed their factories at the high-bandwidth kind that goes next to a GPU, without demand for the ordinary kind falling to match.
The company was explicit that it did not want a flat rise. Their teams went through the catalogue model by model, and the tables in their announcement show it: some configurations move by 5 percent and some by more than 150.
The Number in the Headlines Is Not the Number in the Tables
Coverage of this has settled on "up to 87 percent". That figure does appear in OVHcloud's announcement, next to one storage option, an eight-drive NVMe array going from 806 to 1,506 euros. It is not the ceiling for anything.
Here is what the configuration tables actually say, for new orders from 11 August 2026:
| Range | Increase |
|---|---|
| Advance, Gen 2024 | +16% to +131% |
| Advance, Gen 2026 | +25% to +158% |
| Game, Gen 2026 | +74% to +128% |
| Scale, Gen 2024 | +22% to +127% |
| Scale, Gen 2026 | +28% to +133% |
| High Grade, Gen 2024 | +5% to +42% |
| High Grade, Gen 2026 | +46% to +127% |
So the servers themselves go well past 87 percent in five of the seven ranges.
The Memory Options Are Where the Multiples Live
The configuration price is only half of it, and on some ranges it is the smaller half. Memory and storage options were repriced separately, from 1 July 2026, and those tables carry numbers of a different order.
On High Grade Gen 2024, RAM options rise between 162 and 652 percent.
Read that against the row above it. High Grade Gen 2024 has the mildest increase on the machine itself, 5 to 42 percent, and the harshest on the memory you put in it. A quote you took in June for that server with a large memory configuration is not 40 percent more expensive today. It is a different quote entirely.
This is the part worth checking on your own account, because it does not show up in any summary of the announcement.
Three Dates, and the One That Matters to You
OVHcloud published a schedule rather than a switch:
- 1 July 2026 - new rates for memory and storage options, on orders from that date
- 11 August 2026 - new configuration pricing, on new orders from that date
- 1 October 2026 - new rates on servers already running, taking effect on each subscription's renewal date
The first two have already happened and only affect what you buy next. 1 October is the one that reaches machines you are already running, and it does not arrive as a single invoice. It lands on each server when that server renews, so a fleet bought across a year will reprice across a year.
That detail is the practical difference between a nasty surprise and a plan. You can find out today which of your servers renew soonest after 1 October, and what each will cost when it does.
What Is Not Affected
Worth saying plainly, because the headlines do not. The Kimsufi, So you Start and Rise ranges are not affected, and neither are generations before Gen 2024.
If your workloads sit on older hardware or on the budget lines, this announcement does not touch you. That covers a lot of the small production servers people actually run.
Why This Is Not Only an OVHcloud Story
Hetzner repriced its cloud servers in June, with some lines up between 113 and 175 percent, which we covered in Hetzner more than doubled some cloud prices. Different provider, different month, same cause underneath.
OVHcloud's other post on this is blunter than most vendor writing about where it goes next. They say the market is not expected to find a new balance until late 2026, and that prices are not expected to return to historical levels before 2028, because that is how long new production capacity takes to come online. They also make a point that is easy to miss: paying more does not guarantee you get the parts. Supply is constrained on top of being expensive.
What to Do Before October
Three things, in order of how much they are worth.
Find your renewal dates. The increase arrives per server, at renewal, from 1 October. That list is the whole plan, and it takes ten minutes.
Check your memory configuration separately from your server. On some ranges the options rose several times more than the machine did. The total is not the headline percentage applied to your invoice.
Decide what actually needs that much RAM. This is the first time in years when trimming an over-specified memory configuration pays for itself immediately. A server sized for a workload it grew out of two years ago is now costing real money for the difference.
If you want a second pair of eyes on which of those servers are genuinely sized right, we manage infrastructure on OVHcloud and Hetzner and the renewal list is usually where that conversation starts.
Or read how we handle it in Infrastructure Management.
Related News
Hetzner More Than Doubled Some Cloud Prices Today And What To Do About It
On June 15, 2026, Hetzner repriced its cloud servers, and the dedicated and AMD shared vCPU lines (CCX, CPX) jumped 113 to 175 percent while the ARM and Intel-shared lines rose about 30 percent. Existing instances are protected, but a rescale reprices you. Here is exactly what changed and what to do.
Server & DevOpsThe DNS Root Key Changes on October 11. Is Your Server Ready?
On October 11, 2026 the DNS root starts signing with a new key-signing key, KSK-2024, for only the second time ever. Most sites need to do nothing. A server that validates DNSSEC through its own resolver must already trust the new key, and a one-minute check tells you.
Server & DevOpsGitHub Retires SHA-1 SSH, and Old Git Clients Feel It First
GitHub will stop accepting SHA-1 RSA signatures and one old key exchange over SSH, with brownouts on November 4 and December 9. HTTPS remotes are untouched and any OpenSSH from the last ten years already copes. The risk sits in tools that carry their own SSH code.