HA Billing
Billing structure and examples for IP Transit HA instances.
Last updated
Billing structure and examples for IP Transit HA instances.
Core principle: Physical resources (backbone bandwidth, public bandwidth) are billed independently; logical resources (IP addresses) are billed as a single unit.
HA Backbone Bandwidth
1 unit (primary + standby combined)
Billed at the sum of both links' bandwidth
HA IPT Public Bandwidth
1 unit (primary + standby combined)
Billed at the sum of both links' bandwidth
Public IP address block
Per address block
IPs are bound at the HA logical layer — each block is charged once
Example: Primary link 100 Mbps + standby link 100 Mbps, one /30 and one /31 public IP block
HA Backbone Bandwidth
200 Mbps
HA IPT Public Bandwidth
200 Mbps
Public IP (/30)
1 unit
Public IP (/31)
1 unit
Example: Primary link with 30 Mbps commit / 100 Mbps burst, standby link with the same spec, one /30 and one /31 public IP block
Case 1: Monthly traffic stays within the commit (combined 95th percentile of both links ≤ 30 Mbps)
HA Backbone Bandwidth (commit)
30 Mbps
HA IPT Bandwidth
30 Mbps
Public IP (/30)
1 unit
Public IP (/31)
1 unit
Case 2: Traffic exceeds the commit (example: combined 95th percentile = 70 Mbps)
HA Backbone Bandwidth (burst)
70 Mbps
HA IPT Bandwidth
70 Mbps
Public IP (/30)
1 unit
Public IP (/31)
1 unit
Burstable 95th Note
The system aggregates traffic data from both links and uses the combined 95th percentile value as the billable measurement. Only one commit fee is charged.
Last updated