Redundancy and Failover: When One Connection Isn't Enough

Getting the Internet Right: Part 10 of 12

Everything we've covered in this series so far has been about choosing the right primary internet connection. But here's an uncomfortable truth: every type of internet connection, even the best ones, goes down sometimes. Cables get cut. Equipment fails. Providers have outages. Storms take out infrastructure. A backhoe operator digging up a parking lot doesn't check for buried fiber before he starts.

If your business can afford to be offline for a few hours, or even a day, without serious consequences, then a single well chosen connection is probably fine. But if being offline means you can't take calls from customers, can't process transactions, can't access your cloud applications, or can't communicate with your team, then relying on a single connection is a gamble. It's not a question of whether it will go down. It's a question of when, for how long, and what it costs you.

Redundancy means having more than one connection so that when one fails, the other can take over. Failover is the mechanism that makes the switch happen. Together, they're your insurance policy against the thing that everything else in your business depends on.

The basic concept

The simplest form of redundancy is two internet connections from two different providers, ideally using two different technologies and two different physical paths. If your primary connection is cable from Provider A, your backup might be fixed wireless from Provider B, or DSL from Provider C, or a cellular connection. The goal is diversity. If one goes down, the other shouldn't go down at the same time for the same reason.

This sounds simple, and conceptually it is. But the details matter a lot, because poorly planned redundancy gives you a false sense of security that's arguably worse than knowing you have no backup at all.

Why provider diversity matters

Having two connections from the same provider might not protect you as much as you think. If both connections use the same provider's network, a single failure in that provider's infrastructure could take out both circuits simultaneously. This happens more often than people expect. A router failure at the provider's local facility, a fiber cut on their backbone, or a software issue that affects their entire network will take down every connection you have with them.

Using two different providers gives you protection against provider level failures. But even this isn't enough by itself.

Why physical path diversity matters

Consider this scenario: you have cable from one provider and fiber from a different provider. Great, two different providers, two different technologies. But both cables enter your building through the same conduit, cross the same utility right of way, and run along the same stretch of road. A single construction accident, a vehicle hitting the right utility pole, or flooding in the right spot can take out both connections at once because they share the same physical path for some portion of their route.

True physical path diversity means the two connections take completely different routes to reach your building. This is easier said than done, and it's one of the reasons wireless backup connections (fixed wireless or satellite) are popular for redundancy. A wireless connection doesn't use any of the same physical infrastructure as a wired connection, so a cable cut can't affect both.

If both your connections are wired, it's worth asking each provider how their cable reaches your building and whether the two paths share any common infrastructure. In practice, achieving complete physical diversity with two wired connections is sometimes impossible, especially in areas where all the utility infrastructure runs along the same corridor. But even partial diversity is better than no diversity.

How failover works

Having two connections doesn't help if the switch between them isn't handled correctly when the primary fails. Failover can be automatic or manual, and the difference matters.

Automatic failover uses a router or firewall that monitors both connections and switches traffic to the backup when the primary goes down. Good routers do this within seconds, so the disruption is brief. The best setups monitor not just whether the connection is up but whether it's performing adequately, so the failover triggers on degradation, not just total failure. This is important because some outages aren't clean. The connection might stay technically up but with such high packet loss or latency that it's functionally useless. A failover system that only triggers on complete loss of connectivity won't help in these situations.

Manual failover means someone has to notice the outage and take action, whether that's switching a cable, logging into a router, or calling someone to make a change. This is cheaper to set up but introduces a delay between the outage and the recovery. If the outage happens at 3 PM on a Tuesday when the IT person is in the office, the delay might be a few minutes. If it happens at 8 PM on a Saturday, it might be hours before anyone notices and responds.

For businesses where connectivity is critical during business hours, automatic failover is worth the investment. The hardware to support it is not exotic or excessively expensive. Most modern business routers and firewalls support dual WAN connections with automatic failover, and configuring it is straightforward for anyone with basic networking knowledge.

What happens to your phone calls during a failover

If your phones are VoIP and your internet goes down, your calls drop. If the failover happens quickly, say within five to ten seconds, active calls will likely drop but new calls can be placed almost immediately on the backup connection. If the failover takes minutes, you're offline for that entire period.

Some VoIP systems handle failover better than others. Cloud hosted phone systems, where the PBX is in the provider's data center rather than in your office, tend to handle connection changes more gracefully because the call routing intelligence isn't tied to your specific internet connection. If your internet fails over to a backup, the cloud PBX doesn't care which connection you're using. It just sees your phones reconnect.

On premises phone systems can be more sensitive to connection changes, depending on how they're configured. If your PBX registers with the VoIP provider using the IP address of your primary connection, and the failover switches you to a different IP address, the registration may need to re-establish before calls can flow. This can add delay to the recovery.

It's worth testing your failover scenario with your actual phone system before you need to rely on it. Disconnect the primary connection deliberately during a low traffic period and observe what happens. How long until the phones reconnect? Do active calls survive the switch? Does everything come back up automatically, or does something need to be manually restarted? Finding out the answers during a planned test is much better than finding out during a real outage.

Common redundancy configurations

Cable primary, cellular backup. This is one of the most common and affordable setups for small businesses. Your primary connection is cable or fiber, and you keep a cellular failover device (often called an LTE or 5G failover router) that activates when the primary goes down. Cellular has the advantage of being completely independent of your wired infrastructure. The downside is that cellular bandwidth is limited and can be expensive if you're on a metered plan, and cellular can be congested in dense areas.

Fiber primary, fixed wireless backup. A good combination for businesses that need more bandwidth on the backup than cellular can provide. The fixed wireless connection takes a completely different physical path since it's wireless, providing true path diversity. If the provider uses licensed spectrum, the backup can be quite reliable.

DIA primary, cable backup. For businesses that have DIA as their main connection, a cable line as backup provides a cost effective fallback. The cable connection doesn't need to deliver the same quality as the DIA. It just needs to keep things running until the primary is restored.

DIA primary, DIA secondary. For businesses where even brief outages are unacceptable, two DIA connections from different providers on different physical paths provides the highest level of redundancy. This is the most expensive option but provides the best protection and allows for load balancing across both connections during normal operation.

The cost question

Redundancy costs money, both for the second connection and for the equipment to manage the failover. For some businesses, the cost is hard to justify when the primary connection is working fine, because you're paying for something you hope you'll never use.

The way to evaluate this is to estimate the cost of an outage. If your business generates $5,000 per day in revenue and an internet outage means you can't take orders, process transactions, or communicate with customers, then a full day outage costs you $5,000 or more. If a backup connection costs $100 a month and saves you from even one full day outage per year, the math is straightforward.

For businesses where the financial impact of downtime is hard to quantify, think about the operational and reputational costs. Employees sitting idle because they can't access their tools. Customers calling and getting no answer. A partner trying to reach you and hearing dead air. These costs are real even if they don't show up on a spreadsheet.

Setting it up right

If you decide to implement redundancy, a few practical considerations:

Make sure both connections are tested regularly. A backup that's been sitting idle for six months might have developed a problem you don't know about until you need it.

Configure your failover to test connectivity to something beyond your provider's network, not just to the provider's gateway. A connection that reaches the provider's first router but can't get to the broader internet isn't useful.

Consider whether certain traffic should always use one connection over the other. Some setups route voice traffic over the more reliable connection and general internet traffic over the less expensive one, using both connections actively rather than keeping one as a cold standby.

Document your setup so that when an outage happens, whoever is responding knows what to expect and what to check.

Next up: Reading an ISP Quote: The Questions You Should Be Asking, how to evaluate what you're being offered and compare proposals that don't make it easy to compare.