VPS Bandwidth Explained: How Far 1 TB to 16 TB Actually Goes on a Romania VPS

If you're comparing VPS plans and the bandwidth column means nothing to you, here's the short answer: 1 TB per month is plenty for a normal website, blog, API or small app, but it's tight for a personal VPN you use daily, and it's not enough for video, large file downloads or heavy off-site backups. On IronBalkans plans, the allowance scales from 1 TB on Iron 1 (€3.99/mo) to 16 TB on Iron 4 (€29.99/mo), all on a 1 Gbps port — and for most buyers, RAM will run out long before bandwidth does.

This article gives you the actual math, real-world estimates by workload, and the commands to measure your own usage so you can pick a plan with confidence instead of guessing.

Bandwidth vs. port speed: two different numbers

Almost every VPS listing shows two traffic figures, and people mix them up constantly.

Port speed (1 Gbps) is how fast data can move at any given instant. It sets your ceiling for a single large transfer, a burst of visitors, or a backup upload.

Monthly allowance (1 TB, 4 TB, 8 TB, 16 TB) is how much total data you're expected to move in a billing month.

The gap between them is enormous. A 1 Gbps port moving data continuously for 30 days would transfer roughly 324 TB. So a 1 TB monthly allowance is about 0.3% of what the port can physically push. Put differently: using exactly 1 TB in a month is an average of about 3 Mbps sustained, 24/7.

That's not a trick — it's how the whole industry works. Fast ports exist so your peaks are fast: a 500 MB release tarball downloads in seconds, a traffic spike doesn't queue, a database restore doesn't crawl. Sustained usage is what the allowance covers.

What actually counts toward your allowance

Two things to check with any host before you pay:

1. Does it count outbound only, or both directions? Outbound (data leaving your server) is what most hosting traffic consists of, and many hosts count only that. If inbound counts too, workloads like VPNs and backup targets roughly double their consumption.
2. Is there a hard cap, a speed throttle, or a per-GB overage charge? These have very different consequences. A throttle slows you down; a per-GB charge turns a predictable bill into a surprise.

IronBalkans pricing is flat monthly with no metered per-GB billing and no renewal price increases, and every plan lists its traffic allowance up front. If you expect to run close to the edge of your allowance, the honest move is to ask before you buy — Telegram (@ironbalkansnews) and SimpleX are the support channels, and the FAQ covers the policy side. Any host that won't give you a straight answer about overages is telling you something useful.

How far 1 TB actually goes, by workload

These are estimates based on typical file sizes, not measurements of any specific server. Use them as planning ranges, then measure your own traffic (next section).

Websites, blogs, portfolios. If your average page weighs 2 MB — realistic for a modern, image-heavy WordPress site — 1 TB is roughly 500,000 pageviews a month. A well-optimized site at 500 KB per page pushes that toward 2 million. Most small and medium sites never come close. Bandwidth is almost never the limiting factor here; RAM and CPU are.

APIs and backend services. JSON responses are tiny. A 5 KB API response means 1 TB covers around 200 million calls. Unless you're serving media, you can ignore bandwidth entirely and size on CPU and memory.

Personal or team VPN. This is where 1 TB gets tight. All your browsing, streaming and downloads pass through the server, and if the host counts both directions, every gigabyte you consume costs two. A single person who streams video through their tunnel can burn 200–500 GB a month alone. For a full-time VPN exit for several people, plan on 4 TB or more. If you haven't set one up yet, our self-hosted WireGuard guide covers the build, and the self-hosted vs. commercial VPN comparison covers whether it's the right choice at all.

Video and large downloads. 1080p streaming runs roughly 2–4 GB per hour, so 1 TB is around 300 hours of viewing total, across all users. A small Jellyfin or PeerTube instance shared with friends will eat an allowance fast. Budget generously.

Off-site backups. Both directions matter. Pushing a 60 GB full backup weekly is about 240 GB a month before you restore anything, and restore tests — which you should be doing — add more. If your VPS is the backup target rather than the source, inbound traffic may count. Deduplicating tools help enormously here; see the restic and Borg backup guide.

Game servers, Matrix homeservers, Mastodon. Chat and federation traffic is small per message but constant, and media attachments dominate. A small Matrix or Mastodon instance typically lands in the low hundreds of gigabytes per month; federation with many large instances pushes it higher.

Tor relays and public proxies. These consume bandwidth by design, in the terabytes, and are governed by acceptable-use policy as much as by allowance. Check with the host first rather than assuming.

Measure it instead of guessing

If you already run a server anywhere, you can get a real number in five minutes.

