Connectivity guide · Peplink Certified Associate

Peplink multi-WAN for RVs — when to bond, when to fail over

Serious travelers rarely trust a single WAN. Cellular is fast near towers; Starlink keeps you online where towers disappear. A Peplink mobile router turns those links into one coach network — bonding and/or failover as configured — not a pile of hotspots fighting over DNS.

Active corridor: Montana · Wyoming · Idaho · Washington — case-by-case beyond.

Field notes

United Mobile RV is a Peplink Certified Associate. We install routers like electrical work: mounted, sealed, fused, and integrated so the system survives washboard roads. Firmware and InControl come from peplink.com only — we do not redistribute proprietary binaries. This guide will not promise miracle uptime. Trees, canyons, dead outdoor cell, and 12V brownouts still win.

Who this is for

Right place if you

Work or stream from the coach and cannot afford one carrier dropping the whole day. Already run (or plan) both cellular and Starlink and want them coordinated. Need a travel-safe install: SIM trays accessible, Ethernet routed cleanly, power fused into coach DC.

Maybe not yet if

You only camp near strong towers and a phone hotspot is enough. You only need occasional Starlink at a fixed clear-sky site. Your pain is zero outdoor cell — that is coverage first; a router cannot invent RF. Pair with the weBoost and Starlink guides.

Bonding vs failover (honesty)

SpeedFusion is Peplink’s multi-WAN toolkit. On a given chassis and license it can mean bonding and/or failover as configured — those are not synonyms.

Failover

One WAN stays primary. When Health Check declares it dead, traffic moves to the backup. Upside: simple mental model. Cost: no combined capacity; cutover can interrupt sessions; a flapping primary can thrash if thresholds are wrong.

Bonding

Multiple healthy WANs participate so capacity and resilience improve when the design and license support it. Upside: better use of two decent links. Cost: more complexity; needs healthy multiple WANs to matter.

Both when the site needs it

Many serious builds use failover as the safety net and bonding where licensed for day-to-day resilience. Valid — as long as you hear the real policy, not a marketing diagram.

What we will not claim

Miracle uptime. “Bonding” on a failover-only config. That Peplink invents outdoor cell or clear sky. Nationwide SLA vibes. If dropouts persist after a clean install, start at WAN flapping / Starlink offline troubleshoot.

Diagnostic-first before you buy

Travel pattern

Nights near towns vs forests/canyons vs driving days with maps and calls. Cell-first corridors reward low-latency cellular. Remote nights reward Starlink. Mixed months reward bonding and/or failover so apps do not care which pipe is healthy.

WAN health first

Cellular: stand outside — bars plus real speed tests. Dead outdoor cell → placement or weBoost only when weak-but-present signal exists. Starlink: clear-sky at typical parks. Campground Wi‑Fi: optional, captive-portal messy, never your only plan.

Power and space

Fused DC near the install zone, ventilation, Ethernet path, cellular antenna lead path. Dirty power and shared noisy circuits create flaky radios that look like ISP failure.

Latency vs throughput

Video calls hate high latency even when megabits look fine. Near towers, prefer cellular priority. Where towers vanish, Starlink carries. Policy should match that reality.

WAN Health Checks

Health Checks are how Peplink decides a WAN is alive. Bad settings feel like random dropouts or “it never fails over.”

Owner checklist
  • Know which WAN is primary vs backup — write it down
  • Confirm Health Check targets make sense for travel (not one brittle destination that dies in captive-portal parks)
  • Watch for flap: marginal cell that passes/fails every few minutes
  • After firmware from peplink.com, re-verify Health Check and outbound policy
  • Road-test cell-only, Starlink-only, then failover/bonding before calling the install done

12V brownouts look like ISP failure

Radios and Starlink power paths hate voltage sag. Classic false diagnosis: “internet died” when the inverter surged or the converter dipped.

Design for

Dedicated fused DC sized for router + modem loads; label the fuse. Check voltage under A/C start and inverter surge. Strain-relieved connectors. Keep Starlink power independent enough that microwave cycles do not reboot the dish.

Fix power first

If sessions die when the inverter kicks or the battery is low, fix power before buying another WAN. Ties to electrical service and connectivity troubleshoot pages.

Install sequence (travel-safe)

  1. Confirm WANs on site: outdoor cell, Starlink sky, optional Wi‑Fi plan
  2. Pick mount with ventilation, lead length, SIM service access
  3. Mount with real fasteners — no zip-tie hinge specials
  4. Route Ethernet and antenna leads with drip loops, chafe protection, service loops; seal exterior penetrations
  5. Land fused DC; verify voltage under load
  6. Insert SIMs; connect Starlink WAN per kit topology
  7. Firmware / InControl from peplink.com only
  8. Configure outbound policy + Health Checks; name bonding and/or failover honestly
  9. Document SSIDs, priorities, fuse location; road-test cutover behavior

Starlink does not replace cellular everywhere. It pairs via Peplink bonding and/or failover. Clear sky still wins for the dish. Starlink is install capability only — never “Starlink Certified.”

Failure modes we see

Wrong mental model

Expecting bonding from failover-only (or the reverse).

Starlink behind trees

Fix sky and mount first — the router cannot invent clear sky.

Dead outdoor cell

Measure outside. weBoost only for weak-but-present signal.

Dirty power

Shared circuits, undersized fuse, inverter surge impersonate bad ISP.

RF self-interference

Antenna placement vs Starlink, indoor boosters, noisy DC-DC.

Unlabeled spaghetti

Label WAN/LAN/fuse for the next 10 p.m. failure.

DIY vs book UMRT

Reasonable DIY

Account setup, SSID naming, basic WAN priority on a pre-installed router; speed tests by park; cable dressing without new penetrations or fuse-panel work if you are competent.

Book us when

You need a clean travel-safe install; bonding and/or failover designed for real routes; Starlink + cellular on one coach network; prior install is ladder-rack chaos; you are in MT · WY · ID · WA or need a case-by-case trip quote.

FAQ

Is bonding the same as failover?

No. SpeedFusion supports bonding and/or failover as configured. Ask what was actually configured — bonding ≠ simple failover.

Will Peplink keep me online in the trees?

No router invents clear sky or outdoor cell. Peplink coordinates the WANs you actually have. No miracle uptime.

Internet dies when A/C kicks on?

Often 12V / power quality, not the ISP. Fix fused DC and brownouts before buying another WAN.

Related: Starlink guide · weBoost install · Wireless service · Peplink WAN flapping · Starlink offline · Software /peplink/

Pricing teaser

Trip fee $75 within 30 miles, then $1.50/mi each way. Labor ~$150/hr (1-hour minimum, billed in 30-minute increments). Diagnostic $150 applied toward repair if you proceed.

Credentials (text): Victron Professional Certified Installer · weBoost Authorized Installer · Peplink Certified Associate · Dometic Professional Certified. Starlink = installs only (not a certified partner title).

Text / Call Book Now