Ask ten network vendors how to keep a site online and you will hear two words: failover and bonding. They sound similar, and both involve more than one internet connection. They behave very differently when something goes wrong, and that difference decides which one a site needs.
How failover works
Failover keeps one connection active and holds the others in reserve. The router watches the primary link. When it fails or degrades past a threshold, traffic moves to the backup. When the primary recovers, traffic moves back.
Failover is simple, affordable and effective for most branch locations. Its limitation is the switch itself. Active sessions such as a video call or a large upload usually drop and reconnect when traffic moves, and the site only ever uses the capacity of one link at a time.
How bonding works
Bonding uses every connection at once. Traffic is split across several links and reassembled at a bonding server in the cloud or a data center, so the site sees one larger, steadier connection. If one link drops, the session continues on the others, often without users noticing.
Because traffic is reassembled upstream, bonding needs that server to live somewhere: in your own private cloud, in your data center, or hosted by a partner. That design choice affects performance, control and cost.
Side by side
- Capacity. Failover uses one link at a time. Bonding combines them.
- Session survival. Failover usually interrupts live sessions during a switch. Bonding keeps them up.
- Complexity. Failover lives on the edge router. Bonding also needs a hosted server and more engineering.
- Best fit. Failover suits most fixed locations. Bonding suits vehicles, high-demand buildings and anything where a dropped session is costly.
Where bonding earns its keep
- Vehicles, where every cellular link changes constantly as the vehicle moves.
- Multi-tenant buildings where hundreds of residents share one connection.
- Data center builds that need serious capacity before permanent circuits are lit.
- Live video, telemedicine and other sessions that cannot simply reconnect.
A real example
A regional fiber provider wanted a backup with gigabit-class ambitions for buildings of up to 500 residents. SimpleCom installed four to six dome antennas per building and bonded multiple carriers into one connection hosted in the provider’s own data centers. Read Building-wide backup for fiber residents.
How to choose
Start with what a dropped session costs. If a few seconds of reconnection is acceptable, well-designed failover across two separate paths is usually enough. If the site moves, serves many users at once, or runs sessions that cannot drop, bonding is worth the extra engineering.
Common questions
Can bonding combine different types of connections?
Yes. Cellular, fiber, cable and satellite links can be bonded together, which also adds path diversity.
Does bonding increase speed?
It combines the capacity of the links, so a site with several connections can move more traffic than any single link allows.
Is failover still worth having with bonding?
Bonding already handles a lost link. Many designs still keep a separate failover path for the bonding service itself.
Deciding between bonding and failover?
One team to survey, install and support every site, on your timeline.