Three different claims
| Claim | What it usually means | What to read instead |
|---|---|---|
| “1 TB per month” | A quota, with a reset boundary | What counts toward it, and what happens at zero |
| “Unlimited” | No hard cap, plus a fair-use policy | The policy: throttling thresholds, route restrictions, termination clauses |
| “Pay per use” | Billing tied to consumption | The unit price, the multiplier scope, and whether there is a floor |
These are three different commercial shapes. Choosing between them is a question about your usage pattern, not about which word sounds better.
What actually gets counted
- Direction: whether upload counts, and whether it counts once or is doubled.
- Route: multipliers applied to specific exits or regions.
- Protocol: some transports counted differently from others.
- Time: peak-hour weighting, if the terms mention it.
- Retries: whether failed or repeated transfers are counted. Usually they are — bytes left the server.
Find your real consumption before choosing
- Start with the smallest plan that covers a week of your normal use.
- Record the panel's quota at the beginning and end of that week.
- Compare against what you believe you used; the difference is the effect of the counting rule.
- Multiply by four for a monthly estimate, then add margin for a month with more streaming.
This is more work than reading a plan table, and it is the only estimate that applies to you.
The boundary matters as much as the size
| At the limit | Practical effect | What to ask before buying |
|---|---|---|
| Hard stop | Service ends until reset or upgrade | Whether a top-up exists, and its price |
| Throttle | Continues at reduced speed | What speed, and whether it applies to all routes |
| Multiplier increase | Continues, but consumes quota faster | Whether this is documented |
| Silent overage charge | Bill grows beyond the plan | Whether a cap exists |
Fair use, read as a policy
A fair-use clause typically reserves the operator's right to act on usage patterns it considers abnormal: sustained saturation, resale, or traffic shapes that affect other users. That is a legitimate operational concern and also a source of ambiguity, because “abnormal” is defined by the operator. Read whether the policy names thresholds, and whether action is throttling or termination.
What to record
- Plan name, quota, price, term, and the date you read the terms.
- The counting rule, including direction and any multiplier scope.
- What happens at the limit, in the provider's own words.
- Whether unused quota carries over, and the reset time zone.
- Your measured consumption for one representative week.
Scope
This page explains how to compare a quota with a policy claim. It names no provider, publishes no plan data, and makes no assertion about any operator's terms. Where the terms are silent, the honest record is “not stated” rather than an assumption.