Bandwidth billing on budget VPS plans is designed to be hard to reason about. Most buyers compare monthly transfer caps — “1 TB included” — without realising that the number that actually decides their bill is how the provider treats short bursts above the plan’s rate. A workload that quietly spikes for a few seconds a day can generate overage charges that a monthly cap never warned you about. This article explains burst and credit models and how to model your own worst case.
Three ways providers meter a burst
- Hard monthly cap: You get a pool (say 1 TB) and are throttled or charged once it is exhausted. Simple, but a single spike can consume a month’s allowance in an hour.
- Rate limit with burst allowance: You have a sustained rate (e.g. 100 Mbps) plus permission to burst above it briefly. Crossing the burst window triggers throttling or a charge.
- 95th-percentile billing: Charges are based on the top 5% of sampled bandwidth. This tolerates brief spikes, but a sustained ten-minute surge sets your rate for the whole month.
Why “unmetered” and “1 TB” can mean the same bill
A plan can advertise unmetered transfer and still charge you, because unmetered usually means “not capped at a total, but limited by rate.” If your app maxes the port for an hour during a traffic spike, you may hit a fair-use or rate-limit clause. Conversely, a metered 1 TB plan with generous burst headroom may cost you nothing extra. The lesson: read the *rate* terms, not just the total.
Modelling your worst case in five steps
| Step | What to compute |
|---|---|
| 1. Baseline | Average GB/day from your logs over a normal week |
| 2. Peak multiplier | Largest single-day ÷ average day (often 3–10x) |
| 3. Burst shape | Peak MB/s sustained during that day, and for how long |
| 4. Overage price | Provider’s per-GB rate beyond allowance |
| 5. Worst-case bill | (Peak-day GB − daily allowance) × overage price |
Run the numbers for your single biggest day in the last year, not an average one. Budget planning on averages is how surprise bills happen.
Buying burst headroom cheaply
- Push static assets to a CDN free tier. Images and scripts leave your VPS, so spikes hit the CDN, not your transfer allowance.
- Compress at the edge. Enable Brotli/gzip so the same content costs fewer bytes per request.
- Cap response sizes. Large media downloads are the usual overage culprit; route them to object storage with cheaper egress.
- Choose plans with burst tolerance. A slightly higher base rate is worth more than a big allowance with a hard cliff.
Bursts you don’t cause: backups, updates, and crawlers
Not every bandwidth spike comes from visitors. Overnight backups, OS and container image updates, and search-engine crawlers all pull real transfer, often at times when you are not watching. A full-site backup uploaded to remote storage can consume several gigabytes in one burst; a re-indexing crawler can hammer a small site for hours. Audit your transfer by source, not just by total, before blaming traffic. Scheduling backups inside your provider’s off-peak window and rate-limiting aggressive crawlers can remove overage risk that your visitor analytics never explained.
When to buy more transfer versus more transfer tolerance
There are two ways to solve a bandwidth problem: buy a bigger allowance, or buy better burst behaviour. They are not the same purchase. If your traffic is steadily high — a busy site with predictable load — a larger allowance is correct and cheap. If your traffic is spiky and mostly idle — a launch, a viral post, a batch job — you want a plan with high burst tolerance and a modest allowance, because you will rarely touch the total but will occasionally hit the rate. Choosing the wrong one of these two is the most common way budget buyers overpay for bandwidth they never use, or get charged for bandwidth they thought was included.
Reading the billing page like an auditor
- Is the allowance a total, a rate, or a percentile?
- What happens at the limit — throttle, charge, or suspend?
- Is egress to a CDN or specific regions metered separately?
- What is the per-GB overage rate, and is it billed in 1 GB or 100 GB increments?
If you are choosing between providers, put their bandwidth terms into the same table. The budget VPS hosting plans page lays out included transfer and structure so you can compare burst behaviour rather than just the headline number. For a first server, it also helps to know which plans include burst headroom by default on the affordable VPS comparison page.
Bottom line
Bandwidth cost is a function of burst shape, not just monthly total. Model your peak day, understand whether your provider charges on totals, rates, or percentiles, and move heavy media off your transfer allowance before a spike finds it. A plan with modest transfer but tolerant burst behaviour will often cost you less than a “generous” plan with a hard cliff hiding behind it.
