Route Summarization Explained
Route summarization (also called supernetting or route aggregation) is the practice of advertising a single, larger prefix in place of multiple smaller, contiguous prefixes. It shrinks routing tables, reduces update churn, speeds convergence, and conserves memory on routers. This guide shows how to compute a summary route by hand. Check your work with the CIDR calculator.
Why summarize?
| Benefit | Explanation |
|---|---|
| Smaller routing tables | 4 × /24s become 1 × /22 — 75% fewer entries |
| Faster convergence | Fewer routes to recompute when a link flaps |
| Reduced update traffic | One prefix in updates instead of many |
| Stability | A flapping subnet behind a summary does not propagate the flap |
| Memory savings | Less FIB/RIB memory consumed on edge routers |
The summarization method
To find the summary route for a set of contiguous prefixes:
- Write all the network addresses in binary.
- Find the longest run of leading bits that are identical across all of them.
- That bit count is the summary prefix length.
- The summary network address is the common bits followed by zeros.
Worked example: summarize four /24s
Summarize these four subnets:
192.168.0.0/24
192.168.1.0/24
192.168.2.0/24
192.168.3.0/24Write the third octet in binary (the first two octets already match):
192.168.0.0 → ...00000000.
192.168.1.0 → ...00000001.
192.168.2.0 → ...00000010.
192.168.3.0 → ...00000011.
^^^^^^^ ← 6 leading bits matchThe first 16 bits (192.168) plus 6 bits of the third octet = 22 matching bits, so the summary is 192.168.0.0/22. This covers 192.168.0.0 through 192.168.3.255 — exactly the four /24s, no more.
The block-size rule
A summary must cover a power-of-two number of subnets: 2, 4, 8, 16… The summary network address must be aligned to that block size. To summarize N subnets, N must be a power of two and the first subnet's network address must be a multiple of N × (subnet size).
| Subnets | Bits borrowed | Prefix shift |
|---|---|---|
| 2 | 1 | /24 → /23 |
| 4 | 2 | /24 → /22 |
| 8 | 3 | /24 → /21 |
| 16 | 4 | /24 → /20 |
When summarization does not fit cleanly
If your subnets are not contiguous or not a power-of-two count, one summary will not cover them exactly. You either (a) use multiple summaries, or (b) accept a broader summary that includes unused space (a "hole"). Example: 192.168.0.0/24 and 192.168.1.0/24 summarize to 192.168.0.0/23, but 192.168.1.0/24 and 192.168.2.0/24 do not — they need a /22 that also covers 192.168.0.0/24 and 192.168.3.0/24.
Configuration
OSPF area summarization (ABR)
router ospf 1
area 0 range 192.168.0.0 255.255.252.0
! Or with prefix:
area 0 range 192.168.0.0/22OSPF ASBR summarization (external routes)
router ospf 1
summary-address 192.168.0.0 255.255.252.0EIGRP summarization on an interface
interface GigabitEthernet0/0
ip summary-address eigrp 100 192.168.0.0 255.255.252.0BGP aggregate
router bgp 65001
aggregate-address 192.168.0.0 255.255.252.0 summary-only
! summary-only suppresses the component routesStatic summary route
ip route 192.168.0.0 255.255.252.0 Null0
! Then redistribute or advertise as neededThe Null0 black-hole trick
When you advertise a summary, install a static route for it pointing to Null0. This prevents routing loops: if a packet arrives for a subnet inside the summary that is currently down, the router drops it instead of forwarding it to a default route and looping it back.
Summarization vs default route
| Approach | Granularity | When to use |
|---|---|---|
| Specific summaries (/22, /20) | Medium | Regional/site aggregation |
| Default route (0.0.0.0/0) | None | Edge/Internet, stub sites |
| Full table (no summary) | Full | Transit/core where specifics matter |
Related guides & tools
- Route Summarization Calculator — calculate summary routes automatically
- Subnet Overlap Checker — verify networks don't overlap
- CIDR Explained — the foundation of prefixes
- VLSM Explained — right-sizing before summarizing
- IPv4 Subnetting Guide
- CIDR Cheat Sheet