Bandwidth, Monthly Transfer, and Overage
How port speed and monthly transfer allowances work on NoBull Networks plans, when the counter resets, and what happens if you exceed your allowance.
Two different numbers describe the network on your plan: the port speed (how fast data can move at any instant) and the monthly transfer allowance (how much data can move in a billing month). Mixing them up is the source of most bandwidth questions, so here is how each works and what happens at the edges. The Terms of Service remain the binding text.
Port speed#
VPS and VDS plans connect at 1 Gbps. Colocation ports are offered at 1 Gbps or 10 Gbps. Port speed is fixed for the plan: we do not sell burstable throughput that quietly exceeds the port at busy times, so the speed you see on the plan card is the speed you get, all month. If you need more throughput, that is a plan or port upgrade rather than a temporary boost.
Monthly transfer allowance#
Every plan includes a transfer allowance measured in terabytes per month (the "TB" figure on the plan card, counted as data transferred). Two details worth knowing:
- The counter resets on your service's recurring billing date, not on the first of the calendar month. Anniversary billing means each service has its own reset day; see Billing Cycles and Automatic Renewal.
- Usage is visible on the service page in MyNobull, so you can watch a busy month coming rather than discover it on an invoice.
What happens if you exceed it#
Your server is not cut off. Transfer beyond the allowance is billed as incremental overage at the rate published in the Terms of Service (currently $0.02 per Gb for the remainder of that monthly period), and the charge appears on your next invoice. If you regularly run close to the line, upgrading to a plan with a larger allowance is cheaper than paying overage; the upgrade is prorated and takes effect immediately.
Most unexpected overage comes from three places: a public mirror or download that got popular, backups being pushed off-server every night at full size instead of incrementally, or a compromised server participating in something it should not. Check all three before assuming legitimate growth.
Reducing transfer#
- Put a CDN or caching layer in front of static assets and downloads.
- Use incremental, deduplicating backup tools (restic, Borg) rather than full copies. See Backups, RAID, and Data Protection.
- Compress responses (gzip or Brotli) in your web server, and set sane cache headers.
- Watch for abuse: an open resolver, an unauthenticated proxy, or a bot-friendly upload form can move terabytes you never intended.
Colocation#
Colocation ports can be billed flat-rate or on a 95th percentile commit, which suits bursty traffic. That model is explained in Flat-Rate vs 95th Percentile Billing.
