How billable Bandwidth is charged

IDC Connectivity and FTTP Residential Connectivity are charged on the traffic your Access Method carries, so a quieter month costs less. Both services use one method, and this page sets it out in full. Tunnel Connectivity and FTTN Residential Connectivity are flat-rate, and their price stands whatever the traffic.

Your port or your loop runs at its line rate throughout. Everything below decides the charge and leaves the speed alone.

Rates live on the service pages: Residential Connectivity pricing and IDC Connectivity pricing.

The two figures we read

Over each Measurement Period we read the traffic counters on your Access Method in your Measured Direction, the busier of Download and Upload, and take two figures from them.

  • p95 is the 95th percentile of your traffic. It sets aside the busiest 5% of records, about 36 hours of a 30-day Measurement Period, so bursts that add up to less than that leave it where it is.
  • Mean Bandwidth is the total traffic divided by the time measured. It follows what you sustain.

Your p95 says how wide your traffic gets. Your Mean Bandwidth says how long it stays there. The charge follows both, and the second is what separates an Access Method that bursts from one that runs flat out.

The method

Measured Bandwidth=p95, at most the largest p95 counted, rounded up to a whole Gbps, and at least 1 Gbps Load Factor=Mean Bandwidth ÷ Measured Bandwidth multiplier=Load Factor ÷ reference Load Factor, rounded up to a whole number, and at least 1 billable Bandwidth=Measured Bandwidth × multiplier

Your Measured Bandwidth is your p95 rounded up to a whole Gbps, and every Access Method carries at least 1 Gbps of it. Your Load Factor compares what you sustain against it. While that Load Factor stays within the reference Load Factor for your service, your multiplier is 1 and your billable Bandwidth equals your Measured Bandwidth. Each further step of the reference Load Factor adds 1 to the multiplier.

Where the two services differ

The method above is the same on both. Two parameters and the shape of the invoice are what change.

Parameter Residential Connectivity (FTTP) IDC Connectivity
reference Load Factor 5% 25%
largest p95 counted Line rate Line rate
Charged as Wholesale Access + Capacity for each Mbps + Service Fee for each Gbps of billable Bandwidth rate × billable Bandwidth

The reference Load Factor on FTTP sits lower because a substantial share of what you pay goes to the wholesale provider for the access loop and the aggregation behind it, so a Residential Access Method carries far more cost than an IDC one before any of our own capacity counts. On an FTTP invoice that share is visible: Wholesale Access is the tariff for your loop, Capacity covers the aggregation behind it, and the Service Fee is what AS30265 charges to carry your traffic.

What the multiplier does

One rule, read against each service's reference Load Factor.

Load Factor on Residential Connectivity (FTTP) Load Factor on IDC Connectivity Multiplier
Up to 5% Up to 25% 1×
Up to 10% Up to 50% 2×
Up to 15% Up to 75% 3×
Up to 20% Up to 100% 4×

An Access Method that bursts wide and rests keeps a multiplier of 1. An Access Method that holds its traffic near its Measured Bandwidth around the clock climbs the table, because capacity held around the clock is capacity nobody else can borrow.

Worked figures in dollars sit with each service: what common household traffic costs and what each multiplier costs for each Gbps.

When your billable Bandwidth changes

Your billable Bandwidth starts at 1 Gbps and is sold in whole Gbps. When it moves significantly, or in a consistent pattern, we may notify you and adjust your billing. Wherever we can we tell you first, so a month that is about to look different from the last is a conversation ahead of the invoice.

On a household line this stays theoretical. Reaching the second step on FTTP means sustaining roughly 50 Mbps every hour of the month. What that would actually take.

The authoritative wording, along with the Measurement Period and the rest of the billing terms, is in the Acceptable Use Policy.

An unhandled error has occurred. Reload ✕

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.