Every VPS plan has limits: CPU cores, RAM, disk and usually monthly bandwidth. Virtualizor shows how much of each you use, so you can spot problems early – a traffic spike, a runaway process or a disk filling up – and decide when to upgrade. This guide explains the graphs and how to investigate further inside the server.
Before you start
- Access to the Virtualizor panel and SSH access to the VPS.
- Your plan's limits, shown on the VPS overview.
Bandwidth usage
- Log in to Virtualizor and open your VPS.
- Open Bandwidth (or Statistics → Bandwidth).
- Review the monthly total compared with your limit, and the daily graph of inbound and outbound traffic.
Bandwidth counters normally reset monthly. What happens at the limit depends on your provider: traffic may be throttled to a lower speed, charged as overage, or the VPS may be suspended. Check your plan terms.
Performance graphs
Open Statistics / Performance to see CPU, RAM, disk I/O and network graphs over hours, days or months:
- CPU constantly near 100% means the VPS is overloaded or something is misbehaving.
- RAM close to the limit leads to swapping and slow responses, or processes killed by the out-of-memory killer.
- Disk I/O spikes often line up with backups or database jobs.
- Network spikes can be legitimate traffic, a crawler, or an attack.
Investigate inside the VPS
| Question | Command |
|---|---|
| What uses CPU and RAM now? | top or htop |
| How much memory is free? | free -h |
| Which disk is full? | df -h |
| Which folders are biggest? | du -sh /var/* | sort -h |
| Which process does disk I/O? | iotop |
| Live traffic per connection | iftop or nethogs |
| Monthly traffic history | vnstat -m |
Common causes of high usage
- Bots and crawlers hammering a website – check web server logs and block bad user agents or rate-limit.
- Compromised server sending spam or mining cryptocurrency – look for unknown processes and outgoing connections; consider a reinstall from a clean template.
- Large backups transferred off-site – schedule them at night and use incremental tools.
- Under-sized plan – if usage is legitimately high, upgrade. See how much RAM a VPS needs and VPS CPU cores explained.
Set up alerts
Virtualizor's graphs are for looking back. For alerts, install a monitoring stack or a lightweight agent; see VPS monitoring with Node Exporter and Grafana. Alert on disk above 85%, sustained CPU above 90% and memory pressure.
Troubleshooting
- Graphs empty: statistics may take a while to appear on a new VPS, or the provider disabled them.
- Panel bandwidth differs from vnstat: the panel counts at the host level, including traffic blocked by your firewall; small differences are normal.
- VPS slow but graphs normal: check for disk I/O wait (
waintop) and application-level issues.