A colocation quote says "$15 per Mbps, 95th percentile." A cloud invoice says "$0.09 per GB." A dedicated server listing says "20 TB included, unmetered after." None of these numbers can be compared to each other until you know what each one is actually measuring — and that gap is where 95th percentile billing gets misread most often, in both directions. This is what the four models actually do, where each one shows up, and the one traffic pattern that makes 95th percentile expensive instead of cheap.
What 95th percentile actually measures
The mechanic is older than most of the infrastructure it now bills. A provider samples your bandwidth every five minutes — 288 samples a day, roughly 8,640 across a 30-day month — then sorts all the samples from highest to lowest and discards the top 5%. Whatever sample sits just below that cutoff becomes your billed rate for the month (Wikipedia, "Burstable billing"; Kentik, 2026).
The consequence of that mechanic is the part worth internalizing: discarding the top 5% of a 30-day month gives you roughly 36 hours of unmetered headroom. You can burst to any level for a day and a half, spread across the month, and pay nothing extra for it (Wikipedia; major.io, 2026). That is the entire value proposition of the model — it absorbs short spikes without forcing you onto a higher committed rate, and it is why the model has been standard for internet transit and peering for over two decades.
Two details in the fine print change the bill more than the headline rate does. First, direction: some providers bill the 95th percentile of the higher of inbound or outbound traffic; others average the two. Billing on the maximum of the two directions, rather than the average, can push the effective rate meaningfully higher for asymmetric workloads — a video-heavy site with outbound-dominant traffic is billed differently depending on which convention the contract uses, so this is a line worth reading before signing, not after the first invoice. Second, what counts as traffic: some DDoS-protected bandwidth products exclude attack traffic from the measurement entirely and only meter legitimate post-scrubbing traffic — a distinction that matters enormously if you are DDoS-protected and assumed the meter includes everything hitting your network (Alibaba Cloud documentation, 2026).
If you have read our breakdown of [cloud egress pricing → /blog/cloud-egress-fees-comparison], the metered row is the one that piece covers in depth. This article covers the other three, which is where colocation and dedicated-server buyers actually spend their negotiating time.
The one traffic pattern that breaks the model
95th percentile billing rewards spiky traffic and punishes sustained traffic, and most people intuit it backwards.
Spiky is cheap. If your load is low most of the month with occasional bursts — a batch export job, a viral moment, a monthly report run — the discard window absorbs it. You are billed near your baseline, and the burst was functionally free.
Sustained is expensive, and here is the mechanic that surprises people: because the calculation only discards the top 5%, a workload that runs hot most of the time gets almost no benefit from the discard. Worse, a single unusually heavy day — a product launch, a Monday traffic pattern that repeats weekly, a marketing push — can set the billed rate for the entire month if it lands inside the 95% that doesn't get discarded, rather than the 5% that does (major.io, 2026; Wikipedia). Many sites see their heaviest single day of the week determine the whole month's bill, precisely because that pattern is common enough not to fall in the discarded top 5%.
This is the reverse of how metered billing works, where every byte costs the same regardless of when it moved. Under 95th percentile, when your traffic happens matters as much as how much of it there is.
Where each model actually shows up, and why
95th percentile dominates IP transit and peering because it was built for exactly that use case — bulk carriers with genuinely bursty aggregate traffic, where a fixed committed rate would either overcharge for headroom or undercharge for real peaks. It is also common in colocation contracts and DDoS-protected bandwidth, where the provider is reselling transit it bought the same way.
Metered per-GB dominates cloud hyperscalers because their cost structure and customer base look nothing like a transit carrier's — highly variable per-customer usage, no meaningful volume discard, and a billing system built to itemize everything. There is essentially no 95th-percentile cloud product at hyperscaler scale.
Unmetered and bundled dominate dedicated servers and VPS because the provider is selling you a port, not a byte count. A "20 TB unmetered after" server is really selling you a guaranteed connection speed with a soft usage ceiling attached for abuse prevention, not a precise 20 TB meter.
What no vendor will tell you
A provider that only offers a committed rate, with no 95th-percentile option, can be a signal about their network, not just their pricing philosophy. Practitioners who have run colocation deployments for years have flagged this directly: a datacenter that refuses to offer burstable billing, insisting on a flat committed rate instead, sometimes doesn't have the backbone headroom to absorb burst traffic across its customer base — burstable billing only works if the provider is genuinely oversubscribed in the statistical sense, banking on the fact that not all customers spike simultaneously (major.io, "Lessons learned: Five years of colocation," 2026). It's one of the first things INXY checks when qualifying a new bandwidth partner, and if a shortlisted provider won't do 95th percentile at all, ask why before assuming it's just a pricing preference.
The inbound-vs-outbound billing convention is the negotiating point nobody raises. A provider billing on the higher of the two directions, instead of the average, is charging more for the identical traffic pattern than a provider using the average convention — and this is rarely called out clearly in a sales conversation. For asymmetric workloads (heavy egress, light ingress, or the reverse), ask which convention applies before comparing quoted rates, because the headline $/Mbps number is not comparable across providers until you know this.
What breaks in production
Your own monitoring doesn't match the provider's meter. If you're graphing bandwidth with a different sampling interval, a different discard rule, or router counters instead of the provider's measurement point, your internal dashboard and your invoice will disagree — sometimes by a meaningful margin. Ask the provider for their raw sample export, not just the monthly summary number.
A recurring weekly pattern quietly becomes your permanent rate. A Monday-heavy traffic shape that repeats every week for a full month can settle into the 95th percentile as if it were your baseline, even though it only represents one day in seven. Reviewing daily, not just monthly, samples is the only way to catch this before it becomes a permanent line item.
"Unmetered" gets confused with "unlimited." A bundled dedicated server transfer allowance is almost always capped by port speed, and abuse thresholds exist even on plans marketed as unmetered. Sustained saturation of a "1 Gbps unmetered" port can trigger a conversation with the provider that a metered plan would never have caused, because metered billing has no concept of "too much," only "billed."
Billing method changes mid-relationship without much warning. Providers periodically retire or restrict specific burstable billing methods — Alibaba Cloud discontinued new sign-ups for its monthly 95th-percentile method for Anti-DDoS bandwidth in March 2026, moving customers toward the daily variant (Alibaba Cloud documentation, 2026). Check your contract's renewal terms for what happens if your specific billing method is deprecated.
How to pick correctly
Four questions, in order:
- Is your traffic genuinely spiky, or does it just look spiky on a monthly average? Pull daily, not monthly, granularity before assuming 95th percentile favors you. A workload that's "spiky" only because you've never looked at daily resolution is often sustained in disguise.
- What's the billing direction convention? Max of inbound/outbound, or average? This changes the effective rate for asymmetric traffic more than the headline number does.
- Do you need a hard ceiling, or genuine elasticity? Committed rate gives predictability at the cost of paying for unused headroom. 95th percentile gives elasticity at the cost of a bill that moves with your traffic shape.
- Is DDoS-protected bandwidth in the mix? If so, confirm explicitly whether attack traffic counts toward your meter. This is a materially different product depending on the answer, and it is not always obvious from the sales page.
Most of the disputes we see between infrastructure teams and providers on this topic aren't about the headline rate — they're about a billing convention nobody asked about until the first invoice. INXY brokers dedicated servers and colocation with the billing model matched to the actual traffic shape, not the default the provider happens to sell, because the "cheapest" $/Mbps number on a quote sheet is frequently not the cheapest bill once the direction convention and traffic pattern are accounted for.
If you're comparing quotes right now, send us the traffic profile — daily granularity, not monthly averages — and we'll tell you which billing model actually wins for your shape before you sign anything. [Request an infrastructure audit → /book-a-demo]. To see the underlying capacity options: [dedicated servers, colocation and racks → /hosting-solutions].
FAQ
What is 95th percentile billing? A method that samples your bandwidth every five minutes across the month, discards the highest 5% of those samples, and bills you at the rate of the next-highest sample. It gives roughly 36 hours a month of unmetered burst headroom, which makes it favorable for spiky traffic and unfavorable for sustained high usage.
Is 95th percentile billing cheaper than metered billing? It depends entirely on your traffic shape. For bursty workloads with real idle periods, 95th percentile is usually cheaper because the discard window absorbs the peaks. For sustained, consistently high traffic, metered per-GB billing can be more predictable, since 95th percentile offers little benefit when there's no meaningful low-traffic period to discard against.
Why did my bandwidth bill spike from one bad day? Under 95th percentile billing, a single unusually heavy day can set the billed rate for the entire month if it falls within the 95% of samples that aren't discarded. A weekly-recurring traffic spike, such as a Monday pattern, is especially prone to this because it repeats often enough not to land in the discarded top 5%.
What does "unmetered bandwidth" actually mean? It typically means there is no per-gigabyte charge up to the limit of your port speed, rather than truly unlimited transfer. The real ceiling is almost always the connection speed itself, and sustained saturation can trigger provider intervention even on plans marketed as unmetered.
Does 95th percentile billing measure inbound or outbound traffic? It depends on the provider's convention. Some bill on whichever direction (inbound or outbound) is higher in a given sample; others bill on the average of the two. For asymmetric traffic patterns, this convention can materially change the effective cost, so it is worth confirming before comparing quotes across providers.
Does DDoS attack traffic count toward my 95th percentile bill? It depends on the product. Some DDoS-protected bandwidth services explicitly exclude attack traffic from the billing measurement and only meter legitimate traffic that reaches your origin after scrubbing. This is not universal, so confirm it directly rather than assuming it from the marketing copy.
