How to Use Two Starlink Connections: Dual-WAN Failover and Load Balancing

Two Starlink kits can make a remote site more resilient, but the two connections do not automatically combine themselves. You need two independent service lines, a clear view of the sky for each dish, and a third-party multi-WAN router that can fail over or distribute new connections.

This guide explains a practical order: build reliable failover first, then add load balancing only after both Starlinks are stable on their own.

Independent owner's guide: Starlink Tips is not part of Starlink. Starlink hardware, plan availability, account rules and network features vary by location and kit generation. Check the current instructions for your exact hardware before making changes.

Claim Your Free Month

Order through my referral link and activate your service. Your second month of Starlink service will be free.

What a two-Starlink setup can do

A correctly configured multi-WAN router can:

• Keep sending new internet connections through the second Starlink when the first one is offline.
• Spread separate household sessions across both connections.
• Give you one local network, one Wi-Fi system and one place to manage routing.
• Make maintenance easier because you can take one terminal offline while the other stays available.

It cannot make every individual connection twice as fast. A single download, video call or VPN session will normally use one WAN path at a time unless you add a specialist bonding service. Starlink also says that the extra bandwidth from multiple antennas does not scale linearly, so two terminals should not be assumed to deliver exactly double the speed.

Two dishes at one property can still share the same problems. A storm, a blocked sky view, a damaged cable, a building-wide power failure or a problem with the multi-WAN router can affect both.

What you need before you start

Two complete Starlink connections

Plan for two independent terminal and service-line combinations:

• Dish and matching power supply.
• Correct dish cable and any required Ethernet adapter.
• A Starlink subscription for each connection.
• Two safe mounting positions with clear sky views.
• Enough power capacity for both terminals, the network router and your access points.

Do not assume that two dishes from different generations use the same cables, power equipment or mounts. Identify each kit before you order accessories.

A multi-WAN router

The router should have:

• At least two Ethernet WAN ports, or a supported way to assign two ports as WANs.
• DHCP support on each WAN.
• Health checks that can mark one link down without taking down the other.
• Failover rules.
• Load balancing or traffic distribution if you need more than failover.
• A normal LAN and Wi-Fi side for your home, office or site.

A dual-WAN business router is usually easier to configure than trying to join two Starlink routers with an ordinary Ethernet switch. Look for the terms multi-WAN, failover, load balancing and link health checks in the product documentation.

A safe installation plan

Each terminal must have its own unobstructed view of the sky. When dishes are installed close together, follow the model-specific Starlink installation guidance for separation and orientation. Starlink's current guidance varies by hardware family, and nearby antennas may need to be tilted away from each other.

Treat the two installations as two separate radio and electrical systems. Do not mount either dish where it can fall, rub against a structure, collect water around a connector or be reached only by climbing onto an unsafe roof.

The recommended network layout

Use this order:

The multi-WAN router should be the single DHCP and NAT gateway for your local network.

Do not plug both Starlink LAN outputs into the same unmanaged switch and expect the switch to combine them. That can create competing DHCP servers, confusing routes and an unstable local network.

If your hardware supports a clean Ethernet handoff or bypass mode, use the method documented for that kit. If you keep the Starlink routers in normal router mode, the multi-WAN router may see private WAN addresses and you can create double NAT. Double NAT is not always fatal for ordinary browsing, but it can complicate inbound connections, gaming, VPNs and troubleshooting.

For one consistent Wi-Fi network, use the Wi-Fi system connected to the multi-WAN router. You can leave each Starlink router available for direct testing, but separate Starlink routers do not become one mesh just because they share an SSID and password.

Set up each Starlink separately first

Do not begin by connecting both dishes to the new router. Establish two known-good baselines.

1. Bring up Starlink A

1. Connect the dish, matching power supply and router or Ethernet handoff exactly as required for the kit.
2. Open the Starlink app and wait for the terminal to report a usable connection.
3. Check for alerts, obstructions and unusual outage activity.
4. Run several ordinary speed tests at different times. Record download, upload, latency and any interruptions.
5. Label the cable and power supply as A.

2. Bring up Starlink B

Repeat the same process and label every part as B. If B is slower or less stable on its own, fix that before adding a second WAN. A multi-WAN router can route around an outage, but it cannot repair an obstructed dish, a weak mount or a damaged cable.

3. Connect the WANs

Connect the Ethernet handoff from Starlink A to WAN 1 and Starlink B to WAN 2. Set both WANs to obtain an address automatically unless your router documentation or Starlink plan requires another setting.

Set the local LAN subnet and DHCP range on the multi-WAN router. Make sure it does not overlap with either upstream router's management subnet.

Configure failover before load balancing

Failover is the safest first milestone.

1. Set WAN 1 as the preferred connection.
2. Set WAN 2 as the backup.
3. Configure health checks against stable public IP addresses such as 1.1.1.1 and 8.8.8.8, rather than relying only on a DNS server supplied by Starlink.
4. Use moderate thresholds. For example, a check every 10 seconds with five consecutive failures can be a reasonable starting point, but use the values recommended by your router manufacturer.
5. Save the configuration and watch both WAN status pages for at least several minutes.
6. Start a new web session from a device on the LAN.

