Request more CPU, RAM or disk

Resizing is a request rather than a button you press. Three reasons:

• it changes what you’re billed, so it shouldn’t happen silently
• it can be physically impossible — a host with no spare memory cannot grant more
• growing a disk cannot be undone, so it deserves a second pair of eyes

Ask for a resize

1. Go to Servers and open the server.
2. On the Resources card, choose Request resize.
3. Fill in only what you want changed. Each field shows the server’s current value, and anything you leave blank stays as it is.
4. Add a note if there’s context worth having — “running out of space on the database volume” tells us more than the numbers alone, and sometimes leads to a better suggestion than the one you asked for.
5. Send it.

You can have one open request per server at a time. If you already have one, the panel shows it with its status instead of a fresh form — we’ll come back to you on that one first.

What happens next

Our team reviews it and either carries it out or declines with a reason, which you’ll see on the request. If it’s declined, that’s usually capacity on the current host, and the reply will say what the alternative is — often moving you to a host with room.

After a resize lands

More CPU or memory may need a restart before the server uses it. Check the server’s Specifications card: if it shows the new values but the operating system doesn’t (nproc, free -h), reboot it from the power controls in the page header.

More disk needs a step inside the server. The virtual disk is bigger, but the partition and filesystem on it are not — until you extend them, df -h shows the old size. This is expected: follow Grow a disk inside the guest.

Sizing notes

Disks only grow. There is no shrink, on our side or in most filesystems. Ask for what you need plus reasonable headroom, not the largest number you can imagine.

Check what you’re actually short of first. A server that feels slow is often short of disk I/O or waiting on something external, not short of CPU. The Metrics tab shows CPU, memory and disk over time, which is a better guide than a guess.

If the panel shows memory near full, confirm it inside the server. Without the guest agent, the memory figure reflects what the host has allocated rather than what your OS is really using, and tends to read high on a perfectly healthy server. Check with free -h before asking for more.