Identify the VPS and keep its current order or upgrade details available. Resource statistics depend on the virtualization type and installed guest integration, so some readings may be delayed or unavailable.

1. Open List VPS and note the virtualization type shown for the server. Select Manage for the correct VPS ID.
2. Review its configured memory, CPU, disk allocation and assigned IP addresses. Check additional addresses or disks separately when your plan includes them.
3. Review the usage graphs and their time range. A short CPU spike does not carry the same meaning as sustained saturation.
4. Compare disk allocation with the filesystem size inside the guest. On Linux, read-only commands such as lsblk and df -h help show the distinction between a virtual disk and a mounted filesystem.
5. Compare the memory allocation with guest information and check whether swap or cached memory explains a perceived difference. Record the figures before requesting an upgrade or reporting a discrepancy.

Confirm that the panel allocation matches the active service and that the operating system recognizes the expected devices. After a disk upgrade, partition or filesystem expansion may still be required; do not format a disk to make the numbers match.

If an expected address or resource is missing, include the VPS ID and the relevant order in your support request. If a graph is blank, check guest integration and sampling before concluding that usage is zero. Never add an unassigned public IP to the guest configuration.

• Checking whether a Virtualizor VPS is running
• Opening the Virtualizor VNC console
• Changing the VPS hostname in Virtualizor
• Changing APIC, ACPI and VNC options in Virtualizor

• Virtualizor: Manage VPS