An internal system is not functioning. The firewall administrator has determined that the incorrect egress interface is being used. After looking at the configuration, the administrator believes…

A static route will not be used if it cannot be installed into the firewall's routing table (FIB), which can occur if the associated egress interface is down or the next-hop is unreachable, preventing the route from becoming active.

While a duplicate static route with a worse administrative distance or metric will not be used, this implies another route *is* being used, which may not align with an administrator's belief that *a* specific route isn't being used.

If path monitoring is configured on a static route and the monitored destination becomes unreachable, the firewall will dynamically remove that static route from its routing table, causing it not to be used.

If a static route is explicitly disabled in the configuration, it is a deliberate administrative choice to not use it, rather than an operational reason why a seemingly active route is unexpectedly not being utilized.