Overview
Most ALYPOD Pods include a monthly bandwidth allowance, and traffic beyond it may be billed or rate-limited depending on your plan. This article shows how to check your usage in the ALYPOD Console and how to measure traffic from inside the server.
Before you begin
- Access to the ALYPOD Console at account.alypod.com.
In the ALYPOD Console
- Log in to account.alypod.com and open the ALYPOD Console.
- Select your Pod and open the Networking or Statistics tab.
- Graphs show inbound and outbound traffic over time. Most providers bill outbound traffic, so focus on the outbound figure.
- Check your plan's monthly allowance so you know how much headroom remains.
Measuring usage on Linux
- Install
vnstat, which keeps a persistent per-interface history:
bash
sudo apt install -y vnstat # Debian/Ubuntu
sudo dnf install -y vnstat # Rocky/AlmaLinux
sudo systemctl enable --now vnstat
- Wait a few minutes for data to be collected, then view it:
bash
vnstat
vnstat -d # daily
vnstat -m # monthly
vnstat -i eth0 -h # hourly, replace eth0 with your interface
- For a live rate, use
iftopornload:
bash
sudo apt install -y iftop
sudo iftop -i eth0
- To see which processes are generating traffic, use
nethogs:
bash
sudo apt install -y nethogs
sudo nethogs eth0
Reducing usage
- Serve static assets through a CDN so repeated downloads are cached at the edge.
- Use the private network (which does not consume public bandwidth) for traffic between your own Pods.
- Compress responses and enable HTTP caching.
- Find and stop runaway backups or sync jobs sending data off-site.
Troubleshooting
- Problem: Local counters and the Console disagree. Solution: The Console measures traffic at the edge of our network, including filtered and duplicated packets; treat it as the billing source of truth.
- Problem: Usage spiked unexpectedly. Solution: Check
nethogsfor the responsible process and review logs for loops or compromised services.
Related articles
- [DDoS protection overview]
- [Private networking between Pods]
