Upgrading your plan

Picking a bigger plan, what the pro-rated invoice pays for, and exactly which resources change immediately versus at your next full stop and start.

Your servers4 min read

On this page
  1. What you can upgrade to
  2. Downgrades
  3. Upgrading
  4. What applies immediately, and what waits
  5. Knowing it worked
  6. If something does not look right
  7. Related

Upgrading moves your service onto a bigger plan and resizes the server to match. You pick the plan, pay the pro-rated invoice, and the resources are applied for you. No ticket, and nobody has to touch the hypervisor by hand.

Servicesyour serverUpgrade

There are two ways in, and they land on the same page: Upgrade in the server's sidebar, or the Upgrade link on the Resources allocated card on the Overview tab.

What you can upgrade to

The page lists the plans above yours in the same product type and the same region. A VPS in Mumbai offers larger Mumbai VPS plans; a dedicated server in Singapore offers larger Singapore dedicated plans. Nothing crosses a region or a product family, because an upgrade changes the plan on the machine you already have; it cannot move that machine to another continent.

A plan is only offered when it is bigger on every resource: vCPU, memory, disk and transfer. That rules out sideways moves, where one plan has more cores but a smaller disk than another.

Each card shows the plan name, its monthly price, and the resources you will get. If nothing is listed, the page says so plainly: either you are already on the largest plan available online, or this service is not one that can be upgraded from the panel. Both link to Talk to sales, which opens a ticket.

The Upgrade page for a server on Plan A, with two larger plans in the same product type and region. Each is bigger on every resource, which is why it is offered. Marker 1 is step 1 under Upgrading below. Prices are left out of this example. Example view.

Downgrades

Downgrades are not available online, and this is deliberate rather than a missing feature. A smaller plan means a smaller disk, and a disk cannot be shrunk under data that is already on it without deciding what gets destroyed. That is not a decision to hand to a one-click button.

Open a ticket and we will work out what needs to come off the disk first, then move the plan.

Upgrading

  1. Pick the plan

    Select Upgrade to this plan on the plan you want. A dialog titled Upgrade to and the plan's name repeats what happens next, and Confirm upgrade submits it. Cancel backs out.

  2. Pay the pro-rated invoice

    The billing system works out the difference between what you have already paid for the rest of your term and what the new plan costs, and raises an invoice for it. Find it under Invoices and pay it as normal.

    Nothing changes on the server until this invoice is paid.

  3. The server is resized for you

    Once the payment lands, the new resources are applied automatically. This happens on its own within a couple of minutes of the invoice settling; you do not need to be on the page, and there is nothing to press.

  4. Stop and start the server when it suits you

    Extra vCPU and transfer are already live. Extra memory and disk are waiting for the next full power cycle: Shutdown, then Boot; see below.

What applies immediately, and what waits

This is the one part worth reading carefully, because half the upgrade lands at once and half of it waits for you.

ResourceWhen it takes effect
vCPUImmediately, while the server is running.
Transfer allowanceImmediately.
MemoryAt your next full stop and start.
DiskAt your next full stop and start.

Memory and disk cannot be changed underneath a running kernel, so they are queued and applied the next time the machine goes through a full power cycle. Nothing is lost while they wait, and there is no deadline: the server carries on with its old memory and disk until you stop and start it.

You confirm theupgradeYou pay theinvoiceThe resize isapplied for youA full stop andstart, when itsuits youvCPU and transferOld allocationNew: live at onceMemory and diskOld allocationQueuedNewNothing changes on the server beforethe invoice is paidA reboot from inside the guest doesnot countYou confirm the upgradeA pro-rated invoice is raisedYou pay the invoiceNothing changed on the server before thisThe resize is applied for youvCPU and transfer: live at onceMemory and disk: queued, old ones in useA full stop and start, when it suitsyouMemory and disk: liveA reboot inside the guest does not count
The order an upgrade lands in. Nothing moves until the invoice is paid; then vCPU and transfer change at once, while memory and disk sit queued until the machine is fully stopped and started again, on your schedule. Illustration.

Do it whenever the downtime suits you. There is no benefit to rushing, and no penalty for waiting.

Knowing it worked

When the resize is applied you get a notification in the panel saying the upgrade is live, and on Discord too if you have a webhook connected. It repeats the point above: CPU and bandwidth are already live, memory and disk arrive at the next full stop and start.

After the server has been stopped and started, the Overview tab shows the new allocation. That is the confirmation that the whole upgrade has landed.

If something does not look right

  • The invoice is paid but nothing has changed. Give it a few minutes. If the vCPU count on the Overview tab has not moved after that, open a ticket with the invoice number.
  • The memory or disk is still the old figure. Check the server has been through a real power cycle rather than a reboot from inside the guest.
  • The plan you want is not listed. It is either not larger on every resource, or it is in a different region or product family. A ticket can do what the panel will not offer.

Need a server, or a hand with one?

Pick a plan to deploy a server, or open a ticket in the panel. Support runs 24/7/365.