Routing table analyzer
Paste a routing table to find duplicate routes, routes made redundant by a broader route, and next-hop conflicts.
Runs in your browser ยท nothing is sentRouting & topologyNew
Enter a routing table to see the result.
How to use
- Export or copy your routing table.
- Paste it into the tool, one route per line.
- Review the findings: duplicates, redundant routes and next-hop conflicts.
- Check the default route points to the gateway you expect.
Common scenarios
Find routes that became redundant once a broader summary route was added, and remove the ones that no longer add anything.
Spot a more specific route pointing to an unexpected next hop that overrides a broader route you expected to be in effect.
About this tool
Paste a routing table, one route per line ("10.0.0.0/24 via 192.168.1.1", with an optional metric), and the tool finds exact duplicate routes, more specific routes that are redundant because a broader route already sends the same traffic to the same next hop, and more specific routes that point to a different next hop than a broader route covering the same space (not necessarily wrong, since longest-prefix-match always resolves this, but worth a second look). It also flags the default route so you can confirm it points where you expect. Nothing is sent anywhere; the table stays in your browser.
๐ Your input stays in your browser and is never sent anywhere.
Frequently asked questions
What format does this expect?
"<network>/<prefix> [via <next-hop>] [metric <n>]", for example "10.0.0.0/24 via 192.168.1.1 metric 10", or network and mask separated by a space instead of a CIDR prefix. Both the next hop and the metric are optional.
Is a next-hop conflict always a mistake?
No. Longest-prefix-match means the more specific route always wins, so a conflict is not a routing error by itself. It is flagged because it is a common sign of a route that was added for a specific host or subnet and then forgotten, or of a change that was only partially rolled back.
Does this check live routes on my router?
No. You paste a copy of the table yourself (for example from "show ip route" or an equivalent command); the tool never connects to a device.
What to do next
Found a problem or have a suggestion? Tell us