Hetzner Cost-Optimized not available? Four options

When Hetzner Cost-Optimized is not available in Falkenstein, Nuremberg or Helsinki, try a direct API request first, because the Console may show outdated availability. If you need another plan, compare larger CX sizes with CPX and keep a 40 GB disk if you intend to return to CX23 later.

Hetzner's Cost-Optimized line uses older hardware, so its capacity is limited. The line includes x86 CX23 through CX53 and Arm64 CAX11 through CAX41. For an unavailable plan, the product page gives no restock date and says: "This product is currently unavailable. Please check back later."

The API can succeed when the Console shows no availability

Hetzner checks plan availability about every 15 minutes, according to its server FAQ. The Console loads the latest result when you open the form but does not refresh it automatically, so reload the page to see an update.

An API request tries to create the server immediately, without waiting for the Console's next check. As Hetzner's Katie explained in July 2026, it can therefore succeed before the Console shows the free capacity.

If Hetzner's hcloud CLI is installed and authenticated to your project, try this command for Falkenstein. Replace deploy-key with an SSH key already registered in the project:

hcloud server create \
  --name app-1 \
  --type cx23 \
  --image ubuntu-24.04 \
  --location fsn1 \
  --ssh-key deploy-key

For Nuremberg, use nbg1; for Helsinki, use hel1. A successful request creates a billable server, including a separately billed Primary IPv4 with the default network settings.

Before connecting, check in the Hetzner Console that the server is running, because a server ID alone does not confirm successful creation.

A larger CX can cost less than CPX22

CPX22 and CX23 both provide two shared x86 vCPUs and 4 GB RAM, but CPX22 costs €19.49 a month compared with €5.49 for CX23 at current new-order prices. If CX43 is available, its €15.99 monthly price gives you 8 shared vCPUs and 16 GB RAM for €3.50 less than CPX22.

The table shows EU new-order prices in euros, excluding VAT, from our pricing data verified on 24 October 2026. Primary IPv4, backups and other separately billed resources cost extra; the Hetzner Cloud price browser has the full catalogue and price history.

CAX11 is part of Cost-Optimized, but its Arm64 capacity pool is separate from x86 CX. It may therefore have capacity when CX does not, though CAX can also show limited availability. If you are moving an existing x86 installation, its snapshot cannot be restored onto Arm64, so you need compatible software and a data migration.

CPX (Regular Performance) and CCX (General Purpose) are separate product lines without the Cost-Optimized "Limited availability" badge. CCX also provides dedicated vCPUs.

Keep a 40 GB disk if you intend to return to CX23

A newly created CPX22 comes with an 80 GB disk, but Hetzner does not support rescaling to a smaller disk. You therefore cannot rescale that server to CX23's 40 GB plan, even if you have used less than 40 GB. Instead, you would need to migrate to another server or choose a plan with at least 80 GB, such as CX33.

Check the monthly cap before rescaling, as well as the target price. At the listed rates, a server kept on the same plan from the start of the month reaches its cap after about 26 days. In a 30- or 31-day month, that leaves roughly four or five days with no further compute charge. If a rescale raises the cap, hourly charges can resume, so a late-month change can cost more than leaving the server unchanged. You can explore the effect of monthly caps in the CloudTally demo.

If you need CPX22's CPU and RAM temporarily, start with CPX12 if it is available: one vCPU, 2 GB RAM and a 40 GB disk. Use --type cpx12 in the creation command above, then rescale it to CPX22 while keeping the disk. A rescale changes a server's size; choose CPU and RAM only in the Console, or pass --keep-disk with the CLI to prevent the disk from growing.

After a clean shutdown of the CPX12 server named app-1:

hcloud server change-type app-1 cpx22 --keep-disk

Once the rescale succeeds, restart the server with hcloud server poweron app-1. You now have CPX22's CPU and RAM at its normal rate, while keeping the 40 GB disk. When a rescale to CX23 is available, shut down cleanly again, run the following command and restart after it succeeds:

hcloud server change-type app-1 cx23 --keep-disk

Keeping the disk at 40 GB lets you target CX23 later, but the switch still depends on available CX capacity. Both rescale operations require downtime, and your workload must fit on 40 GB. If you temporarily choose a larger CX plan, the same restriction applies: creating CX43 directly gives you 160 GB, whereas upgrading an existing 40 GB server with --keep-disk retains the smaller disk.

Retry creation deliberately and stop after success

If a request fails because capacity is unavailable, you can retry once a minute for a set period. A 15- or 30-minute interval leaves longer gaps in which free capacity may be allocated to someone else. The shorter interval gives you more chances, although it cannot guarantee a server.

Retry the creation request itself, rather than only checking the availability display. Retry only capacity failures, and stop as soon as the command creates a server successfully or your deadline passes. If a request times out or gives an uncertain result, check the project's server list and recent activity before trying again, so you do not accidentally order multiple servers.

Hetzner's Cloud API reference gives a default limit of 3,600 requests per hour per project. One creation attempt per minute is 60 initial requests per hour, but CLI status checks and other tools also consume that project's allowance. Honour 429 responses and the rate-limit headers.

If you already have a CX server, deleting it means you may need one of these alternatives when you want it back. Keeping it switched off retains its allocation, but Hetzner still charges the normal server rate, up to the monthly cap. Before deleting or rescaling, compare that cost with the alternative you would need and any locked-in price you would lose. Hetzner Cloud billing explained covers the hourly charges and monthly caps.