Routers decide between competing routes to the same destination using administrative distance (AD) — a trust score where lower wins. A floating static route is just a static route that exploits that rule on purpose: give it a high AD and it sits in reserve, ready to take over.

How it works

Normally a static route has an AD of 1, so it beats nearly any protocol-learned route. A floating static is given an AD higher than the route you want to use first. While the primary route is valid, it wins and the floating route is held back. When the primary's next hop goes unreachable and the route is withdrawn, the floating static becomes the best remaining option and is installed.

Configuring one

Classic dual-ISP example — a primary default route out the main link and a floating backup out a second ISP:

! Primary default route (default AD 1)
R1(config)# ip route 0.0.0.0 0.0.0.0 203.0.113.1

! Floating backup default route (AD 200 - stays inactive)
R1(config)# ip route 0.0.0.0 0.0.0.0 198.51.100.1 200

Run show ip route and only the primary appears. Drop the primary link and the AD-200 route immediately shows up in its place.

Choosing the AD value

The only rule: the floating route's AD must be higher than the route it's backing up (and below 255, which means "never install"). Backing up another static (AD 1)? Use 2+. Backing up OSPF (AD 110)? Use something above 110, like 130 or 200. The specific number is a style choice; the ordering is what matters.

Why use one

For a single backup path, a floating static is the simplest failover there is — no routing protocol to configure or troubleshoot across the backup link, just one extra line that quietly waits for trouble.