Routing Table Coverage Analyzer
Compare entered routes with target ranges.
Routing Table Coverage Analyzer: inputs and results
Enter an IP address, CIDR prefix, or range. Then check its first and last address below.
Calculated Boundaries & ParametersReady
Key Capabilities
- •100% Client-Side: Zero telemetry or server latency.
- •RFC Compliant: Exact 32-bit and 128-bit integer precision.
- •Quick Copy: Instant access to CIDR, mask, and range bounds.
- •Cross-Platform: Works on desktop, tablet, and mobile browsers.
Related Planning, VLSM & CloudAll Tools
VLSM Calculator
Allocate differently sized subnets.
VLSM Allocation Validator
Check alignment, capacity, and overlaps.
Supernet Calculator
Find a covering parent prefix.
Exact CIDR Aggregator
Merge prefixes without adding addresses.
Route Summary Calculator
Summarize networks and identify included gaps.
DHCP Scope Calculator
Plan allocation boundaries within a subnet.
How Routing Table Coverage Analyzer Works?
The Routing Table Coverage Analyzer works by merging every entered route into a covered set, then comparing that set with each target range to find covered and uncovered addresses.
Enter the routes
Paste the routing table prefixes, such as
10.0.0.0/17and10.0.128.0/18.Enter the target ranges
Type the ranges that must be reachable, such as
10.0.0.0/16.Intersect and subtract
The analyzer computes the covered part and the uncovered part of each target.
Report coverage
Each target receives a coverage percentage and a list of uncovered CIDR blocks.
Routing Table Coverage Analyzer Formula
The Routing Table Coverage Analyzer formula is Coverage = |Target ∩ ∪ Routes| ÷ |Target| × 100 %, and Uncovered = Target − ∪ Routes.
Covered
Target ∩ ∪ RoutesReachable addresses.
Uncovered
Target − ∪ RoutesAddresses with no route.
Coverage
|Covered| ÷ |Target| × 100 %Per target.
Default route effect
0.0.0.0/0 covers everythingCoverage is then 100 % by definition.
Worked example: target 10.0.0.0/16
Routes : 10.0.0.0/17, 10.0.128.0/18 Covered : 10.0.0.0 – 10.0.191.255 (49,152) Uncovered: 10.0.192.0/18 (16,384) Coverage : 75 %
Routing Table Coverage Analyzer Conversion Table
The Routing Table Coverage Analyzer conversion table checks 5 target ranges against a 5-route table (10.0.0.0/17, 10.0.128.0/18, 172.16.0.0/16, 172.17.0.0/17, 192.168.10.0/24).
| Target | Covered | Coverage | Uncovered Blocks |
|---|---|---|---|
| 10.0.0.0/16 | 49,152 | 75.0 % | 10.0.192.0/18 |
| 172.16.0.0/15 | 98,304 | 75.0 % | 172.17.128.0/17 |
| 192.168.10.0/24 | 256 | 100.0 % | None |
| 192.168.0.0/20 | 256 | 6.3 % | 192.168.0.0/21, 192.168.8.0/23, 192.168.11.0/24, 192.168.12.0/22 |
| 10.0.64.0/18 | 16,384 | 100.0 % | None |
What is Routing Table Coverage Analyzer?
The Routing Table Coverage Analyzer is a tool that checks whether a set of routes reaches every address in one or more target ranges, and lists the addresses left without a route.
Missing routes cause partial outages that are hard to spot: most of a remote site works, but 1 subnet times out. Comparing the routing table with the full list of networks that must be reachable exposes those holes.
The analyzer ignores the default route on request, which shows coverage by specific routes only. That view matters for VPN tunnels and cloud route tables that do not use a default route.
What are the uses of Routing Table Coverage Analyzer?
There are 4 main uses of the Routing Table Coverage Analyzer, including VPN route checks, cloud route table audits, and migration validation.
Checking VPN route coverage
Every remote subnet must appear in the tunnel routes or proxy IDs.
Auditing cloud route tables
AWS and Azure route tables are checked against all peered networks.
Validating migrations
After a routing change, coverage of every site range is confirmed.
Finding missing summaries
Uncovered blocks show where a summary route stops short.