VPS Plans HelpDesk Services MARKETPLACE Tutorials Support My Account
Home / Linux / How to Monitor VPS Health (CPU, RAM, Disk, Network)

How to Monitor VPS Health (CPU, RAM, Disk, Network)

A practical checklist of commands to monitor VPS health: CPU load, memory, disk space, network, and service status, with expected output and alerts to watch.

Views: 19 Unique: 15 Updated: 2026-03-20

What this is

This guide gives you a simple, beginner-friendly monitoring checklist for your VPS using standard Linux commands.

What it is for

  • Detect problems early (disk full, high load, low memory)
  • Confirm the VPS is healthy after updates/reboots
  • Troubleshoot slowness

Prerequisites

  • SSH access
  • Optional: sudo privileges for some commands

Step-by-step monitoring checklist

1) Quick overview: uptime and load

uptime

What it does: Shows how long the server has been running and the load averages.

What to look for: Very high load compared to CPU cores can mean overload.

2) CPU usage (live)

top

Expected output: Live process table. Look for processes with high %CPU.

3) Memory usage

free -h

What to look for: Focus on available. If it is very low and swap is heavily used, you may have memory pressure.

4) Disk space (most common VPS outage cause)

df -h

What to look for: If / is near 100%, services can fail.

5) Largest folders (when disk is filling up)

sudo du -xh / --max-depth=2 2>/dev/null | sort -h | tail -n 20

What it does: Finds the largest directories (depth 2).

Warning: This can take time on large disks.

6) Network basics: IP addresses

ip a

Expected output: Interfaces and IPs.

7) Network reachability

ping -c 4 1.1.1.1

Expected output: 4 replies and a summary. Packet loss indicates network issues.

8) Check listening ports (services exposed)

sudo ss -lntp

What it does: Lists TCP ports and the processes listening.

What to look for: Confirm expected ports (22/80/443) and watch for unknown services.

9) Service health (failed units)

systemctl --failed

Expected output: Ideally none.

Final verification (simple daily routine)

  1. Run uptime, free -h, df -h.
  2. If disk is high, investigate with du and logs.
  3. If load is high, identify the process with top/htop.
  4. Confirm services with systemctl --failed.

Conclusion

With these commands you can monitor the VPS health quickly and catch the most common issues before they become outages.

Back to category