WAN bonding merges several independent internet connections into one logical link. comBOX combines fiber, DSL, 4G/LTE, 5G, Starlink and satellite services into a single Virtual Leased Line, so a site can use the capacity of every link at the same time and keep working when one of them degrades or fails.
TRUSTED BY MSPS, VARS, AND CARRIERS TO POWER BUSINESS-CRITICAL CONNECTIVITY
The definition
WAN bonding is a networking technique that combines two or more wide area network connections into a single logical link. Traffic is split across every active connection and put back together at the other end, so applications see one connection carrying the combined capacity of all of them, and keep running when any individual link degrades or drops.
A wide area network connection is simply the link that joins a site to the outside world. In most buildings there is exactly one: a single circuit from a single provider. When it slows down, everyone on site slows down. When it fails, the site is offline.
Bonding removes that single point of dependency. Several services (fiber, DSL, cellular, satellite) terminate on one device at the edge of the network. That device presents all of them to the LAN as one connection, and distributes traffic across them continuously rather than choosing one and holding it.
Because the distribution happens beneath the application, nothing on the network has to be aware of it. Users, servers and cloud services see a single gateway and a single public IP address.
The bonded link pools the throughput of every connection attached to it. Because packets from one session can travel over several links at once, large transfers and single high-bandwidth streams are not confined to the capacity of one circuit.
Every link carries production traffic all of the time. There is no standby circuit waiting for an outage, so nothing has to be detected, switched and re-established before the second connection starts being useful.
Independent services from different providers and different access technologies rarely fail together. Spreading traffic across them means a fault in one provider’s network, or one access medium, does not take the site offline.
Bonding is designed to absorb the ordinary bad behaviour of commodity internet services (loss, jitter and brief interruptions), so that voice, video, VPN and cloud applications stay usable rather than merely reachable.
The mechanics
Bonding is done by a pair of endpoints. One sits at the customer site, the other sits in the provider network. Everything between them can be any mix of internet services, because the two endpoints, not the carriers, are responsible for holding the connection together.
Scroll sideways to see the whole diagram
Any mix of access technologies can be used, from different providers: fiber, VDSL, fixed wireless, 4G/LTE, 5G, Starlink or VSAT. They stay exactly as the carriers delivered them: no special circuit, no carrier co-operation and no change of contract is required.
The appliance sits between the customer LAN and the WAN modems or routers and becomes the site’s internet gateway. It is available as a hardware appliance or as a virtual appliance on approved platforms, so it can fit a rack, a cabinet at a remote site, or an existing virtualisation host.
This is the step that separates bonding from every kind of per-session steering. Rather than choosing one link for a connection and keeping it there, the appliance decides link by link, packet by packet, using continuously measured utilisation of each path. One file transfer, one video call or one backup job can therefore occupy several links simultaneously.
All of the links terminate on the same remote endpoint: a comBOX network server provisioned for that deployment in the nearest data centre inside the comBOX global private backbone. The set of links plus that endpoint is what forms the Virtual Leased Line.
Packets that took different paths, and therefore arrived with different delays, are re-ordered into the original stream. comBOX also applies its WAN optimization here, including a performance enhancing proxy that improves TCP behaviour over links with high latency or packet loss.
From the internet’s point of view the site is reached through the comBOX network server and keeps a single public IP address. Return traffic is split across the same links on the way back, so the aggregation and the resilience apply to downloads as well as uploads.
Why it matters
What changes for a business when several ordinary internet services are bonded instead of being bought, installed and used separately.
Every active link contributes to the throughput available to the site. Because distribution happens per packet, that capacity is available to a single heavy session as well as to many small ones, which is what makes bonding useful for backups, file sync and video, not just for busy offices.
A site stops depending on one provider, one technology and one physical path. comBOX recommends combining connections from different ISPs and different access types precisely so that the causes of downtime are not shared between them.
comBOX uses a smart, transparent failover mechanism: when a link fails its traffic is rerouted over the remaining connections without a change of public IP address, so established sessions are designed to survive rather than restart. The faulty link is isolated until it recovers.
Access technologies can be mixed freely and are chosen for what is actually available at each address. A branch might bond fiber with 5G, a vessel might bond VSAT with Starlink and cellular, and a temporary site might run entirely on wireless services. The bonding layer does not care which combination it is given.
Point-of-sale, ERP, VoIP, video conferencing, remote access and cloud storage now fail together when connectivity fails. Keeping the connection usable through partial outages is what keeps the rest of the business running. For sites with a legal or safety obligation to stay reachable, it is not optional.
Capacity is added by adding another internet service and attaching it to the existing bond, rather than by upgrading a single circuit and waiting for the carrier. comBOX places no restriction on the number or type of bonded connections, so a deployment can grow as a site’s demand grows.
Bonding reduces the impact of a single link failing; it does not make a site immune to every failure. Results depend on the quality of the underlying services, the site’s power and cabling, the deployment configuration and the comBOX service selected. Combining links that share a single provider, an exchange or a mast reduces the benefit, because those links can fail together.
The most common confusion
Both put several internet connections behind one gateway. The difference is the unit of work they distribute. That single design decision is what determines whether a session can exceed one link, and whether it survives a link failing.
A load balancer decides once, when a session starts, which connection it will use, then keeps it there. Many routers do this well, and for a site whose traffic is lots of small independent sessions it spreads load sensibly.
Bonding distributes individual packets rather than whole sessions, and reassembles them at a remote endpoint. The decision is made continuously, from live measurements of each path, instead of once at the start.
Scroll sideways to see the whole diagram
| Behaviour | Session-based load balancing | comBOX packet-level bonding |
|---|---|---|
| Unit that is distributed | A whole session, chosen when it starts | Individual packets, decided continuously |
| Throughput of a single session | Limited to the one link it was placed on | Can draw on several links at the same time |
| Use of spare capacity | Depends on how sessions happen to be spread | Available to whatever traffic needs it |
| Public IP address | One per WAN link | One, held at the comBOX network server |
| Effect of a link failing | Sessions on that link break and must restart | Traffic is rerouted over the remaining links; sessions are designed to continue |
| Loss and latency handling | Left to the individual link and to TCP | TCP acceleration, forward error correction and QoS applied across the bond |
| Remote endpoint required | No, the router acts alone | Yes, a comBOX network server completes the path |
Products differ. Some SD-WAN platforms include per-packet techniques for selected traffic, and some load balancers add duplication for real-time flows. The comparison above is between the two architectures, not between specific vendors’ products.
Backup line or bonded links
A backup internet connection is the traditional answer to downtime: keep a second service in reserve and switch to it when the first one stops. It works, but only after something has already gone wrong, and only if the failure is complete enough to be detected.
In a failover design one link is live and the other waits. The business pays for both but uses one, so the money spent on the backup service buys nothing on an ordinary day. When the primary fails, the router detects it, switches, and every session that was open at that moment is torn down: VPN tunnels reconnect, calls drop, file transfers restart, and users notice.
Failover is also poor at partial failures. A link that is up but losing packets, or has collapsed to a fraction of its normal speed, often looks healthy enough to keep using, which is the situation staff describe as the internet is working, it is just unusable.
Bonding keeps every service in production simultaneously. Nothing has to be detected before the second link becomes useful, because it was already carrying traffic. When one link degrades or fails, its share of the load moves to the others and the bonded connection keeps the same public IP address, so sessions are designed to survive rather than restart.
The practical consequence is that the second connection earns its cost every day: it adds capacity when everything is healthy, and it absorbs the load when something is not.
Access technologies
comBOX is carrier-agnostic: the bond is built from whatever services are available at the address, from any providers, in any combination. These are the connection types comBOX supports today.
Two connections are only independent if their failures are. Links from different ISPs, over different media, following different physical routes out of the building, tend to fail for different reasons: a fibre cut, a mast outage, a rainstorm or a provider’s core problem rarely affect all of them at once. comBOX recommends this diversity because it is what turns several links into genuine redundancy.
You can see every connection type comBOX supports, including the specifics of Starlink and cellular deployments.
Watch for shared failure points. Services that look separate on paper often are not. Two broadband circuits from different providers may ride the same wholesale network and the same exchange; two mobile SIMs may sit on the same mast; every link in the building may pass through one duct, one patch panel and one UPS.
When links share infrastructure they can fail together, and the bond is only as diverse as its weakest shared dependency. Worth checking at survey time, before the design is fixed.
Where it is deployed
Bonding is bought where the cost of being offline is obvious and where a single good circuit either is not available or is not enough. These are the environments comBOX and its partners deploy into.
Vessels move between coverage areas and have no fixed line at all. Bonding VSAT, Starlink and cellular keeps crew welfare, navigation data and operational reporting working as the available links change with position and weather.
Quarries, farms, field offices and sites in underserved regions are often offered one poor circuit or none. Several wireless services bonded together produce a connection that is both faster and more dependable than any of them alone.
Retail outlets, clinics and regional offices need leased-line behaviour on a branch budget. Bonding commodity services at each site raises capacity and keeps card payments, ERP and VoIP working when one provider has a bad day.
Guest wifi, property management systems, booking platforms and staff operations share one connection, and guest expectations are set by what people have at home. A hybrid bond adds capacity at peak occupancy and keeps the property trading when a link fails.
Construction compounds, outside broadcasts and events need working connectivity in weeks or days, long before a carrier could deliver a circuit. Bonded cellular and satellite can be installed quickly and removed when the site closes.
Banks, logistics operators and other organisations running hundreds of sites need consistent, centrally managed connectivity rather than a different local arrangement at every address, with the resilience their regulators and customers expect.
The comBOX implementation
comBOX implements WAN bonding as a fully managed service called the Virtual Leased Line. The name describes the outcome: the behaviour of a leased line, assembled from ordinary internet services and a private backbone rather than from a dedicated circuit.
A comBOX network appliance is installed between the customer LAN and their WAN modems or routers, where it becomes the site’s secure internet gateway and distributes packets across every connected link. It is available as hardware or as a virtual appliance on approved platforms.
Each deployment is paired with a comBOX network server, a managed cloud endpoint provisioned in the data centre nearest the customer, inside the comBOX global private backbone. That server is the remote aggregation point: it reassembles the traffic, holds the public IP address and applies the optimization that makes commodity links behave better than they would on their own.
Because comBOX operates both ends and the network between them, capabilities such as end-to-end quality of service and same-IP failover are possible at all. None of them can be delivered by equipment at the customer site working alone.
comBOX services are sold and supported by its partner network rather than direct. Service bundles are available in tiers, with custom profiles where a deployment needs something specific, and the technology features are modular so a solution can be assembled around what the site actually requires.
Read the full technical detail on the Virtual Leased Line technology page, or see where the aggregation servers are located on the global private backbone page.
Traffic is split across all active WAN links and reassembled at the network server, so aggregate capacity is available to single sessions.
Failed links are isolated and their traffic rerouted over the rest without changing the public IP address, so sessions are not interrupted.
Real-time traffic can be duplicated across the two best links, with whichever copy arrives first being used, for voice and video over lossy paths.
A performance enhancing proxy splits TCP sessions and applies modern congestion control and loss recovery, aimed at high-latency and congested links.
Bidirectional prioritisation and bandwidth allocation per traffic type, enforced across the whole bond rather than on one link at a time.
Two appliances can be configured as a high-availability cluster so the appliance itself is not a single point of failure.
Specific traffic can be directed down chosen paths, and the appliance can be introduced without redesigning the existing network.
No restriction on the number or type of bonded links, and no dependency on a single provider’s network or co-operation.
Service management and monitoring for every deployment from one place, which is what makes the model workable across many customer sites.
Which of these features apply to a given deployment depends on the service bundle selected, the appliance used and the site’s configuration. Throughput, latency and availability depend on the underlying internet services: bonding improves how they are used, it does not change what the carriers deliver.
For MSPs, VARs and carriers
comBOX sells through partners. The appliance, the network servers and the backbone are operated by comBOX; the customer relationship, the service wrapper and the billing stay with you, including under your own brand if you want it that way.
For a managed service provider, bonding answers a question customers already ask: our internet is not good enough and there is nothing better available here. It is a service you can offer at addresses where you currently have no answer at all.
Questions we are asked
WAN bonding, also known as broadband bonding, internet bonding or bandwidth aggregation, combines two or more internet connections into one logical link. Traffic is divided across all of them and recombined at the far end, so the site gets the pooled capacity of every connection and stays online when one of them has a problem.
An appliance at the customer site spreads outgoing packets across every live connection, and a server in the provider network puts them back into order before forwarding them on. Return traffic is split the same way. Because both ends of the path are controlled, the two can coordinate on which link to use next, which is what a router on its own cannot do.
Yes, and two is a common starting point, typically one fixed line plus one wireless service. There is no upper limit imposed by the technology, and links can be added later to an existing bond as demand grows. The connections do not have to be the same type, the same speed or from the same provider. If you are not sure which mix suits your site, the Connection Advisor can suggest one.
It increases the bandwidth available to the site, because every connection contributes at once, and because distribution happens per packet, a single large transfer can use more than one link. It does not increase the speed of any individual circuit, and it cannot make a link faster than the carrier provisioned it. Latency is a separate matter: bonding does not reduce the physical delay of a path, although comBOX applies TCP acceleration and forward error correction to improve how applications behave over slow or lossy links.
Load balancing assigns each session to one link and leaves it there, so a single transfer can never exceed that link and a failure breaks the sessions using it. Bonding distributes packets rather than sessions, so one session can span several links and a failure is absorbed by the rest. The comparison above sets the two side by side.
comBOX isolates the failed link and redistributes its traffic over the connections that remain. Because the bonded connection keeps the same public IP address throughout (it belongs to the comBOX network server, not to any one circuit), established sessions are designed to continue rather than reconnect. Available bandwidth drops by roughly what that link was contributing, so a bond should be sized with that in mind for the traffic that genuinely must keep working.
Yes, it is one of the most common combinations, particularly at remote and mobile sites, and it is a good pairing because the two fail for unrelated reasons. Starlink can be affected by obstructions and weather while cellular is affected by congestion and coverage, so one is usually usable when the other is not. Both appear on the supported connections list.
It requires a bonding endpoint at the site, but that can be a comBOX hardware appliance or a virtual appliance running on an approved platform. The existing modems and routers stay as they are, and the carriers do not need to be involved or even aware. The other endpoint is the comBOX network server, which is part of the service rather than something the customer installs. See the network appliances page for the available options.
Remote sites are one of the strongest cases for it, because they are exactly where a single adequate circuit is unavailable. A deployment can run entirely on wireless and satellite services with no fixed line at all, which also makes it quick to install and straightforward to remove when a temporary site closes.
They solve overlapping problems at different layers. SD-WAN is primarily about policy: choosing which path a given application or session should take, and managing that centrally across many sites. Bonding is about the path itself: making several links behave as one, below the level at which applications are steered.
The two are not mutually exclusive, and some SD-WAN platforms include per-packet techniques for selected traffic. The practical question for a specific product is whether a single session can exceed one link, and whether that session survives the link failing. comBOX compares the approaches in detail on its SD-WAN vs VLL page.
More questions about deployment, commercial models and support are answered in the comBOX partner FAQ.
