Why VPS Prices Are Moving in 2026
The virtual server market is going through a realignment that simultaneously affects components, datacenter geography, and demand. Memory prices rose 250 to 300% between September 2025 and end of 2026, driven by AI infrastructure deployments. European providers, facing structurally higher energy and labour costs than their US counterparts, absorb part of this pressure but pass on the excess. Cost-optimised ranges are hit first: they rely on hardware generations kept in service specifically to contain prices, which mechanically caps available capacity.
- 2 September 2026 — Hetzner: the entire CX and CAX range switches to "not available" simultaneously across all datacenters; the CPX range remains orderable at a noticeably higher price point.
- 1 April 2026 — OVH: the 2026 VPS range (VPS-1 to VPS-6) increases by 40 to 67%; VPS-1 moves from €4.90 to €7.60 excl. VAT/month, VPS-4 from €26.00 to €43.50.
- 15 June 2026 — Oracle Cloud: Always Free Ampere A1 allocation cut from 4 OCPU / 24 GB RAM to 2 OCPU / 12 GB RAM with no public announcement; enforcement applied from 18 August 2026.
Hetzner: Sold Out Since 2 September 2026
Hetzner's CX range is built on previous-generation hardware deliberately kept in service to offer some of the most competitive prices in the European market. This policy implies a finite capacity that cannot be expanded at short notice. On 2 September 2026, stock trackers recorded the simultaneous switch of all CX and CAX plans to "not available" status across all datacenters. Restock windows do occur sporadically — sometimes for only a few minutes — as machines are terminated and returned to the pool, but no schedule is published. The CPX range, based on current hardware, remained orderable at a different price level. For an existing infrastructure running on CX, the immediate risk is one of renewal or extension: an active plan continues to run, but adding an extra node may encounter prolonged unavailability.
OVH VPS: +40 to +67% on Entry-Level Plans (April 2026)
OVHcloud announced in advance a pricing revision effective 1 April 2026 across the entire 2026 VPS range. Increases range between 40 and 67% depending on the plan. The stated rationale is the rise in component costs — primarily RAM — combined with energy costs at French and Canadian datacenters. Existing contracts were held at the old rate until their next renewal. This window offered time to evaluate alternatives without immediate pressure, but many customers discovered the increase at billing renewal, without having noticed or acted on the initial notification.
Oracle Cloud ARM: Silently Halved (June–August 2026)
Oracle Cloud's Always Free tier had offered since 2020 an Ampere A1 allocation of 4 OCPUs and 24 GB of RAM, distributable across instances. This allocation formed the backbone of many lightweight architectures: single-node Kubernetes, development instances, reverse proxies. On 15 June 2026, with no press release, no blog post, and no email to affected users, Oracle reduced this allocation to 2 OCPUs and 12 GB. Enforcement was deferred until 18 August 2026, when instances exceeding the new limits were automatically stopped. The issue is not the reduction itself — it is the complete absence of any notice, which caught off guard teams for whom the Oracle instance was a link in their infrastructure with no monitoring or redundancy planned at that point.
Stable criteria for evaluating a VPS host in 2026
Scroll the table
| Criterion | What to check | Warning sign |
|---|---|---|
| Guaranteed resources | Are vCPUs and RAM dedicated or shared (burst)? | Mention of "shared vCPU" or "burst" without a guaranteed floor |
| Modification policy | Can the provider change specs or pricing without notice? | No contractual notice clause (30 days minimum) |
| Datacenter location | Is the datacenter in Europe (GDPR, latency)? | US or Asia datacenter presented without transparency on data jurisdiction |
| Root access | Is root SSH access guaranteed without restriction? | Proprietary control panel mandatory, root SSH disabled by default |
| Dedicated IPv4 | Is a dedicated public IPv4 included or an optional extra? | Shared IPv4 or NAT by default, dedicated IPv4 billed as an unannounced surcharge |
| Uptime SLA | What is the contractual SLA and how is compensation calculated? | SLA insufficient or compensation in non-redeemable credits |
What You Are Really Looking for in a VPS in 2026
The three events described above reveal a gap between what many users thought they had purchased and what they actually had. A VPS whose resources can be reduced without notice is not a VPS in the contractual sense; it is a variable allocation. A range whose availability depends on the existing hardware pool offers no extension guarantee. What one looks for in 2026 is less an entry price than a set of invariants: resources guaranteed in writing, dedicated IPv4 included, datacenter located in Europe with an explicit GDPR clause, unrestricted root access, and a modification policy that binds the provider to sufficient notice to plan a potential migration.
How to Plan a VPS Migration Without Downtime
Compile a precise inventory of everything running: services, open ports, cron jobs, data volumes, inter-service dependencies. An incomplete inventory is the leading cause of omissions during a migration.
Subscribe to the new VPS alongside the old one, without cancelling immediately. Keeping both active throughout the migration allows an instant rollback.
Create a full snapshot of the source server before starting. This snapshot is your fallback in the event of a problem discovered after cutover.
Transfer data and configure the new server as a mirror. Test the application on the new server using its own test DNS name (for example, your-domain.com → new.your-domain.com) before any DNS switch.
Lower the DNS TTL to 300 seconds at least 24 hours before cutover. A high TTL at the time of the switch extends the propagation window and therefore the period during which some visitors still reach the old server.
Switch DNS while keeping the old server active. Monitor the logs of both servers for at least 2 hours to detect any requests still being routed to the old one.
Verify that the new server's dedicated IPv4 is correctly referenced in all dependent configurations: SPF, DKIM, reverse DNS, client firewalls, whitelist access.
Cancel the old server only after a confirmed period of stability, never on the day of cutover.
Troubleshooting: Classic Mistakes of a Rushed Migration
Here are the most common mistakes in a rushed VPS migration, and how to avoid them.
- Cancelling the old server before DNS stabilisation: propagation can take up to 48 hours, and visitors may still be routed to the old IP during that window.
- Forgetting to configure reverse DNS on the new server: mail servers check PTR/A consistency; missing rDNS causes silent rejections on outbound sends.
- Migrating without testing automated backups on the new server: an untested backup system is a non-functional backup system.
- Overlooking IPv4 in client firewall rules: if clients or partners have whitelisted the old IPv4, they will be blocked after cutover with no explicit error message.
- Assuming the same deployment scripts will work identically on a slightly different OS distribution: verify the exact target OS version before starting.
Before signing with a new host, check the general terms to confirm whether the advertised resources (vCPU, RAM) are guaranteed or shared in burst mode. Ask explicitly whether the provider can modify these resources without notice. A vague answer or one that refers to the terms without a specific clause is a negative answer.
Reassess Without Urgency, Choose on Durable Criteria
The three shocks of 2026 do not require any existing hosting customer to migrate in the coming weeks, unless their current resources are directly affected. They do, however, invite a reassessment of the implicit contract with the provider. A VPS with dedicated IPv4, guaranteed resources, and a European datacenter is not a premium category: it is the minimum definition of a service on which to build professional infrastructure. ServOrbit offers root VPS with dedicated IPv4, hosted in European datacenters, with guaranteed resources starting from 99 DH/month. Migration from an existing provider can be performed without downtime following the steps described above.
