BigLeaf compared: single circuit, dual-WAN, traditional WAN
A factual assessment: what do the usual approaches to internet resilience deliver – and where are the architectural differences to BigLeaf?
| Criterion | Single internet circuit | Classic dual-WAN failover | Traditional WAN (e.g. MPLS) | BigLeaf SD-WAN |
|---|---|---|---|---|
| Automatic failover | No: No alternative during an outage | Partly: Yes, usually only on a full outage (link or ping check) | Partly: Depends on the provider's redundancy design; often needs an extra backup line | Yes: Yes, also on quality degradation, per flow |
| IP address continuity | No: Provider IP, unreachable during an outage | No: Public IP changes with the provider – sessions drop | Partly: Internal addressing stable; internet breakout depends on design | Yes: Bigleaf-issued public IP stays the same |
| Intelligent path selection | No: Not available | Partly: Rule-based, statically configured | Partly: Routing defined by the provider | Yes: Per flow based on continuous measurements |
| Real-time monitoring | Partly: Depends on the router, usually basic | Partly: Basic reachability checks | Partly: Provider portal, usually limited to its own network | Yes: Latency, jitter, packet loss, capacity – 10× per second, both directions |
| Dynamic prioritisation | No: None | Partly: Static QoS rules, mostly outbound only | Partly: Class-based QoS within the provider network, configured manually | Yes: Dynamic QoS, automatic, in both directions |
| Firewall integration | Partly: Firewall directly behind the provider router | Partly: Function usually inside the firewall – changing it means redesign | Partly: Separate security architecture | Yes: In front of any existing firewall, without touching its rules |
| Administration effort | Yes: Low – but without protection | Partly: Medium: rules, tests, provider coordination | No: High: contracts, change processes, long lead times | Yes: Low: pre-configured, no manual policies (manufacturer) |
| Cloud optimisation | No: None | No: None | Partly: Cloud traffic often backhauled via a central site | Yes: Via Cloud Access Network peering with 150+ networks |
The approaches in detail
Single internet circuit
The simplest and cheapest solution – as long as everything works. If the circuit fails or quality collapses, there is no alternative. For sites that can operate without internet, that is legitimate.
Classic dual-WAN failover
Dual-WAN firewalls and routers usually have limited analysis tools for internet problems and can prioritise only outbound traffic. On failover the public IP address changes – which inevitably interrupts VoIP calls, virtual desktops and VPNs. Often they switch only on a complete outage.
Classic load balancers
Classic load balancers are not designed to optimise different services such as VoIP, remote desktop and VPN specifically. They also usually assume equal bandwidths and stable connections – rarely the case in practice with fibre plus 5G.
Traditional WAN (e.g. MPLS)
Provider WANs offer predictable quality within their own network but are often expensive, inflexible for new sites and frequently backhaul cloud traffic through a central site. For companies whose applications have moved to the cloud, this model fits less and less.
BigLeaf SD-WAN
BigLeaf provides end-to-end visibility across the internet path and seamless same-IP failover to keep applications running. Control extends into its own Cloud Access Network; prioritisation works in both directions; the firewall stays unchanged. The prerequisite for resilience remains: at least two independent circuits.
Video: making the internet resilient
The video from the previous site explains bonding different providers (in German, YouTube channel “Compatible Computer Solutions”).
Try it: disrupt a circuit, see the effect.
Set one or more circuits to “degraded” or “down”. The status board shows how BigLeaf reroutes traffic – and, if you like, what a classic dual-WAN would do in the same situation.
Control circuits
Normal operation: all circuits carry traffic. Voice and video run over the circuit with the best quality.
Classic dual-WAN: the primary circuit carries traffic, the backup waits unused.
Simplified illustration of the principle – no measurement data, no performance commitment. The IP address is from a documentation range (RFC 5737). The circuit order is an example assumption.
Related questions
What is the difference between BigLeaf and classic dual-WAN?
A dual-WAN router or firewall controls traffic only at its own site and uses the providers' IP addresses. On failover the public IP therefore changes and sessions drop. It can usually prioritise only outbound traffic. BigLeaf extends control into its own Cloud Access Network: prioritisation works in both directions, the public IP stays the same, and quality degradation short of a full outage is taken into account. See the full comparison
What happens when an internet circuit fails?
BigLeaf detects the outage through its continuous measurements and automatically moves the affected flows to the remaining circuits. Because the public IP address comes from Bigleaf rather than the provider, active sessions – such as VoIP calls, VPN tunnels or cloud applications – stay up according to the manufacturer. This requires at least one other working circuit at the site.
Does my public IP address stay the same?
Yes. Your site receives a Bigleaf-issued public IPv4 address or IP block. It is independent of the individual providers and stays the same on every circuit switch (same-IP failover). During rollout, services that previously allow-listed your provider IP are switched to the new address once. How same-IP failover works
Do I need several internet providers?
Not necessarily. According to the manufacturer, BigLeaf can also run on a single circuit and then provides prioritisation, visibility and the backbone network. For automatic failover you need at least two circuits. Different providers and media – such as fibre plus 5G – are recommended so that a single cable cut or provider incident does not hit both circuits.
Sources (retrieved 7 Nov 2026)
Ready for a more reliable internet connection?
Talk to our team about your sites and circuits. We show BigLeaf in a live demo and check how it fits into your existing infrastructure.