Back to Blog
wan aggregationmulti-wantroubleshootingrouter settings

How to Fix Slow Speeds When Your Router Supports WAN Aggregation but Your ISP Doesn’t: Multi-WAN and Bonding Explained

Your router touts WAN aggregation for double the speed, but your ISP hasn’t cooperated and your connection still crawls. Here’s why the mismatch happens and exactly what to do about it.

How to Fix Slow Speeds When Your Router Supports WAN Aggregation but Your ISP Doesn’t: Multi-WAN and Bonding Explained
8 min read

You bought a high-end router specifically because the spec sheet listed “WAN aggregation” or “dual-WAN bonding.” You imagined combining your cable connection with a backup link and doubling your throughput. Instead, speeds are identical to before—or worse, the feature broke something. The culprit is almost always a mismatch between what your router can do and what your ISP actually provisions. This guide explains the gap and gives you five concrete paths forward.

What WAN Aggregation Actually Requires

WAN link aggregation uses Link Aggregation Control Protocol (LACP, IEEE 802.3ad) to bond two physical Ethernet ports into a single logical connection. Think of it like tying two garden hoses together to increase flow rate. But both ends of those hoses have to cooperate—your router on one side and your ISP’s modem or ONT on the other.

Specifically, your ISP’s modem or optical network terminal (ONT) must also support LACP-IEEE 802.3ad and must be provisioned by your ISP to use it. Most residential cable modems and DSL gateways do not support LACP at all. Fiber ONTs from carriers like AT&T and Verizon Fios typically expose only a single Ethernet port. Unless your ISP has explicitly enabled multi-gig bonding on your account, flipping the switch on your router accomplishes nothing on the WAN side.

Why Speed Tests Still Show Only One Line’s Worth of Speed

Even on networks where bonding is correctly configured end-to-end, a single Speedtest.net run will almost never show the full aggregated bandwidth. That’s because Speedtest opens one TCP session, and one TCP session travels through one path—it cannot split across two bonded links. To verify true aggregate throughput, you need two devices running speed tests simultaneously, each pulling from a different server so the egress IPs differ and the router’s load-balancing hashes them to separate WAN ports. If each device gets your full single-line speed, your bonding is working correctly.

Option 1: Switch to Multi-WAN Load Balancing (Most Practical)

If your ISP won’t provision LACP, abandon true bonding and switch your router to multi-WAN load balancing mode instead. This is supported on consumer routers from ASUS (Dual WAN), Netgear Nighthawk, TP-Link Archer/Deco, and virtually every pfSense or OpenWrt-based build.

In load-balancing mode the router distributes individual sessions across two WAN connections using a flow-based hash (typically source IP + destination IP). No single download gets faster—a 4K stream still uses one link—but the total household throughput scales with the number of simultaneous sessions. During a busy evening with five people streaming, gaming, and video calling, aggregate household bandwidth effectively doubles.

To configure it on an ASUS router: go to WAN → Dual WAN → enable Dual WAN → select Load Balance. On TP-Link Archer routers it lives under Advanced → Network → Internet → Load Balancing.

Option 2: Upgrade to a Single High-Speed Port

Many users discover they don’t need aggregation at all—they need a faster single connection. If you’re on a gigabit cable plan and your ISP has started offering 2.5 Gbps or multi-gig tiers, a single 2.5GbE port on the modem side will outperform two bonded 1GbE ports and requires zero ISP coordination. Routers like the ASUS RT-BE96U and Netgear Nighthawk RS700 include 2.5GbE or 10GbE WAN ports for exactly this scenario.

Check whether your ISP offers a multi-gig modem upgrade before attempting complex bonding configurations. A $10/month plan upgrade plus a compatible modem often delivers more real-world speed than any aggregation workaround.

Option 3: Ask Your ISP to Enable It

Some ISPs—particularly those offering business-class fiber—can provision LACP on the ONT if you ask. Frontier Fiber, some Comcast Business accounts, and enterprise-tier AT&T Fiber installations have been documented enabling this. Residential accounts rarely qualify, but it costs nothing to call and ask. Have the model numbers of your modem/ONT and router ready, and specifically request “LACP or 802.3ad bonding on the WAN-side Ethernet port.”

Option 4: Multi-Link PPPoE (MLPPP) for DSL Users

If you are on a DSL connection, Multi-Link PPPoE (MLPPP) is the only WAN bonding technology that can deliver true per-session aggregate bandwidth—meaning a single download can use both lines simultaneously. MLPPP requires explicit provisioning at the DSLAM (your ISP’s equipment in the street cabinet) and is offered by a shrinking number of rural DSL providers as a way to deliver 40–80 Mbps from two 20–40 Mbps DSL pairs. Routers running pfSense or MikroTik RouterOS can terminate MLPPP if your ISP supports it. Ask your DSL provider directly.

Option 5: Failover Instead of Aggregation

If pure speed isn’t the goal but uptime is, configure your dual WAN in failover mode rather than load balance. Your primary connection handles all traffic; the secondary takes over automatically only if the primary goes down. This is far simpler to set up, universally supported by ISPs, and provides meaningful reliability for home offices and remote workers—even if it doesn’t increase peak throughput.

Set the detect interval in your router’s dual-WAN settings to at least 30 seconds to avoid false failovers during brief ISP hiccups.

Quick Diagnostic Checklist

  • Confirm your ISP modem/ONT model supports LACP-IEEE 802.3ad (check the data sheet or call support)
  • If bonding is unsupported, switch router to load balance mode
  • Test throughput with two devices simultaneously—not a single Speedtest run
  • Check whether your ISP offers a multi-gig plan with a 2.5GbE or 10GbE modem
  • On DSL: ask about MLPPP provisioning if you have two phone lines
  • For reliability over speed: use failover mode with a 30-second detect interval

Once your WAN setup is sorted, run a speed test from multiple devices at once to verify real aggregate throughput. If raw speeds are still disappointing, the bottleneck may now be your WiFi—check our guide on why WiFi is slow and our WiFi 6 vs WiFi 7 upgrade guide for the next steps.

Related Articles