Burstable billing¶

A network-capacity charging method that bills a high percentile of sampled traffic, allowing short bursts above commitment without pricing every peak as sustained demand.

Version: v2 · 2026-09-19 · History
Domain-specific #: 3558
Domain group: Social Sciences
Origin domain: Economics & Finance
Subdomain: Telecommunications Economics → Economics & Finance
Aliases: 95th-percentile billing

Core Idea¶

Sampling interval, inbound or outbound aggregation, percentile, commitment and overage formula are contract-specific, and discarded top samples are not free capacity if they cause congestion.^[1] Traffic rate is sampled throughout the billing period, observations are sorted, a small upper tail is discarded and the next value becomes the billable sustained-capacity statistic relative to the committed rate. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of telecommunications economics. It is the domain-specific identity fixed by the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test. This gives the entry an operational identity rather than merely a historical label.

A useful analysis keeps three layers separate. The constitutive layer says what must be true: the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit. The evidential layer asks what observation or proof warrants the claim: type the carrier, state every parameter and convention in the definition, test that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. The use layer asks what reasoning becomes available once the identity is established: recognizing and comparing instances of Burstable billing, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Conflating the layers is the most common source of scope inflation.

How would you explain it like I'm…

Throw Out the Biggest Bursts

Imagine paying for a water hose by how much water flows through it. Burstable billing checks the flow many times a month, lines up all the checks from smallest to biggest, and ignores the few very biggest ones. You pay based on the next biggest one, so a few short gushes do not cost extra, but lots of heavy use does.

Pay for Usual, Not Peak

Internet companies often charge businesses using burstable billing. Throughout the month, they measure how fast data is flowing at regular times. At the end, they sort all those measurements from lowest to highest and throw away a small top slice, often the top 5 percent. The next highest value is what you are billed on, compared with the speed you promised to pay for; going above that costs extra. This lets short bursts of heavy traffic go uncharged. But the exact rules, like how often they measure and which percent they use, depend on the contract, and those uncharged bursts can still slow down the network.

Percentile-Based Bandwidth Billing

Burstable billing is a method for charging for network capacity based on sustained usage rather than brief peaks. Throughout the billing period, the traffic rate on a circuit is sampled at regular intervals. At the end, the samples are sorted, a small top portion is discarded, and the next value, commonly the 95th percentile, becomes the billable rate. That rate is compared with the committed rate the customer signed up for, and usage above it is charged as overage. The details are set by the contract: sampling interval, whether inbound and outbound traffic are combined or billed separately, which percentile, the commitment, and the overage formula. The discarded top samples aren't really 'free,' since heavy bursts can still cause congestion.

Burstable billing charges for network capacity using a percentile of sampled traffic rate rather than peak or total volume. During the billing period the provider samples traffic counters on a circuit at a fixed interval, converts them to rates, sorts the samples, discards a small upper tail, and takes the next value, for example the 95th percentile, as the billable sustained-capacity statistic. This is compared with a committed information rate, and usage above the commitment is billed at an overage price. Nearly everything is contract-specific: the billing period and circuit, the sampling interval and rate calculation, handling of missing samples, whether inbound and outbound are measured separately or aggregated, which percentile is used, the commitment, the overage formula, and aggregation and audit rules across multiple ports. An important caution is that discarded top samples are not free capacity: bursts that fall in the ignored tail still load the network and can cause congestion.

Structural Signature¶

Carrier: the typed telecommunications economics carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets
Inputs or antecedent state: the exact telecommunications economics carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Burstable billing
Constitutive operation: Traffic rate is sampled throughout the billing period, observations are sorted, a small upper tail is discarded and the next value becomes the billable sustained-capacity statistic relative to the committed rate.
Invariant: the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit
Recognition test: type the carrier, state every parameter and convention in the definition, test that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
Output or consequence: recognizing and comparing instances of Burstable billing, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions
Failure boundary: the carrier is mistyped, the condition that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test

What It Is Not¶

It is not the whole field of telecommunications economics. The field contains many questions and methods that do not instantiate Burstable billing.
It is not its most familiar example. A canonical instance directly demonstrates that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
It is not the neighboring catalog concept Peak-rate billing. Peak billing charges the single maximum; burstable percentile billing ignores a declared small tail and charges a sustained high-usage estimate.
It is not a claim that every boundary case has one uncontested classification. a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Burstable billing must control the decision
It is not an unrestricted metaphor for any process that seems similar. Outside telecommunications economics, the vocabulary and validity conditions do not transfer literally.