When WAN 1 fails, existing TCP or video sessions may pause or reconnect because the public path has changed. That is normal. The goal is for new connections to use WAN 2 without requiring you to rewire the site.

To test failover, disconnect the Ethernet handoff from WAN 1 at the multi-WAN router. Do not pull a wet outdoor connector or climb to the dish just to simulate an outage. Confirm that a new browser session works, then reconnect WAN 1 and watch the router restore the preferred path.

Add load balancing only after failover works

Load balancing is useful when several people or devices are active at once. It is not a magic speed multiplier.

Use a new-session or connection-based policy so one session stays on one WAN. Prefer a throughput-aware method when the router supports it. A simple 50/50 split is only a starting point; it may be a poor choice if one Starlink is obstructed, congested or on a slower plan.

Test with several separate activities:

• A video call on one device.
• A download or upload on another device.
• A speed test from a third device.
• Normal browsing and streaming from the rest of the household.

Compare the total site throughput with the results from each Starlink alone. Expect the combined result to vary with satellite conditions, obstructions, network congestion and the router's balancing algorithm.

Avoid packet-by-packet splitting unless the router and application are designed for it. Packets from one session taking different paths can create reordering and instability. Connection-based balancing is the more practical default for a home, office or remote property.

Remote access and VPN cautions

A second Starlink does not automatically make inbound access reliable. Each connection may use CGNAT, and a failover event can change the public path seen by a remote service.

If you need cameras, a NAS, a server or remote administration:

• Check whether each Starlink connection provides the public IP feature you need.
• Prefer an outbound overlay VPN or managed remote-access service when inbound port forwarding is not available.
• Decide whether the service should use one preferred WAN or be allowed to follow failover.
• Test access while each WAN is active, then test again after the router fails over.
• Document any fixed routes, VPN policies or firewall rules that mention WAN 1.

Keep the local network secure. Do not expose router administration, cameras or a NAS to the internet just because a second WAN is available.

A practical validation checklist

Before relying on the setup, complete this sequence:

1. Test Starlink A alone for a normal working period.
2. Test Starlink B alone for the same type of workload.
3. Confirm both dishes have clear sky views and no unresolved app alerts.
4. Confirm the multi-WAN router sees two live DHCP leases.
5. Check that only the multi-WAN router is providing DHCP to the main LAN.
6. Test browsing with WAN 1 active.
7. Disconnect WAN 1 at the router and test a new connection through WAN 2.
8. Restore WAN 1 and confirm the router returns to the intended policy.
9. Run parallel workloads and compare the total result with each Starlink alone.
10. Test VPNs, cameras, printers and other important services separately.
11. Record the final WAN labels, health-check settings and recovery steps.

Keep the first week of logs. A short note with timestamps, weather, which WAN was active and what the app reported is more useful than a single impressive speed test.

Troubleshooting common problems

The second WAN shows no link

Check the local Ethernet port, the correct power supply, the adapter or bypass setting, and whether the Starlink itself is online in its app. Swap only one cable at a time so you know what changed.

Both WANs are online but all traffic uses WAN 1

Check the load-balancing policy, WAN weights, sticky-session settings and any rule that pins traffic to a preferred link. A single existing session may stay on WAN 1 by design; start new sessions when testing.

A video call drops during failover

The public source path changed. Configure failover for new connections, keep the health-check threshold reasonable and use a VPN or application designed to reconnect if the call must survive a WAN change.

The combined speed is not double

That is expected. A single flow usually stays on one WAN, and Starlink states that multiple-antenna performance does not scale linearly. Test several independent workloads instead of judging the setup by one speed test.

Both Starlinks interrupt together

Look for a shared cause: severe weather, a shared power circuit, a common obstruction, nearby construction, a faulty multi-WAN router or a common cable route. Check each Starlink in its own app before changing routing settings.

The Starlink app stops reaching a terminal

Third-party routing and bypass mode can change how local management works. Connect directly to the affected Starlink or follow the model-specific app instructions before assuming the dish is offline.

Safety and maintenance

Power down equipment before changing a cable or connector. Do not work on a dish, mast or roof during lightning, high winds, rain or icy conditions. Inspect mounts and cable routes from a safe position after severe weather, and use a qualified installer or electrician when the work involves roof access, structural fixings, grounding or electrical changes.

Once a month, check:

• Both Starlink apps for alerts and obstruction changes.
• Mount movement, loose fasteners and cable damage.
• Health-check status and failover events in the multi-WAN router.
• UPS or backup-power capacity for both terminals.
• Firmware and security updates for the router and Wi-Fi access points.

The most reliable two-Starlink system is the one you can diagnose quickly. Label everything, keep the routing simple and test one failure at a time.

Sources and scope

• Starlink Help Center: Multiple Starlinks
• Starlink Performance Gen 3 installation guidance
• Starlink specifications

Claim Your Free Month

Order through my referral link and activate your service.

Related Starlink guides

• How to Use Starlink as Backup Internet for Fiber or Cable
• How to Set Up UniFi With Starlink
• How to Use a PoE Switch With Starlink