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.

Built by a network engineerCalculations run locally in your browserNo signup requiredNetwork information is not transmitted to our servers

Why summarize?

BenefitExplanation
Smaller routing tables4 × /24s become 1 × /22 — 75% fewer entries
Faster convergenceFewer routes to recompute when a link flaps
Reduced update trafficOne prefix in updates instead of many
StabilityA flapping subnet behind a summary does not propagate the flap
Memory savingsLess FIB/RIB memory consumed on edge routers

The summarization method

To find the summary route for a set of contiguous prefixes:

  1. Write all the network addresses in binary.
  2. Find the longest run of leading bits that are identical across all of them.
  3. That bit count is the summary prefix length.
  4. 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/24

Write 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 match

The 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).

SubnetsBits borrowedPrefix shift
21/24 → /23
42/24 → /22
83/24 → /21
164/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/22

OSPF ASBR summarization (external routes)

router ospf 1
 summary-address 192.168.0.0 255.255.252.0

EIGRP summarization on an interface

interface GigabitEthernet0/0
 ip summary-address eigrp 100 192.168.0.0 255.255.252.0

BGP aggregate

router bgp 65001
 aggregate-address 192.168.0.0 255.255.252.0 summary-only
 ! summary-only suppresses the component routes

Static summary route

ip route 192.168.0.0 255.255.252.0 Null0
! Then redistribute or advertise as needed

The 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

ApproachGranularityWhen to use
Specific summaries (/22, /20)MediumRegional/site aggregation
Default route (0.0.0.0/0)NoneEdge/Internet, stub sites
Full table (no summary)FullTransit/core where specifics matter

Related guides & tools

Technically Reviewed By

Senior Enterprise Network Engineer — 25+ years of IT and network infrastructure experience, including enterprise Cisco switching, routing, wireless, firewalls, VPN, network access control, SD-WAN, and large-scale network operations.

Last reviewed: 2026-09-02

Calculations are performed using standards-based formulas and verified against known reference values. All computation runs client-side in your browser.