low cost VPS server: what does 'unlimited traffic' actually mean per provider?
For the three checked low cost VPS server pages, “unlimited traffic” leads to three different published outcomes: IONOS says there are no extra traffic charges on its US VPS page, OVHcloud caps bandwidth at 10 Mbps after Asia-Pacific plan quotas, and netcup temporarily throttles the selected European VPS to 200 Mbps when traffic in the last 24 hours exceeds 2 TB. [evidence]
Evidence and source links
The check uses the official OVHcloud unmetered VPS page, IONOS US VPS page and netcup VPS 500 G12.5 product page. Each provider row keeps its own geography, plan context, exact traffic wording, excess-traffic treatment and verification date. All three pages returned HTTP 200 during the check.
Does unlimited VPS traffic mean there is no usage limit?
Not as a provider-independent rule. The checked IONOS page promises no traffic overage charge and a connection up to 1 Gbps. The checked OVHcloud page says traffic volume is unlimited but separately gives Asia-Pacific monthly quotas followed by a 10 Mbps cap. The selected netcup page calls the plan a traffic flatrate and gives a last-24-hour trigger followed by temporary throttling. The usable answer is the row for the exact region and plan, not the word “unlimited” by itself.
How this check classifies excess traffic
A provider passes the evidence check only when one official page supplies both the traffic claim and the treatment that applies when usage grows. “No extra charges,” a post-quota speed cap and a temporary rolling-window throttle are recorded as different outcomes. They are not collapsed into a pass/fail score.
Product scope stays attached to every statement. OVHcloud's exception is for its Asia-Pacific VPS regions; IONOS wording is from its US VPS offer; netcup's threshold is from the selected VPS 500 G12.5 European product view. A rule from one row is never transferred to another provider, region or plan.
No live server was load-tested. “Published treatment” means the current official page states the action. It does not prove how quickly a control system reacts, how long a throttle lasts in practice, or whether support may enforce separate acceptable-use rules.
Put the published limits on the same unit scale
The two speed-control rows can be normalized without pretending they are the same policy. For netcup, the official trigger is 2 TB across the last 24 hours. Using decimal SI units for an explicit example:
2 TB × 8 bits per byte ÷ 24 hours ÷ 3,600 seconds per hour = 185.19 Mbps average
The page says TB but does not define decimal TB versus binary TiB. Under the binary interpretation, the same arithmetic is 203.61 Mbps. This conversion is a reader aid, not a replacement for netcup's own 2 TB trigger or its stated 200 Mbps temporary throttle.
For OVHcloud's published Asia-Pacific post-quota cap, the decimal transfer ceiling implied by 10 Mbps is:
10 Mbps × 86,400 seconds ÷ 8 = 108,000 MB, or 108 GB, per 24 hours
Inference: both rows control speed, but they reach that state through different conditions. OVHcloud ties the cap to a monthly regional quota; netcup ties temporary throttling to the traffic measured over the last 24 hours. The calculation does not rank either provider.
A three-line check before buying
- Match the exact datacenter region and plan to the traffic sentence; do not reuse a global headline for an Asia-Pacific or Europe-specific row.
- Record the excess action as one of three separate fields: added charge, fixed speed cap, or temporary throttle.
- Save the source URL and check date with the plan. Recheck the same page before checkout because provider terms can change after this capture.
Inference: a workload with short download bursts and a workload with sustained transfer can encounter these published rules differently. That is why the table reports the trigger and action instead of declaring one provider “best.”
Provider-by-provider evidence table
Quoted wording is confined to this evidence area. Each conclusion is limited to what that provider's linked page says; no wording from one company is used to fill another company's row.
| Provider and exact view | Published traffic wording | Region or contract context | Published excess-traffic treatment | Extra traffic charge stated? | Checked |
|---|---|---|---|---|---|
| OVHcloud · Unmetered VPS | Yes, the traffic volume is unlimited. | UK English page. The exception names Mumbai, Singapore and Sydney. The traffic wording is not tied to one contract length. | After the plan-specific Asia-Pacific monthly quota: Beyond this, the bandwidth is capped at 10 Mbps.The page lists 1 TB for VPS-1/2, 3 TB for VPS-3/4 and 4 TB for VPS-5/6. | The page says unmetered plans avoid overage fees; the Asia-Pacific exception describes a speed cap rather than an added traffic price. | 2026-09-24 |
| IONOS · US VPS | Unlimited traffic up to 1 Gbps | US English product page. The traffic feature is presented across the VPS plan set; displayed offers use a one-year term. | No extra charges, no matter how much your traffic grows.The same page describes transfer through a connection up to 1 Gbps and gives no usage-volume trigger. | No extra traffic charge is stated on this page. | 2026-09-24 |
| netcup · VPS 500 G12.5 | Traffic Flatrate | English product view, no-preference Europe location, 24-month configuration, 2.5 Gbit/s interface. | If the average network traffic of the last 24 hours exceeds 2 TB, a temporary throttling to 200 Mbps is applied.The page says the throttle is lifted when the condition no longer applies. | No added traffic fee is stated in the captured network-traffic clause; the published action is temporary throttling. | 2026-09-24 |
Number source checklist
Every article number comes from one of the linked official pages or from the displayed unit-conversion formulas. The live requests to all three official pages returned HTTP 200 on the check date.
- A — OVHcloud: official unmetered VPS page. Source for the unlimited-volume statement, plan-specific Asia-Pacific quotas, the 10 Mbps post-quota cap and the absence of an overage fee in the described unmetered offer.
- B — IONOS: official US VPS page. Source for unlimited traffic, the connection up to 1 Gbps, the one-year displayed offer context and the no-extra-charge statement.
- C — netcup: official VPS 500 G12.5 page. Source for the 24-month European configuration, 2.5 Gbit/s interface, 2 TB last-24-hour trigger, 200 Mbps temporary throttle and lift condition.
- D — calculations: 8 bits per byte and 3,600 seconds per hour are unit definitions. The 24-hour, 2 TB, 200 Mbps and 10 Mbps inputs come from A or C. Decimal outputs use 1 TB = 1,000,000,000,000 bytes and 1 Mbps = 1,000,000 bits per second; the alternative 203.61 Mbps result uses 1 TiB = 1,099,511,627,776 bytes.
Downloadable comparison table
The CSV preserves the three provider rows with source URL, geography or contract context, claim, excess-traffic treatment and check date.
Download the unlimited-traffic CSVWhat people running these plans say in their own words
Reproduced verbatim and unedited, each with its discussion title, link and date. These are experience reports from people who pay for such plans or were throttled on them — not official provider wording and not this page's conclusion. Where a quote and the evidence table above disagree, the linked official page states the published rule and the quote stays as one person's experience.
How these are counted: one sample is one discussion thread, not one person. Several people replying to each other inside the same thread count once. The six quotes come from three threads: quotes 1, 2, 3 and 6 come from one thread about a provider cutting VPS traffic (November 2024); quote 5 comes from a thread about an account termination (December 2024); quote 4 comes from a thread about small Linux boxes (January 2026).
Reported in more than one thread: two things. OVHcloud plans being treated as unlimited in everyday use — quote 6 (thread one) and quote 5 (thread two). And “unlimited” or “unmetered” still ending in a speed consequence or a second set of terms — quotes 2 and 3 (thread one) and quote 4 (thread three).
Reported in one thread only, so not a pattern: quote 1's definition of “unmetered” as a billing statement rather than an absence of measurement; the 1 Mbps figure in quote 2; and the 24 TB and 100 Mbps figures in quote 4, which describe a different provider and not the three rows above.
Not found: no comparable first-person quote was found for the IONOS row or the netcup row. Those two rows stay on official wording only.
One number conflict, stated as it is: quote 2 reports an OVHcloud terms restriction of 1 Mbps, while the OVHcloud row above reports a 10 Mbps cap after the Asia-Pacific monthly quota from the UK VPS page. Two documents, two scopes, neither used to correct the other. If you need the number that governs your plan, the plan page and the terms have to be read together.
1 · What the word means for billing · pricing
“Unmetered” means “You will not be charged under normal circumstances based on the measurement of the data you use.” It does not mean that your traffic is literally not measured. They don’t put a specific hard limit because doing so both limits their own flexibility as a service provider and creates a target for abuse by users.
Where this gets stuck: “normal circumstances” is not defined on any plan page, so the overage cannot be priced from the marketing wording. Way around it: copy the excess-traffic sentence for your exact plan into your budget sheet, and leave the field unknown when the page states no trigger.
2 · The terms say something else · oversubscription
If you look beyond the marketing material, hoever, the ToS says: > OVHcloud reserves the right to restrict the VPS Service bandwidth to 1 Mbps (1 Megabit per second) until the end of the current billing period in cases of excessive use by the Client but it advertises with “unmetered”... so is a meter attached by which they can tell whether your bandwidth use is excessive or not?
Where this gets stuck: the plan page and the terms are two different documents, and only one of them carries a number. Way around it: save both sentences — the plan page claim and the terms restriction — before you pay, so a later throttle is not a surprise.
3 · What throttling feels like in practice · oversubscription
The systems *I* currently have at hetzner are, so far as I'm aware, on a “we don't charge for bandwidth but if you use a shitload you'll get throttled for the rest of the month” plan just like my ovh boxen. But I only pull dedis from hetzner; my VPSen are all ovh based. So please nobody expect my experience to generalise without triple checking the terms just like I did in the process of signing up for those systems.
Where this gets stuck: “throttled for the rest of the month” has no published threshold on the plan page. Way around it: take your own peak month's transfer volume to support and ask what volume triggers the cap, instead of inheriting someone else's workload.
4 · Unlimited with a number behind it · oversubscription
I have tried Upcloud for free and they are more expensive but they offer unlimited bandwidth (and the cap after 24 TB of free bandwidth/month is at 100 mbps)
Where this gets stuck: the limit is a speed, not a bill, so it never shows up as an overage charge you can budget. Way around it: divide your monthly transfer by the stated threshold first — this person's number is 24 TB and it belongs to Upcloud, not to the three rows above.
5 · Chosen over a capped provider · switching
Not OP but I use OVH which is better value and more reliable. OVH VPS’s also include unlimited bandwidth, by comparison hetzner imposes data caps and will nickel and dime you on just about everything. I run a few bandwidth heavy applications that do 10-20tb of traffic a month. If I was using hetzner I’d effectively be flushing cash down the drain
Where this gets stuck: this is a 10–20 TB per month workload judging a plan, and it says nothing about a light-traffic site. Way around it: compare against your own monthly transfer, not against this person's, before treating “unlimited” as the deciding factor.
6 · Unlimited as a reason to stay · pricing
I've only ever been on OVH and was surprised to discover a few years ago that bandwidth is not only unlimited but also costly at most other hosting companies (including cloud ones).
Where this gets stuck: one provider's habit is not another provider's term. Way around it: use this only inside the OVHcloud row; the IONOS and netcup rows above are each sourced from their own page and are not covered by it.
Do this next:
Open the exact plan for your deployment region and copy its trigger and excess action into your budget sheet before checkout. If the page only says “unlimited” and gives no excess treatment, leave that field unknown instead of assuming no fee or no throttle.