CALCULATE / IP60BPS / MODULE
IPV6 SUPERNET
Aggregate multiple IPv6 CIDR prefixes into the smallest exact set and inspect the single containing prefix with exact 128-bit browser-local arithmetic.
EXAMPLES
Exact aggregation never adds IPv6 addresses. The separate single containing prefix can be broader than the entered set when gaps exist. No live route, BGP, ownership or reachability test is performed.
RESULT / EXPLAINED
Exact address math, with operational claims kept separate.
The network-planning tools perform deterministic IPv4/IPv6 arithmetic locally. They describe address-space relationships, not whether a network is deployed correctly.
What is exact
Network boundaries, containment, ranges, prefix lengths, masks and exact aggregation/splitting results come from deterministic address arithmetic.
Canonical output
Normalized network values remove host bits where appropriate. Containment means one calculated address range fully includes another; overlap means ranges intersect.
No live network validation
The browser does not confirm routing tables, VLANs, DHCP, firewall rules, ownership, reachability or whether the calculated prefix is appropriate for your deployment.
Before deployment
Use the arithmetic result as a planning input, then verify it against the real network design, routing/firewall policy and authoritative address allocation.
0BPS SHOWS MEASURED OR CALCULATED FACTS SEPARATELY FROM INTERPRETATION. WHERE A RESULT IS ADVISORY, ESTIMATED OR DESTINATION-SPECIFIC, THE LIMIT IS STATED IN THE TOOL.
REFERENCE / FAQ
COMMON QUESTIONS
What is the difference between exact aggregation and the containing IPv6 prefix?
Exact aggregation covers only the union of the entered prefixes. The containing prefix is one CIDR that covers the full span and can include additional addresses when gaps exist.
Does the planner add IPv6 addresses to the exact output?
No. Exact aggregation preserves the entered address union. Extra coverage is reported only for the separate single containing prefix.
Is any IPv6 prefix data sent to 0bps?
No. Parsing, aggregation and containing-prefix math are performed locally in your browser with BigInt.
The exact output merges only address space already present in the entered prefixes and never widens the union for convenience.
The separate single containing prefix is useful for planning but can include additional IPv6 addresses when gaps exist.
PRACTICAL / EXAMPLES
PUT THE NUMBER IN CONTEXT.
Short examples using the same units and assumptions as this module.
2001:db8::/49 plus 2001:db8:0:8000::/49 aggregates exactly to 2001:db8::/48.
2001:db8::/48 plus 2001:db8:2::/48 remain two exact blocks; the single containing prefix is broader and reports extra addresses.