Install vnstat, which reads kernel interface counters and keeps historical data:

sudo apt install vnstat
sudo systemctl enable --now vnstat
vnstat -m        # monthly totals
vnstat -d        # daily breakdown
vnstat -l        # live view

Give it a full day before trusting the daily figure and a full month for a real baseline. For an instant snapshot of cumulative counters since boot:

ip -s link show eth0

To see what is using the bandwidth rather than how much, nload gives you live throughput, iftop -i eth0 breaks it down by connection, and nethogs attributes it to processes. If nginx serves most of your traffic, your access logs already hold the answer — sum the bytes-sent field per URL and you'll usually find one oversized image or an unthrottled download link.

Two surprises worth checking for specifically: automated scrapers and bots hammering an endpoint, and a misconfigured backup job running far more often than intended.

Ready to pick a plan?

Bandwidth is the easiest spec to plan around because it scales predictably with your traffic, and it's rarely the one that forces an upgrade. Every IronBalkans plan runs on a 1 Gbps port with a dedicated IPv4, a /64 IPv6 block and DDoS protection included, so the only variable between tiers is how much compute, storage and traffic you actually need. Signup takes no email, no name and no ID — a random account ID and a recovery key — and deployment completes in under 60 seconds once your Monero, Bitcoin or Litecoin payment confirms. You can see the plans and allowances side by side and start on the smallest one.

Common bandwidth mistakes buyers make

Buying for peak instead of average. A traffic spike is limited by port speed, not by allowance. Don't buy 8 TB because you might get featured on a news site one day — buy for your sustained monthly average and upgrade if it changes.

Forgetting that a VPN doubles everything. This is the single most common underestimate. Your own consumption becomes your server's consumption, twice over if both directions count.

Serving large media directly from the origin. If you're distributing video, ISOs or big archives, putting a CDN or object storage in front of the server cuts origin bandwidth dramatically — and has the side benefit of keeping your origin IP out of direct view. Just be aware that a proxy alone doesn't hide your server; see the leak paths that expose an origin IP behind a CDN.

Assuming DDoS traffic counts against you. Attack traffic is filtered upstream on IronBalkans plans, and filtering is what determines whether a flood ever touches your port — but the precise accounting of scrubbed traffic is a question to ask a host directly rather than assume. What DDoS protection actually stops is a separate matter from what it bills.

Ignoring cheap wins. Brotli or gzip compression, modern image formats, correct Cache-Control headers and HTTP/2 typically cut a site's outbound traffic by half or more. That's free capacity, and it makes the smallest plan viable for far longer.

Honest trade-offs

Generous allowances look great in comparison tables, and they matter for exactly three workloads: VPNs, media, and heavy backups. For everything else — websites, APIs, dashboards, bots, small databases — the allowance on even an entry plan is far beyond what you'll use, and you should be choosing based on RAM and NVMe instead. Paying more for terabytes you never touch is the most common way people overspend on hosting.

The flip side: if you are in one of those three categories, running out mid-month is disruptive in a way that a slow CPU isn't. Measure first, then size with room to spare.

FAQ

Is 1 TB enough for a WordPress site? Almost always, yes. With reasonable image optimization and caching, 1 TB covers hundreds of thousands of monthly pageviews. Memory is the more likely constraint on a 1 GB plan.

Does uploading to my server count? It depends on whether the host counts inbound traffic. Ask before you buy if your workload is upload-heavy, such as using the VPS as a backup destination.

Is 1 Gbps shared or dedicated? Port speed is the capacity of your network interface; real throughput on any host also depends on upstream capacity and the route to your users. Test it yourself after deployment with iperf3 against a nearby public server, and check latency to your actual audience — Bucharest routing suits some regions better than others.

Can I upgrade if I run out? Moving to a larger plan is the normal answer, and plans are flat monthly, so you're never locked into an annual commitment you've outgrown. Because there's no card on file, you simply pay for the tier you want at the next renewal — see how crypto renewals work.

How do I know how much bandwidth I need before I have a server? Estimate from the tables above, then verify with vnstat in the first week. Start smaller than you think you need; upgrading is easy, and overpaying from day one is money you don't get back.

Get started

Bandwidth is worth ten minutes of arithmetic and no more than that. Work out your rough monthly average, add headroom if you're running a VPN or serving media, and then choose your plan on the specs that actually bite — RAM, vCPU and disk. Our Romania VPS sizing guide maps those to real workloads, and the pricing breakdown shows what's included at each tier.

When you're ready, create an account — no email, no ID, pay in Monero, Bitcoin or Litecoin, and your server is live in under a minute.