Hetzner CX22 vs CX23 in 2026: Should You Migrate?

Short Answer

CX23 replaces CX22 for new Hetzner Cloud deployments, but it is not automatically a performance upgrade. Both tiers provide 2 shared vCPU, 4GB RAM, 40GB NVMe storage, and 20TB of included traffic. The practical difference is lifecycle: CX22 is being deprecated, while CX23 is the current cost-optimized plan — the same pattern Hetzner already applied when CX32 gave way to CX33.

If an existing CX22 server is stable, there is no reason to rebuild it purely for the newer number. For a new server, choose CX23. For a resize or migration, benchmark first and keep a rollback path.

CX22 vs CX23 Specs

Feature	CX22	CX23
Lifecycle	Deprecated Gen2 plan	Current cost-optimized plan
vCPU	2 shared vCPU	2 shared vCPU
RAM	4 GB	4 GB
Local storage	40 GB NVMe	40 GB NVMe
Included traffic	20 TB	20 TB
CPU selection	Not selectable	Not selectable
Best decision	Keep if stable	Use for new deployments

Hetzner’s deprecated-plan reference documents this lifecycle pattern. The current Hetzner Cloud catalog lists CX23 with the same headline resource amounts as the older CX22.

CX23 Pricing After the 2026 Adjustment

Hetzner’s price adjustment that set CX33 at €8.49/month applies the same logic one tier down: CX23 lists at approximately €4.29/month excluding VAT and IPv4 for Germany and Finland — close to, and in some regions slightly below, the original CX22 price of ~€4.35/month.

Cost item	Germany/Finland reference
CX23 server	~€4.29/month before VAT
Primary IPv6	No additional charge
Primary IPv4	Additional paid option
Billing	Hourly with a monthly cap

The exact invoice depends on location, currency, VAT, and network choices. Use the official Hetzner pricing notice as the source of truth, then verify the total in Console before creating the server.

For the original CX22 breakdown and Node.js sizing guidance, see the Hetzner CX22 pricing guide.

Is CX23 Faster Than CX22?

The plan name alone does not prove a speed increase. Hetzner classifies CX as shared-resource compute and states that CX instances may run on Intel or AMD CPUs. Customers cannot choose the CPU type, and the assigned hardware may change during a rescale.

That means a useful comparison requires workload-level measurements:

1. Record API latency, requests per second, CPU steal time, and disk latency on CX22.
2. Take a snapshot or application-level backup.
3. Test CX23 in the same location with the same image and application configuration.
4. Run the benchmark several times instead of trusting one burst result.
5. Compare sustained performance and monthly cost before moving production traffic.

Shared vCPU tiers are best for small APIs, bots, development environments, and bursty background work. Sustained CPU-heavy workloads should be compared with CPX or dedicated CCX plans — see the Hetzner vs DigitalOcean Node.js benchmark for a reference methodology.

Should Existing CX22 Users Migrate?

Keep CX22 when

• The server is stable and has enough CPU, memory, and disk capacity.
• Current pricing remains acceptable for the account.
• Rebuilding would introduce more operational risk than value.
• Monitoring shows no sustained resource pressure.

Move to CX23 when

• You are creating a new server rather than preserving an existing instance.
• Hetzner requires a current plan during a rescale operation.
• You are already rebuilding the stack or changing regions.
• A controlled benchmark shows equal or better results at an acceptable price.

Hetzner warns that some changes to legacy servers can move them onto current pricing. Read the pricing notice and verify the confirmation screen before applying a rescale.

Safe Migration Checklist

1. Export application configuration and secrets to a secure backup.
2. Back up databases independently; do not rely only on a VM snapshot.
3. Record DNS TTLs, firewall rules, cron jobs, and systemd services.
4. Create a snapshot or a parallel CX23 server.
5. Deploy the same application version and run health checks.
6. Benchmark CPU, disk, latency, and memory under realistic load.
7. Switch traffic only after database and application verification.
8. Keep the old instance until logs and monitoring confirm a clean cutover.

For the base Ubuntu, SSH, UFW, PM2, Nginx, and TLS steps, use the Hetzner CX22 setup guide. The process applies to CX23 as well.

Workload Recommendations

Workload	Recommendation
Small API or webhook	CX22/CX23 is enough; benchmark before paying for a bigger tier
Telegram/Discord bot + scheduler	Good fit at this tier; watch memory if you add workers
Production API with headroom	Consider CX33 if you expect to add processes soon
Sustained builds or encoding	Compare CPX or CCX instead of assuming CX23 fits

For a broader provider comparison, pair this with the best VPS hosting for Node.js developers guide.

Verdict

Choose CX23 for a new 4GB Hetzner server. Keep CX22 when an existing server is stable and migration has no measurable benefit. Treat CX23 as the supported successor, not as a guaranteed speed upgrade, because both tiers use shared resources and CPU assignment varies.

The best migration decision comes from current pricing, a reproducible workload benchmark, and a tested rollback plan — not the plan number alone.

FAQ

Is Hetzner CX22 still available?

It is being moved to Hetzner’s deprecated plan lineup. New deployments should use CX23 where available.

What changed from CX22 to CX23?

The lifecycle and current product generation changed, while the headline allocation remains 2 shared vCPU, 4GB RAM, and 40GB NVMe.

Should I resize a working CX22 immediately?

No. Keep it if it is stable. Resize when there is a concrete operational, availability, or pricing reason and after creating a backup.

Is CX23 suitable for a production Node.js API?

Yes for small to moderate traffic. For multiple processes or headroom to grow, compare it against CX33 before committing.