Static route added but traceroute still follows default path

Minimal guidance for messy support realities.

Scenario

An admin adds a static route for a new subnet, yet client traffic continues using the default route.

Recommended Resolution Path

  1. Check route specificity, administrative distance, and whether the next hop is actually reachable.
  2. Inspect policy routes or SD-WAN rules that may override the static entry.
  3. Test from the firewall routing table and from a client behind it because paths can differ.
  4. If the route should apply only to one source network, document that clearly in the design.

Technician Notes

Document what changed, what confirmed the fix, and whether the issue points to a broader standards gap worth addressing for the client.