Scope of Application¶

Burstable billing belongs to telecommunications economics and is useful where the analyst can specify the typed telecommunications economics carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit. The scope is broad within that domain but bounded by the need for the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.^[n1]

Definition and recognition. Determine whether a proposed instance satisfies the constitutive conditions rather than merely sharing terminology.
Construction or evolution. Track how the exact telecommunications economics carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Burstable billing are converted, constrained, or organized by Traffic rate is sampled throughout the billing period, observations are sorted, a small upper tail is discarded and the next value becomes the billable sustained-capacity statistic relative to the committed rate..
Comparison. Compare instances using carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior, without treating convenience measures as the definition.
Boundary analysis. Diagnose cases where a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Burstable billing must control the decision and state which convention or theorem controls the decision.
Downstream reasoning. Use the established identity to support recognizing and comparing instances of Burstable billing, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions while preserving the assumptions under which the inference is valid.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Burstable billing can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated. The disciplined statement is: given the exact telecommunications economics carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Burstable billing, the structure counts as Burstable billing exactly when the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit.

This format also separates identity from measurement. Empirical, computational, or documentary proxies support recognition only under declared validity and uncertainty assumptions; formal cases require proof rather than measurement. Measurements can be noisy, implementations can approximate, and proofs can use equivalent characterizations; none of those facts licenses changing the object being measured. When reports disagree, first check scope and convention, then data or proof, and only then interpret the disagreement as substantive.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Burstable billing. Burstable billing compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

The compression has a price. A single label can hide canonical, generalized, restricted, approximate, computational, empirical, and historically variant formulations of Burstable billing. Good use therefore carries a small declaration of assumptions alongside the name. The abstraction manages complexity when it reduces the state space of the question while keeping the failure boundary visible; it mismanages complexity when the label substitutes for that boundary analysis.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed telecommunications economics carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
Derive consequences. From the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit, infer recognizing and comparing instances of Burstable billing, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Record each assumption used so that a later change of setting does not silently preserve an invalid conclusion.
Test adversarial cases. Examine a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Burstable billing must control the decision and an object that resembles Burstable billing in purpose or vocabulary but does not satisfy its invariant is outside the class. A robust identity explains why the first is convention-sensitive and why the second is outside the class.
Compare and refine. Use carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior to compare legitimate instances, and refine the model when discrepancies reflect hidden variation rather than failure of the abstraction itself.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of telecommunications economics because they reuse the typed telecommunications economics carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Traffic rate is sampled throughout the billing period, observations are sorted, a small upper tail is discarded and the next value becomes the billable sustained-capacity statistic relative to the committed rate., and type the carrier, state every parameter and convention in the definition, test that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. A theorem, diagnostic, or modeling warning can travel when those roles remain literal. For example, the distinction between constitutive identity and a convenient observable transfers from A canonical instance directly demonstrates that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit. to An applied instance preserves the invariant under changed notation, scale, dataset, jurisdiction, or implementation..^[n2]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of Burstable billing, preserve its invariant, and derive only consequences licensed by the stated boundary—may suggest an analogy, but the domain-specific mechanisms, admissible evidence, and consequences do not come along automatically. The safe transfer procedure maps each role explicitly, checks the invariant again, and refuses the name when only a superficial resemblance remains.

Examples¶

Canonical¶

A canonical instance directly demonstrates that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit. The example exposes the carrier and directly tests that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit; changing incidental notation preserves the identity, while removing that condition destroys it. This example is canonical because every role can be inspected: the carrier is the typed telecommunications economics carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets; the operative rule is Traffic rate is sampled throughout the billing period, observations are sorted, a small upper tail is discarded and the next value becomes the billable sustained-capacity statistic relative to the committed rate.; the invariant is the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit; and the result supports recognizing and comparing instances of Burstable billing, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions.^[1] Changing incidental notation or scale leaves the structure intact, while removing the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit destroys the classification.

Mapped back: the typed telecommunications economics carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets → Traffic rate is sampled throughout the billing period, observations are sorted, a small upper tail is discarded and the next value becomes the billable sustained-capacity statistic relative to the committed rate. → the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit → recognizing and comparing instances of Burstable billing, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice¶

An applied instance preserves the invariant under changed notation, scale, dataset, jurisdiction, or implementation. The applied case qualifies only because the same invariant and boundary test remain literal under changed parameters or implementation. The applied case is not licensed merely by vocabulary. It qualifies because the same recognition test—type the carrier, state every parameter and convention in the definition, test that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases—can be run and because the same failure boundary—the carrier is mistyped, the condition that the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test—remains meaningful.^[n1] The case also shows why practical outputs should report assumptions, resolution, and uncertainty instead of a naked label.

