Load Balancing vs Bonding: What’s the Difference and Why It Matters

Buy almost any multi-WAN router today (Teltonika, MikroTik, GL.iNet, Peplink) and the datasheet will proudly tell you it supports multiple internet connections. What it often won’t tell you is how it uses them, and that detail is the difference between a deployment that shrugs off a network outage and one that drops every call in the building.

The two approaches are load balancing and bonding. They sound similar. They both plug into two or more WANs. On a speed test, they can even look the same. But under the surface they behave completely differently, and if you’re running VoIP, live video, CCTV backhaul, or card payments, choosing the wrong one will cost you.

This guide explains exactly what each one does, where load balancing quietly falls short, and why bonding, especially when paired with multi-network SIMs, is the foundation of genuinely resilient connectivity.

What load balancing actually does

Load balancing distributes your traffic across multiple internet connections on a per-session (per-flow) basis. When a device on your network opens a connection, such as a web page, a video call or a file upload, the router picks one WAN for that session and sends the entire flow down that single link.

Open ten sessions and the router will spread them across your WANs, usually weighted by configured ratios or link capacity. Tools like mwan3 on OpenWrt, Teltonika’s multi-WAN features and MikroTik’s PCC routing all work this way.

This is genuinely useful. If you have an office full of people browsing, emailing and streaming, load balancing spreads the aggregate demand across your links and makes better use of the bandwidth you’re paying for. It’s simple, it runs entirely on the router, and it needs no server-side infrastructure.

But there are three limits baked into the design.

1. No single session ever gets combined speed

Because each flow is pinned to one WAN, a single upload, stream or transfer can never go faster than the one link carrying it. Two 40 Mbps 4G connections load-balanced together give you two 40 Mbps lanes, never one 80 Mbps lane. For a live video encoder pushing one big RTMP or SRT stream, the second connection contributes precisely nothing.

2. Failover breaks sessions

When a load-balanced WAN fails, the router detects it (typically via ping checks over several seconds) and routes new sessions to the surviving links. But every session that was mid-flight on the dead link is gone. VoIP calls drop. TLS sessions reset. Video streams stall and reconnect. Card terminals time out mid-transaction.

Worse still, the surviving sessions now originate from a different public IP address. Anything that cares about your source IP, such as SIP registrations, VPN tunnels, banking portals and IP-allowlisted services, has to renegotiate or fails outright.

3. Two connections, two identities

With load balancing, the outside world sees you as two (or more) separate public IPs, and on most cellular connections those IPs sit behind CGNAT, meaning no inbound access at all. Hosting anything, reaching CCTV remotely or maintaining a stable VPN endpoint becomes somewhere between painful and impossible.

What bonding does differently

WAN bonding operates at the packet level, not the session level. Your router establishes an encrypted tunnel to a bonding server in a data centre, and every packet, regardless of which session it belongs to, is distributed across all available WANs, then reassembled in order at the server before heading out to the internet.

That single architectural change fixes all three problems at once:

• True aggregation. One stream, one upload or one call can use the combined capacity of every link. Two 40 Mbps connections genuinely behave like one 80 Mbps pipe (minus a small tunnel overhead).
• Seamless failover. If a link dies, packets simply stop being scheduled onto it within milliseconds, not seconds. The tunnel stays up, sessions stay alive, and your video call carries on without so much as a stutter. When the link recovers, it rejoins automatically.
• One stable public IP. All traffic enters and exits the internet at the bonding server, so you get a single static IP that never changes, no matter which underlying connections come and go. CGNAT on the cellular links becomes irrelevant, and inbound access to CCTV, VPNs and servers just works.

This is exactly how Bondix works, and it’s why bonded connectivity is the standard for outside broadcast, event production and any deployment where a dropped session has a real cost. If you want to see it survive a literal cable cut mid-stream, we’ve demonstrated it live on our YouTube channel.

Side by side

When is load balancing enough?

To be fair to load balancing, if your requirement is simply that a busy office shares two broadband lines and nobody’s workload is critical, it does the job with zero extra infrastructure. Short-lived web traffic barely notices a per-session failover, and there’s no tunnel overhead to think about.

The moment any of these appear on your requirements list, though, you’ve outgrown it:

• Live streaming or broadcast contribution
• VoIP or video conferencing that mustn’t drop
• Card payments at events or retail sites
• CCTV that needs reliable remote access
• A static IP or inbound services on cellular connections
• Long uploads or transfers that need more speed than any single link provides

Multipath resiliency: where bonding really earns its keep

Bonding aggregates whatever paths you give it, but resiliency comes from the diversity of those paths. Bond two SIMs on the same mobile network and a single mast outage still takes both down. True multipath resiliency means combining connections that fail independently: different carriers, different technologies, different physical routes.

This is where bonding and MultiNet Steered SIMs become more than the sum of their parts. MultiNet SIMs connect across EE, Three, Vodafone and O2, with network steering that lets you control remotely which network each SIM uses. Pair two or three MultiNet SIMs, each steered to a different carrier, and you’ve built a bonded connection with no single point of failure in the radio access network:

1. Your router bonds three connections: SIM A on EE, SIM B on Vodafone, SIM C on Three
2. EE suffers a mast outage
3. Bondix stops scheduling packets onto the EE link within milliseconds
4. Your stream, calls and payments continue over Vodafone and Three, on the same sessions and the same public IP
5. When EE recovers, it silently rejoins the bond

Add a fixed line, Starlink or venue broadband into the mix and the bond absorbs those too, because Bondix doesn’t care what the underlying transport is. Fibre plus 4G, satellite plus 5G, or six WANs at once on the right hardware.

What you need for true bonding

Three ingredients:

1. A bonding-capable router. Either a Teltonika RUT, RUTX or RUTM device, or one of the specific OpenWrt routers we have certified for the Bondix Universal Client. Support is per model rather than every OpenWrt 24.10.0 device: right now that means two, the GL.iNet Flint 2 and the MikroTik RB5009, each with its own step-by-step guide, with more to follow as we certify them.
2. Diverse connections. Ideally different carriers or technologies, which is where MultiNet SIMs slot in from £1/month.
3. A bonding server. The aggregation point in the data centre. You can self-host, or let us run it for you.

Why SimpliWiFi for bonding?

SimpliWiFi is Bondix’s own authorised hosted solutions partner. Our hosted bonding gives you:

• UK and EU data centre servers for low latency and data sovereignty
• Static IP included, essential for CCTV, VPN and remote access, even over CGNAT cellular
• Automatic provisioning, with your bonding server live within minutes of subscribing
• MultiNet Steered SIMs, offering carrier-diverse connectivity across EE, Three, Vodafone and O2 from £1/month, purpose-built for multipath bonding
• Flexible plans: monthly, annual, or a 7-day fast pass from £20/month, with no lock-in
• UK-based support from real engineers who run this stack every day

Whether you’re bonding two SIMs on a construction site or six WANs on a broadcast truck, we can spec, supply and support the whole stack. View all Bondix hosting plans or talk to us about MultiNet SIMs.