Multi-Bearer Internet Failover and Redundancy, Explained Properly

01

The terms get used loosely

If you're evaluating wireless connectivity for a business site, you'll hear "SD-WAN," "bonded," "multi-bearer," and "load balanced" used almost interchangeably. They are not the same thing — and the differences between them decide whether the connection you buy actually performs, or just looks good on a quote.

This brief is the plain version: what these terms mean, what actually matters, and what to ask before you sign.

02

Load balanced vs bonded — the real difference

Both approaches combine multiple carriers. The difference is how — and it's not a detail.

Load balanced distributes traffic across carriers independently. Each session — a download, a call, a file transfer — uses one carrier at a time, and the SD-WAN router sends each new session down the least-congested path. It's efficient for a busy multi-user site where lots of people are doing lots of separate things, and it's lower cost because there's no aggregation server in the path.

Bonded combines every carrier into encrypted tunnels through a cloud bonding server, creating one unified pipe. A single download uses the combined bandwidth of every carrier at once. It's the right answer when you need maximum single-session throughput — and, crucially, when you need what bonding makes possible: a real, static, public IP address.

Neither is "better." Load balanced suits multi-user general office traffic at a lower price point; bonded suits sites that need single-pipe performance or inbound access. But you can't choose well if a provider uses the words interchangeably.

03

CGNAT, and why the static IP matters

Here's the issue most buyers don't know to ask about. Most 4G/5G connections sit behind carrier-grade NAT — CGNAT. Hundreds of customers share a single upstream public address. Outbound traffic works fine: the site browses, emails, reaches cloud services normally. But anything inbound — a VPN tunnel terminating at the site, port forwarding, a remote CCTV system, an IT team trying to reach their own kit — simply cannot get through. There is no public address to reach.

A bonded connection solves this structurally. Because traffic routes through the provider's cloud bonding server, the site is handed a real, static, public IP on the way out. Inbound access behaves exactly as it would on a Fibre leased line. If a site needs inbound access — and most business sites do, even when nobody mentions it upfront — that capability isn't a nice-to-have. It's the requirement.

“If a provider uses "bonded" and "load balanced" interchangeably, that tells you what you need to know.”

04

Engineered, not posted

This is the part the spec sheets never cover, and it matters more than any line on them. A wireless connection's real-world performance is decided at the site — not in the datasheet.

A capable router with internal antennas, sitting in a metal comms cabinet, will underperform badly — however strong the carrier signal is outside. The things that actually decide performance: a site survey that tests every carrier before anything is ordered; carrier-specific external antennas, positioned for that specific building; a proper router rather than a consumer device; and, where the optimal antenna position is far from the cabinet, running the cable to suit. The same hardware, engineered for the site versus shipped in a box, is the difference between a connection that performs and one that disappoints.

05

What to ask a provider

Six questions will tell you most of what you need to know:

• Do you survey the site and test carriers before quoting?
• Are the antennas external and carrier-specific?
• Is it load balanced or bonded — and which fits my workload?
• Do I get a static, public IP?
• Is the connection monitored 24/7, and by whom?
• What exactly happens when one carrier degrades or drops?

If a provider can answer those clearly and specifically, you're talking to an engineering business. If they can't, the quote isn't worth comparing.