Mapped back: declared instance → recognition test → boundary check → qualified use

Structural Tensions¶

T1: Axiomatic identity vs. operational recognition. The defining conditions may be exact while empirical or computational recognition is approximate. Neither pole can be removed without changing the analytical task. Diagnostic: Can the reviewer state both the exact condition and the evidence used to infer it?
T2: Local roles vs. global consequence. The mechanism is enacted through local relations, but the abstraction is usually valued for a global classification or prediction. Neither pole can be removed without changing the analytical task. Diagnostic: Does the claimed global result actually follow from the declared local conditions?
T3: Ideal form vs. finite representation. Theory states a clean invariant while data structures, measurements, or proofs expose only finite representations. Neither pole can be removed without changing the analytical task. Diagnostic: Would increasing resolution converge toward the same classification?
T4: Canonical convention vs. legitimate variants. A standard formulation supports communication, while variants may preserve the same core under changed assumptions. Neither pole can be removed without changing the analytical task. Diagnostic: Which role is invariant across variants, and which convention-specific conclusion changes?
T5: Compression vs. hidden assumptions. The name compresses a complex argument but can conceal prerequisites. Neither pole can be removed without changing the analytical task. Diagnostic: Can each downstream inference be traced to an explicit assumption?
T6: Autonomous residual vs. reduction to catalog neighbors. The candidate uses broader structures but adds an identity-bearing residual. Neither pole can be removed without changing the analytical task. Diagnostic: After subtracting the proposed parent and named neighbors, does the constitutive residual still support independent diagnostics?

Structural–Framed Character¶

The entry is structurally mixed but domain-framed. Its portable skeleton is type the carrier, apply the defining mechanism of Burstable billing, preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—Burstable billing, carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from telecommunications economics and cannot be replaced by generic systems language without losing the tests that distinguish valid from invalid instances.

This mixed character explains why the abstraction is reusable inside the domain yet does not meet the Prime bar. The structure organizes reasoning, but its claims still depend on domain-specific objects, evidence, and intervention semantics.

Structural Core vs. Domain Accent¶

The structural core consists of a carrier, Traffic rate is sampled throughout the billing period, observations are sorted, a small upper tail is discarded and the next value becomes the billable sustained-capacity statistic relative to the committed rate., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of Burstable billing, preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: Burstable billing, carrier, parameter, invariant, boundary, evidence, model, transformation, and application determine what counts as an admissible carrier, a valid transition, and successful evidence.

The abstraction therefore remains domain-specific. A cross-domain reuse that preserves only words such as 'balance,' 'cut,' 'sequence,' 'loss,' or 'simulation' is metaphor. Literal transfer requires the original role structure and diagnostics, which in this case remain anchored in telecommunications economics.

This entry is a kind of Measurement.

It remains its own entry because its identity is fixed by the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules.

Relationships to Other Abstractions¶

Current abstraction Burstable billing Domain-specific

Parents (1) — outgoing typed relations

Burstable billing is a kind of Measurement Prime

It remains its own entry because its identity is fixed by the circuit and billing period, inbound and outbound traffic counters, sampling interval and rate calculation, missing-sample handling, percentile such as 95^th, sorting and discarded upper tail, committed information rate, billable percentile and overage price and multiport aggregation and audit rules.

Hierarchy path (1) — routes to 1 parentless root

Burstable billing → is a kind of Measurement

Neighborhood in Abstraction Space¶

Burstable billing sits in a crowded region of the domain-specific corpus (38^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Economic & Financial Indicators (42 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25

Not to Be Confused With¶

Peak-rate billing. Peak billing charges the single maximum; burstable percentile billing ignores a declared small tail and charges a sustained high-usage estimate.
One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
Measurement or implementation of Burstable billing. A proxy or realization is evidence for the abstraction, not the abstraction itself.
Generalized Burstable billing. An extension qualifies only when its changed axioms and retained invariant are stated.

Notes¶

[n1] William B. Norton, The Internet Peering Playbook: Connecting to the Core of the Internet, DrPeering Press. ↩a ↩b

[n2] Internet2, Network Usage Measurement and 95^th-Percentile Billing Guidance. ↩

References¶

[1] Goldman, Alex. "Cogent's Latest Price Drop" , ISP PLANET, April 3, 2006. Accessed April 24, 2008. registry ↩a ↩b