Quick answer: your transfer allowance is printed in the plan label you chose at order time, it resets with each billing month, and if you think you are going to reach it the right move is to open a support ticket before it happens, not after.
What a transfer allowance is
Every VPS plan includes a set amount of network traffic per billing month, usually measured in terabytes. When your server sends a file to a visitor, streams data to an API client, or pulls updates from a mirror, that traffic counts against the allowance. The counter starts again at the beginning of each billing cycle, and unused allowance does not roll over.
Where to find your allowance
Look at the plan label you selected when ordering. On most of our lines the allowance is part of the plan name itself. A Hetzner dedicated tier reads like "Transfer: 20TB", Vultr Cloud Compute tiers carry roughly 1 to 5 TB depending on size, Lightsail bundles print their allowance right in the bundle description, and GPU plans list 1 to 12 TB by tier. If you are comparing plans before buying, the labels in the store show the allowance for every tier before you commit.
Two of our lines work differently:
- Amazon EC2: transfer is a separate option you size at checkout, priced at $0.16 per GB per month on the order form. You choose how much you need rather than getting a fixed bundle.
- Alibaba Cloud (international and mainland China): these plans price network by peak bandwidth rate in Mbit/s instead of a monthly volume. You are paying for the speed of the port, not a data cap, with rates starting at $9 per Mbit/s on the international line.
Our custom Linux VPS line also sells monthly bandwidth as its own configurable component, so the allowance there is whatever you built.
Inbound, outbound, or both?
Providers do not all count traffic the same way. Some count only outbound traffic against the allowance, some count both directions, and the treatment of traffic between servers in the same datacenter varies as well. The plan label wording is the source of truth for your specific product, and if it is ambiguous for your use case, ask us before you architect around an assumption.
What happens if you approach the cap
This also varies by provider line. Depending on the platform your server runs on, exceeding the allowance can mean the port is throttled to a slower speed, or overage is billed. Because the consequences differ, our standing advice is simple: if your monthly usage is trending toward the allowance, open a support ticket while you still have headroom. We can tell you exactly how your line handles it and what the options are, which usually beats discovering the answer through a throttled port on a busy day.
Watching your own usage
The most reliable way to know where you stand is to measure on the server itself. On Debian and Ubuntu systems, vnstat is the classic tool:
apt install vnstat
vnstat -mThe first command installs the daemon and starts tracking; the second shows a per-month summary once data has accumulated. It counts from the server side of the port, so treat it as a close estimate rather than an exact mirror of the provider's own meter, but it is more than enough to spot a trend early.
Keeping usage down
- Enable compression for web traffic (gzip or brotli in your web server config).
- Put a caching layer or CDN in front of static assets so repeat downloads do not hit your port.
- Host large one-off downloads on object storage rather than the VPS itself.
- Check for chatty background jobs: an aggressive backup schedule or a misconfigured monitoring agent can quietly consume terabytes.
Need more?
Moving up a plan tier raises the allowance on the lines that bundle it, and on EC2 you can simply resize the transfer option. Whether a mid-cycle top-up is possible depends on the line, so if you need one, ask via ticket and we will lay out what your specific product supports.
Allowance versus port speed
Do not confuse the monthly allowance with the port speed. The port speed (how fast the server can move data at any moment) is a property of the plan and the platform; the allowance is the monthly volume budget. A fast port with a small allowance can burn through its budget in hours if you let it, and a modest port with a 20TB allowance can serve a surprising amount of traffic if the load is steady. Size the two together: bursty workloads care about the port, download-heavy workloads care about the allowance.
One more subtlety: traffic between two of your own servers counts like any other traffic unless the provider specifically excludes internal networking, and that exclusion differs per platform. If you are moving big datasets between your machines every night, it is worth asking us whether your line offers a private network path that does not touch the allowance.
