low cost VPS server: what does 'unlimited traffic' actually mean per provider?

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

1. 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.
2. Record the excess action as one of three separate fields: added charge, fixed speed cap, or temporary throttle.
3. 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.

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.

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.