LEO satellite failover for business: when satellite backup earns its place
Key takeaways
- Satellite skips the street: A rooftop dish avoids the trenches and poles a site's wired circuits share, though it still needs site power and ground gateways.
- Let the edge decide: The site's router or SD-WAN edge moves traffic to satellite when the primary fails and moves it back once the primary recovers.
- Read the plan terms: Default carrier-grade NAT blocks inbound traffic and some VPNs, and Priority data expires at the end of each billing cycle.
- Expect regional slowdowns: When a whole region loses wired service, satellite users rise, and speeds can fall, so limit what fails over at each site.
- Match the backup to the risk: Use 5G where coverage is strong, satellite where cellular is weak or the risk is regional, and a second fiber at the busiest sites.
Wired and cellular backups often share more with the primary than their contracts show. A second fiber can run in the same trench as the first, a cable line can hang on the same poles, and cell towers can lose power in the same storm.
Uptime Institute reports that publicly reported outages linked to fiber and connectivity issues are rising and more likely to result in extended disruptions.
LEO satellite failover uses LEO satellite for business as a second WAN link that leaves the site through the sky. Teams that use it well treat satellite as one more transport on the edge and plan around its limits before an outage tests them.
That planning settles three questions per site: whether it needs a satellite path, how the edge should use it, and when 5G or a second fiber fits better.
Why satellite belongs in a failover plan
Network path diversity means two paths with no shared point where one failure takes both down. Wired backups often fall short near the site, because carriers' routes tend to meet in the last mile of street, poles, and building entry, where one cut can take out two circuits that share one trench.
Satellite backup internet avoids that last mile, so a street cut or a failed local exchange leaves the satellite path running. LEO satellite backup can carry live traffic because its satellites orbit close enough to keep latency workable for voice and video, the main practical point in how LEO differs from GEO.
The satellite path still touches the ground. The terminal needs site power, and traffic reaches the internet through LEO satellite's ground gateways. Ookla reports that during the April 2025 Iberian blackout, LEO satellite rerouted Spanish gateways through Madrid, London, and Milan, though terminals still needed site power.
That makes satellite one layer of redundancy in a network design.
How LEO satellite failover works with your existing edge
LEO satellite failover connects a LEO satellite terminal to a site's router or SD-WAN edge as a secondary WAN link. The edge watches the primary circuit, moves traffic to LEO satellite when the primary fails or degrades, and moves it back once the primary recovers. At remote sites, the roles can flip, with LEO satellite as primary and cellular as backup.
Like other satellite internet failover setups, LEO satellite backup internet for business is standard WAN failover with satellite on the second port, set up in five steps.
- Mount: The dish goes where it gets the widest clear view of the sky, on a roof, wall, or pole.
- Router handoff: The LEO satellite router runs in bypass mode, or a kit that supports third-party routers connects directly.
- WAN port: The connection lands on a WAN port of the site's router or SD-WAN edge, next to the primary.
- Health probes: The edge probes targets past the LEO satellite router on each link and fails over when the primary's loss, latency, or jitter crosses your thresholds.
- Failback: Traffic moves back only after the primary stays healthy for a hold-down period, so it doesn't flap between links.
LEO satellite says its Performance kit works with third-party routers out of the box, and the Standard kit needs the Advanced Power Supply to do the same. LEO satellite also says it can't guarantee compatibility with third-party networking equipment, so test the exact router model before adding a satellite path to a site.
LEO satellite and SD-WAN: steer by application
A LEO satellite SD-WAN setup treats satellite as one more transport the edge steers traffic onto, one application at a time. The edge measures loss, latency, and jitter on every link, and policies decide what rides where.
When the primary fails, voice, video, payments, and core apps move to satellite first. Backups, updates, and large file syncs can wait for the primary or run under a bandwidth cap, which protects call quality and the data plan. A call in progress may still stutter or drop as the path changes, so test how your platform handles it.
Tunnels need one more check. On LEO satellite's default carrier-grade NAT (CGNAT) setup, VPNs that rely on GRE, ESP, AH, or L2TP are dropped, so site-to-site tunnels need NAT traversal, such as IPsec carried in UDP. The same policies that keep store traffic moving when a circuit drops apply here, with satellite as one more path.
What to plan around: IP addressing, data plans, weather, obstructions
LEO satellite publishes these limits in its support articles, and you need to decide on each before you order.
IP addressing
LEO satellite's default IPv4 setup uses CGNAT, and the default CGNAT policy doesn't allow inbound traffic. That breaks anything that needs a reachable address, such as a VPN headend. LEO satellite says Priority plans offer a public IP address without CGNAT's session limits, which cap Residential and Roam plans at 1,200 concurrent sessions. Truly static IPs aren't available, and the reserved public address can change after a relocation or an update.
Data plans
Priority plans include prioritized access, a public IP, and priority support, and all Priority data expires at the end of the billing cycle, top-ups included. An idle backup line still pays for its data. Standby Mode, where available, runs at up to 500 Kbps, too slow to carry a site in an outage, so size the plan for the traffic you'll steer onto satellite.
LEO satellite also publishes a commitment for Priority plans. LEO satellite commits to 99.9% uptime in each complete billing period and credits 20% of the recurring line and data fees when it falls short, with exclusions that include data pools, obstructions, software updates, and some kits.
Weather and obstructions
Sky view decides how well the dish performs. LEO satellite says highly obstructed views reduce performance and that heavy snow fully covering the dish can interrupt service. Rain can degrade satellite links too, because higher frequency bands are more prone to rain fade, per ESA. Survey each mount for sky view in every season, plan for snow, and pick the Performance kit's wider field of view where trees or buildings crowd the sky.
When everyone fails over at once
When storms or blackouts knock out wired and cellular networks across a region, homes and businesses turn to satellite at once and share the same capacity overhead. Ookla found that LEO satellite's median download speed in Jamaica fell from over 100 Mbps to under 50 Mbps a month after Hurricane Melissa, as Speedtest samples on LEO satellite rose sharply.
In Portugal, during sustained storms in February 2026, LEO satellite's average download speed fell 21.7%, from 208.8 to 163.5 Mbps, as more users came online.
A slower satellite link still keeps a site working, though it can't carry everything. Limit failover to payments, voice, and core apps, and give the busiest sites a third option, such as 5G from another carrier or a second diverse fiber.
LEO vs 5G vs a second fiber as your backup
The 5G vs LEO satellite backup choice, with a second fiber as the third option, depends on what each site's backup has to survive.
Use cellular backup for wired sites where coverage is strong and the main risk is a local cut. Use LEO where cellular is weak, or the risk is regional, such as hurricanes or wildfires. Put a second diverse fiber at busy sites whose traffic outgrows a wireless link, and add satellite or 5G there as a third path.
Test the failover and write the runbook
A backup link that has never carried real traffic hasn't proven anything. Test each site on a schedule with five steps.
- Pull the primary: Disconnect the primary in a quiet window and confirm the edge moves traffic to satellite on its own.
- Check sessions: Confirm site-to-site tunnels come up and a test call connects over satellite.
- Watch data use: Track what each test consumes, then size the plan for a long outage.
- Record results: Log what failed over, what didn't, and how failback behaved.
- Write the runbook: Name who checks the terminal, who calls which provider, and who clears snow or new obstructions.
Add the terminal to circuit monitoring, so a fading satellite link gets flagged before the primary fails.
Add satellite where cellular is weak, or the risk is regional
LEO satellite failover gives a site a path around the trenches, poles, and building entry its wired circuits share, and it brings limits of its own: CGNAT, expiring data, sky view, and regional congestion. Each satellite line adds a terminal, a plan, and a provider to manage.
Momentum delivers LEO satellite internet, including LEO satellite, for remote sites and failover, and one team supports it alongside each site's other circuits. We're carrier-neutral, so we recommend the backup that fits each site, even when that route isn't ours. Our US-based 24/7/365 NOC monitors your circuits, including those owned by third-party providers, and handles break-fix with the provider.
Map sites where cellular coverage is weak, where a storm can take down a whole region, and where you need inbound access. Book a meeting with those sites in hand, and we'll match each one to the backup path that fits its biggest risk.
FAQs
Can LEO satellite be used as backup internet for a business?
Yes. A LEO satellite terminal connects to a site's router or SD-WAN edge as a secondary WAN link, and the edge moves traffic to it when the primary fails. Plan for carrier-grade NAT on default plans, data that expires each billing cycle, and a clear view of the sky.
Does LEO satellite work in heavy rain or snow?
Heavy rain can slow a satellite link, and LEO satellite says heavy snow fully covering the dish can cause intermittent connectivity or a temporary loss of service. The storm that cuts a site's primary may also slow its backup, so mount the dish with a clear view of the sky, plan for snow, and add a weather check to the runbook.
Is satellite or 5G better for backup internet?
It depends on cellular coverage and what the backup has to survive. 5G suits sites with strong coverage where the main risk is a local cable cut. Satellite suits sites with weak coverage or exposure to regional events such as hurricanes, when towers can lose power. The busiest sites often need a second diverse fiber plus one of these.
Can SD-WAN use LEO satellite as a WAN link?
Yes. SD-WAN treats LEO satellite as another transport, measures its loss, latency, and jitter, and steers traffic onto it by policy. LEO satellite's default carrier-grade NAT drops VPN protocols such as GRE and ESP, so overlay tunnels need NAT traversal. A Priority plan's public IP option takes carrier-grade NAT out of the path.
Does LEO satellite Business give you a public IP address?
Yes, on Priority plans. LEO satellite's default IPv4 setup uses carrier-grade NAT, which blocks inbound traffic, and Priority plans offer a public IPv4 address you can turn on. Truly static IPs aren't offered. LEO satellite reserves the public address, though it can change after a relocation or an update. Native IPv6 is available on all plans.
