> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/virtualization-platform/other/requesting-an-upgrade-of-a-vps.md).

# Requesting an upgrade of a VPS

How to request an upgrade of your Synteq VPS

### 1. Open a ticket

Start by going to our [billing panel](https://get.crunchbits.com/), and logging in. Then click on `Support` \[1] > `Open Ticket` \[2].

<figure><img src="https://2514446554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYlJjcmT7LgxrDfamjZ7v%2Fuploads%2FfuD5m7NXj7pqL2btXM1k%2FCleanShot%202025-11-30%20at%2021.31.46%402x.png?alt=media&amp;token=d9d149ef-5c1f-4133-98f2-7552af89a688" alt=""><figcaption></figcaption></figure>

Then click on the `Technical Support` department.

<figure><img src="https://2514446554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYlJjcmT7LgxrDfamjZ7v%2Fuploads%2F7Jkd82WgndIQzRLybhNe%2FCleanShot%202025-11-30%20at%2021.32.54%402x.png?alt=media&amp;token=98d2e04d-956f-4e02-bcce-c8448b1ba508" alt=""><figcaption></figcaption></figure>

### 2. Fill out the ticket

Afterward, please select the appropriate server in the `Realted Service` \[1] field, and fill out the `Subject` \[2], and the `Message` \[3] part as per the table below:

<table data-header-hidden><thead><tr><th width="138.46875"></th><th></th></tr></thead><tbody><tr><td>Subject [1]</td><td><pre><code>VPS Upgrade request
</code></pre></td></tr><tr><td>Message [2]</td><td><pre data-overflow="wrap"><code>Hello, 

I'd like to have my VPS \[IPv4: xxx.xxx.xxx.xxx] upgraded:
CPU: X vCPU -> XX vCPU
RAM: X GB -> X GB
Storage: X GB -> X GB
Bandwidth: X TB -> X TB

Thank you! </code></pre></td></tr></tbody></table>

<figure><img src="https://2514446554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYlJjcmT7LgxrDfamjZ7v%2Fuploads%2FgNi2D3hNeitcIia2VYVC%2FCleanShot%202025-11-30%20at%2021.42.03%402x.png?alt=media&amp;token=1799be15-48b0-41b9-b7bc-935c7dad0f7f" alt=""><figcaption></figcaption></figure>

On the message, the left part is your current amount, and the right amount is the new upgraded amount. Before submitting a ticket, please check that the specifications are within our predefined steps, as well as within the limits of our VPS [here](https://crunchbits.com/vps).&#x20;

### 3. Submit the ticket

After filling out your ticket, please click on the `Submit` button available at the bottom of that page.&#x20;

<figure><img src="https://2514446554-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYlJjcmT7LgxrDfamjZ7v%2Fuploads%2Fnv7xUZnn9l4awYBnuQlZ%2FCleanShot%202025-11-30%20at%2021.40.53%402x.png?alt=media&amp;token=494dd037-7b6b-43f3-bdfb-6bfe546d7133" alt=""><figcaption></figcaption></figure>

### 4. Pay the pro-rated invoice created on your account

Once we reply to you, we'll also add a pro-rated invoice to your account for the upgrade. Please pay it as outlined [here](https://docs.crunchbits.com/client-portal/billing/paying-an-invoice). Afterward, please notify us that the invoice is paid.

### 5. Restart your VPS

After you receive the green light from us that your VPS has been upgraded, please restart it from our Virtualization Panel as outlined here: [Power options on a VPS](/virtualization-platform/server-management/power-options-on-a-vps.md)&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://legacy.docs.synteq.com/virtualization-platform/other/requesting-an-upgrade-of-a-vps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.