OVH Raised Our Price 54%: How to Lock In Hosting Costs

If your hosting renewal just jumped by half, the way to lock in hosting costs is boring but it works: read the repricing clause in your current contract, write down the real date your rate is locked until, and quote your next provider on a fixed term — in writing — before you move anything. A 54% mid-term increase is a contract problem first and a technical problem second.

This blew up on r/webhosting after an OVH dedicated customer watched their price climb 54% in 11 months. The thread hit a nerve because energy costs have made every EU host nervous, and "indexation" language that nobody read at signup is suddenly doing real damage to monthly budgets.

So let's be practical. Here's how to tell whether your provider can legally do this, what energy surcharges can actually touch, and how to move off a ballooning renewal without a panicked 2 a.m. migration.

Can a host legally raise your price mid-contract?

Usually yes — if the contract contains a price-revision clause and the provider gives you proper notice, a mid-term increase is lawful in most EU jurisdictions. The catch is that "proper notice" almost always comes with a right for you to walk away without penalty.

The clause you're looking for sits under names like price revision, indexation, tariff adjustment, or révision des prix in French terms. It will tie your rate to something: a published inflation index (France uses Syntec for IT services a lot), an energy index, or just "at the provider's discretion with 30 days' notice." That last version is the one that bites, because it has no ceiling.

Under EU consumer and B2B rules, a material price change you didn't agree to specifically is a change to the contract. In practice that means the provider must notify you in advance, and you typically get a window to terminate without early-exit fees. If they raised the price and didn't offer you an exit, that's worth challenging in writing before you pay the new invoice.

What energy surcharges can and can't touch

An energy surcharge can only touch what your contract explicitly allows it to touch, and it has to be tied to a real, verifiable index — not a round number a provider likes.

During the 2022–2023 energy spike, several EU hosts added temporary energy line-items. That's defensible when it's a named surcharge, applied transparently, and reversible when wholesale prices fall. What's not defensible is baking a 2022 panic rate permanently into a 2025 renewal, long after spot energy prices came back down. Here's the context that matters: the TTF gas benchmark peaked near €300/MWh in August 2022 and has since settled into a far lower band — often in the €30–50/MWh range through 2024–2025. So if a 2025 renewal still carries a "crisis" surcharge sized for 2022, the index it claims to track is telling a different story. If your increase is justified "because energy," ask two direct questions:

• Which index are you tracking, and what's the current value? A real surcharge references something you can look up — and you can sanity-check it against public benchmarks yourself.
• Is it a separate reversible line-item or a permanent base-price rise? These are very different commitments, and providers sometimes blur them on purpose.

If the answers are vague, you're not looking at an energy pass-through. You're looking at a price increase wearing an energy costume. Say so, politely, in the email — a documented objection matters later.

How to read your contract for repricing clauses

Pull up your current terms and search for five specific things before you do anything else. This takes fifteen minutes and tells you exactly how exposed you are.

• The lock period: Is your rate fixed for the full term, or only the first billing cycle? A lot of "annual" prices only guarantee the first month.
• The adjustment trigger: Index-linked, discretionary, or anniversary-based? Index-linked with a named index is the safest for you.
• The cap: Is there a maximum yearly increase? If there's no cap, there's no ceiling — treat that as a red flag.
• Notice period: How many days before a change takes effect, and in what form (email counts; a buried dashboard notice often doesn't).
• Your exit right: Can you terminate without penalty when they reprice? This is your leverage.

Here's a worked example of the one that trips people up — the locked-until date. Say you signed a 12-month term on 1 March 2025, paid annually, and the contract reads "rate guaranteed for the initial term, renewing at then-current pricing." Your locked-until date is 28 February 2026, full stop. The anniversary renewal can reprice freely. Now take a different clause: "monthly billing, price may be revised with 30 days' notice." Your real lock is 30 days from any notice email — effectively nothing. Same provider, same box, wildly different protection. Write the actual calendar date on a sticky note: "locked until ___." If you can't fill that blank from the contract text alone, your rate isn't really locked, and that's your answer.

Keep the answers in a short note somewhere you'll find it at renewal. When you evaluate your next provider, ask these same five questions in the same order. At TPC Hosting we keep pricing plain and the terms readable precisely so you don't need a lawyer to answer them — and real engineers on chat will tell you straight what your rate is locked at, at any hour.

A calm migration plan when your renewal balloons

Don't rage-migrate. Set a date two to three weeks out, stand up the new environment in parallel, verify it works, then cut over on your terms. A hosting panic-move is how people lose data and sleep.

Here's the sequence that keeps you in control:

• Buy time. Reply to the increase in writing, use your exit right if you have one, and ask for a short extension at the old rate while you migrate. Providers often grant it — a churning customer is cheaper to keep calm.
• Audit what actually runs. List every site, database, cron job, mail flow, and DNS record. The surprises in migrations are always the things nobody documented.
• Build in parallel. Spin up the new server, deploy, and point a test hostname at it. Nothing in production moves yet.
• Lower your DNS TTL first. Drop records to 300 seconds a day before cutover so the switch propagates fast and rollback is quick.
• Freeze, final-sync, switch. Pause writes, do a final database and file sync, flip DNS, watch logs. For most sites the real downtime is minutes.
• Keep the old box for a week. Don't cancel until mail, forms, and payments are confirmed working on the new host.

If you're on dedicated or VPS, budget time for the stuff that doesn't live in a backup: firewall rules, mail reputation and SPF/DKIM/DMARC records, SSL certs, and any IP allowlists third parties hold for you. Those are the items that cause "it works but email bounces" the day after a move. TPC offers free migration and a 30-day window to back out, so you can run the new setup in parallel and confirm it's solid before you commit — EU-hosted and GDPR-friendly throughout.

How to lock in hosting costs going forward

The only reliable way to avoid a renewal shock is to choose terms with a real lock period and a capped or index-linked adjustment, and to re-check that language every year at renewal. Predictability is a contract feature, not a vibe.

When you compare providers, line up the terms that actually control your bill:

One honest trade-off: a longer committed term usually buys you a longer price lock, but it also narrows your exit. Pick the term length against how stable your traffic and stack are. If you're still growing fast, a shorter term with clear pricing beats a cheap three-year deal you'll outgrow in one. The goal isn't the lowest sticker — it's a number you can actually plan around.

And set a calendar reminder for 45 days before every renewal. That's enough runway to object, negotiate, or migrate calmly instead of eating whatever the new invoice says.

FAQ