What Is Supernetting?
Supernetting (also called route aggregation or route summarization) is the process of combining multiple contiguous IP prefixes into a single, shorter prefix. For example, 192.168.0.0/24 and 192.168.1.0/24 can be aggregated into 192.168.0.0/23. This reduces the number of routes in routing tables, improving router performance and convergence time.
Route aggregation is a critical skill for network engineers working with BGP, OSPF, or any large-scale routing deployment. ISPs use supernetting to keep the global BGP routing table manageable — without aggregation, the table would grow far beyond what current router hardware can handle efficiently.
How Route Aggregation Works
The algorithm identifies prefixes that are binary "siblings" — two prefixes that differ only in the last bit of their network portion. When siblings are found, they merge into a single prefix one bit shorter. This process repeats until no more merges are possible.
The calculator also handles deduplication (removing duplicate or overlapping prefixes) and reports reduction statistics so you can see how many routes were eliminated.
When to Summarize Routes
- At OSPF area boundaries (ABR summarization) to reduce LSA flooding
- At BGP autonomous system boundaries to reduce the number of advertised prefixes
- On EIGRP routers using manual summary routes to control query scope
- When requesting provider-independent (PI) address space from a Regional Internet Registry
- During IP address plan design to ensure blocks are allocated in aggregatable ranges
Frequently Asked Questions
What is the difference between supernetting and subnetting?
Subnetting divides a large network into smaller subnets (longer prefix = more specific). Supernetting combines smaller networks into a larger aggregate (shorter prefix = less specific). They are opposite operations: subnetting adds bits to the prefix, supernetting removes bits.
Can I aggregate non-contiguous prefixes?
No. Only contiguous, properly aligned prefixes can be aggregated without covering additional address space. For example, 10.0.0.0/24 and 10.0.2.0/24 cannot be merged into a /23 because 10.0.1.0/24 sits between them. Merging them into 10.0.0.0/22 would include addresses you may not own or control, which could cause routing black holes.
Why does route aggregation matter for BGP?
The global BGP routing table contains over 1 million prefixes. Every additional route consumes memory on every BGP router on the internet. ISPs and enterprises are expected to aggregate their prefixes before announcing them. Many upstream providers filter prefixes longer than /24 for IPv4 and /48 for IPv6, so proper aggregation is required for your routes to be globally reachable.
What is a routing black hole?
A routing black hole occurs when a summary route advertises reachability to addresses that don't actually exist behind the advertising router. Traffic destined for those addresses reaches the router but has nowhere to go and is silently dropped. This commonly happens when aggregating prefixes that are not contiguous or when a component prefix is withdrawn but the summary route remains.
How do I summarize routes in Cisco IOS or Junos?
In Cisco IOS OSPF, use area 0 range 10.0.0.0 255.255.252.0 on the ABR. For BGP, use aggregate-address 10.0.0.0 255.255.252.0 summary-only. In Junos OSPF, use area 0.0.0.0 area-range 10.0.0.0/22. For Junos BGP, define an aggregate route under routing-options aggregate.