You launch a press campaign on Thursday. By Friday noon traffic is eight times normal — exactly the goal. Saturday morning the host suspends the site: "resource overuse." Or worse: next month's invoice shows €340 in "extra bandwidth" nobody budgeted. The site technically held; the plan did not.
The right question is not "how many GB do I have this month?" It is: what happens on the first unexpected spike, and who pays the gap between normal traffic and winning traffic?
Included, metered, fair use: three different regimes
Pricing pages deliberately blur these ideas.
Included traffic (flat plan). A monthly volume is bundled — e.g. 1 TB transfer or "unmetered bandwidth" on shared hosting. Beyond that: billing, throttling or termination per contract.
Metered traffic (pay-as-you-go). Every GB in or out is billed, often with tiered rates. Predictable at low volume; explosive if a video goes viral.
Fair use. No visible counter, but a clause allows slowing or suspending a site that "disrupts other customers." Typical of "unlimited" shared hosting.
| Model | Advantage | Campaign risk |
|---|---|---|
| Capped flat plan | Fixed budget | Overage or cut-off |
| Per-GB metered | Elastic | Unpredictable bill |
| Fair use | Simple day-to-day | Suspension without a number |
"Unlimited" often describes an invisible cap, not the absence of a limit.
What actually drives the bill
Web traffic is not a single "bandwidth" line.
Egress (outbound). Files, images, JSON APIs: the most billed item on cloud. A heavy media site can spend more on transfer than on CPU.
Requests and connections. Some CDNs or load balancers bill per million requests. A campaign with many light pages can hit that quota before GB volume.
Backend vs edge. If the CDN serves cache, the spike is absorbed at the edge. If every visit hits PHP/MySQL, the bottleneck is compute — not bandwidth.
Geographic zones. Cross-region or cross-continent transfer often costs more. A suddenly US audience on EU hosting can trigger surcharges.
Scenario A vs B: same campaign, two bills
Scenario A — "Unlimited" shared, €12/month. WordPress site, 500 visitors/day normally. TV campaign: 80,000 visits in 48 hours. Host applies fair use, limits PHP-FPM, site slows then is suspended. No extra invoice — but campaign lost.
Scenario B — VPS + metered CDN, 1 TB included then €0.02/GB. Same campaign, assets on CDN with 90% cache. Origin traffic: 120 GB, CDN egress: 800 GB. Bill: plan + ~€16 overage. Site held, cost controlled — if cache was configured before launch.
| Element | Scenario A | Scenario B |
|---|---|---|
| Model | Fair use | Cap + overage |
| Spike absorbed? | No | Yes (with CDN) |
| Campaign cost | €0 + lost opportunity | Plan + ~€16 |
| Prerequisites | None | CDN + cache configured |
The peak: the plan survives normal, not success
Here is what "unlimited" pages do not state clearly.
Marketing sells quiet Tuesdays. Your business plays out on peak Saturday.
Decide and move forward without blind spots
Before the next campaign:
- Read the traffic clause: cap, fair use, price per GB, suspension procedure.
- Model a realistic spike: history × safety factor + load test.
- Put a CDN or cache in front of static assets if the backend does not scale.
- Set an overage cap or billing alert at 80% of campaign budget.
Compare billing models in our compare tool and use-case offers under by use case.
Frequently asked questions
Is "unlimited bandwidth" truly uncapped?
Almost never. Fair use or CPU/RAM limits come before a bill. Read the terms.
What happens when you exceed included traffic?
Per-GB billing, throttling, suspension or forced upgrade — per contract. Get it in writing before launch.
Does CDN traffic count toward hosting?
Often not for integrated CDN, yes for egress to third parties or uncached origin traffic.
How do you estimate traffic before a campaign?
Historical peak × safety factor, media weight, load test, marginal cost per GB.
Next time a campaign wins, you do not want to discover the plan's limit in a suspension email. Ask now: what happens at GB number 1,001?
