Why might a correctly configured static route not appear in the routing table?

Three main reasons: (1) the exit interface is down, (2) the next-hop IP (Internet Protocol) is unreachable (no connected route to reach it), or (3) a route with a lower Administrative Distance already exists for the same destination (floating static scenario).

* Why a configured static route isn't installed. *

Reason 1 — Exit interface is down (most common):

• The static route points to a next-hop IP that's reachable via an interface
• If that interface goes down → the connected route disappears → the static route depending on it is withdrawn
• Check: show ip interface brief — look for "down/down" or "administratively down"

Reason 2 — Next-hop is unreachable:

R1(config)# ip route 10.0.0.0 255.0.0.0 192.168.99.1

• If no interface on R1 has an IP in the 192.168.99.0/x range → R1 can't reach 192.168.99.1
• The route exists in the config but is not installed in the routing table
• Check: show ip route 192.168.99.1 — if "not in table," that's your problem

Reason 3 — Lower AD (Administrative Distance) route exists:

• A floating static with AD=5 won't appear if a normal static (AD=1) or OSPF (Open Shortest Path First) route (AD=110, but still lower than a floating with AD=130) exists for the same destination
• This is intentional behavior — the floating static is a backup
• Check: show running-config | include ip route shows all configured routes; show ip route static shows only installed ones

Diagnostic workflow:

1. show running-config | include ip route → Is the route configured?
2. show ip route static → Is it installed?
3. If configured but not installed → check interface status and next-hop reachability
4. show ip interface brief → Any interfaces down?
5. ping <next-hop> → Can the router reach the next-hop?

Go deeper:

• Administrative distance (Wikipedia) — the lower-AD-route-wins rule behind a floating static being suppressed.