Automatic failover when cellular drops

Automatic failover means your router uses one internet connection as primary, keeps testing it, and switches to the backup on its own when the tests fail. For an RV, that’s usually cellular primary and Starlink backup, or the reverse. Starlink’s recommended health check for third-party routers is to ping a public IP such as 8.8.8.8 or 1.1.1.1 every 10 seconds and mark the link down after 5 failures in a row, which means the router decides in about 50 seconds. Then test it at home before you rely on it.

This guide assumes you already have a dual-WAN router wired with both links. If not, start with cellular first, satellite second or the travel routers page.

Failover rules in plain words

Why ping a public IP

A link can look “connected” (it has an address, the modem light is on) while nothing actually reaches the internet. Pinging a reliable address out on the internet tests the whole path. Starlink’s guide adds one warning: Starlink’s own DNS servers don’t respond to ping, so a check pointed at them fails even when the link is fine.

Many routers let you set two targets so one unreachable server doesn’t trigger a false failover. If yours does, use both 8.8.8.8 and 1.1.1.1.

Switch time

With Starlink’s recommended settings, the math is simple: 5 failures × 10 seconds ≈ 50 seconds before the router calls the primary down, then a few seconds to move traffic.

Should you make it faster? Trade-offs:

Starlink itself reroutes around brief obstructions very quickly; its help center says mobile dishes switch satellites within tens to hundreds of milliseconds. You don’t want your router reacting to blips the dish already handles. That argues for Starlink’s slower suggestion when satellite is primary.

What the switch feels like

• Web pages, email, streaming: a pause, then they carry on. Streams usually buffer through it.
• Video calls: usually drop and rejoin. A switch changes your public address, so the call app has to reconnect.
• VPNs: reconnect, often automatically.
• Downloads: some resume, some restart.

Starlink also notes that its connection uses a carrier-grade NAT address by default, so a few apps that need incoming connections may behave differently on satellite than on cellular. If something works on one link and not the other, that’s a likely reason.

Fail-back without flapping

Flapping is when the router bounces between links every minute because the primary keeps half-recovering. On a weak cell signal at the edge of coverage, it’s common. Three fixes:

1. Raise the recovery threshold. Require several good checks in a row before calling the primary “up”.
2. Add a fail-back delay. Wait a few minutes after recovery before switching back.
3. Turn fail-back off temporarily on a known-bad stretch and switch back by hand.

Testing it

Do this at home or in the driveway with both links working:

1. Note your public address on a “what is my IP” site.
2. Unplug the primary (or turn off the cellular modem).
3. Time it. You should see the router mark the primary down after about 50 seconds at the suggested settings, and the IP site should show a different address.
4. Make a test call on the backup to check quality.
5. Plug the primary back in and watch it return after the recovery threshold and delay.
6. Repeat with the backup unplugged to make sure the router doesn’t switch when it shouldn’t.

Which link should be primary: four cases

Many routers let you change priority without rewiring. At a tree-covered site with great LTE, put cellular first; at an open desert camp with weak LTE, put Starlink first.

Health checks on the cellular side

The same idea applies to the cellular link: ping a public IP, not the carrier’s own gateway, so the check tests the whole path to the internet. A cellular modem can hold a “connected” signal while data doesn’t move, especially at the edge of coverage. A public-IP check catches that; a signal-bars check doesn’t.

If your router supports it, keep the backup link’s health checks running too. Otherwise the router may fail over to a backup that has itself quietly stopped working.

Common mistakes

• Pinging Starlink’s DNS servers as the health target. They don’t answer pings.
• Load balancing two capped plans when you meant failover. Both allowances drain.
• No fail-back delay on a weak cell signal, causing constant flapping.
• Two Wi-Fi networks. If both the Starlink router and the travel router broadcast, devices may hop between them. Starlink says bypass mode turns off its router’s Wi-Fi; on Router 3 and Router Mini, leaving bypass mode needs a factory reset.
• Never testing it. The first real failover shouldn’t be during a client call.

What we don’t know

• Your router’s exact menus. Every brand names these settings differently. We haven’t tested routers, so we don’t walk through a specific model.
• How quickly your call app reconnects. It varies by app and version.

What to do next

If you haven’t chosen which link should be primary, read cellular first, satellite second. If the satellite side drops on drive days, dropouts on the highway explains why. To size the data plans on both sides, use the travel plan picker.

Research and spec-based analysis. We haven’t used Starlink in an RV, van or boat; this post is built from Starlink’s own documents, carrier pages and dated reports, cited above. Links to Starlink’s plan pages here use the site owner’s own referral link: the owner may get a referral reward if you order, and your price is the same. There are no affiliate links. Starlink and Roam are trademarks of Space Exploration Technologies Corp. Starlink RV USA is not affiliated with, endorsed by, or sponsored by SpaceX or Starlink. Spotted an error? Tell us.