“We have a backup line, so we’re covered.” It is a reassuring sentence, and it is often only partly true. A second internet connection protects the business against some failures and does nothing about others. Knowing which is which is the difference between continuity and a false sense of security.
Match the line to the failure you are worried about
| Failure | Does a second internet line help? |
|---|---|
| The primary provider’s service drops | Yes, if the switchover works and the lines are genuinely independent |
| A cable is cut in the street | Only if the second line takes a different physical route |
| The office router or firewall fails | Not unless the design also removes that single point of failure |
| Power is lost in the communications room | No, unless backup power covers the whole path |
| A cloud application or provider is down | No; the problem is outside your connection |
Before buying anything, list the activities that must continue and the specific interruptions the design is meant to handle. The comparison above is a useful starting point for the design discussion.
Two provider names are not two independent routes
Two different providers may still share a route into the building, a street cabinet or upstream infrastructure. Ask each provider what they can tell you about their physical path and dependencies. Information is not always available. Record any uncertainty rather than assuming that the second line has an independent route.
Check how applications behave during switchover
Some services depend on the business’s internet address, on permissions tied to it, or on connections that drop when the route changes. A remote-access system, a supplier portal or a phone service may need adjustment to keep working on the alternative line. Confirm these dependencies with the responsible suppliers during design, not in the middle of an outage.
Illustrative scenario. Imagine a business whose browsing works fine on the backup line during an outage, while its card terminals and the accounting portal refuse to connect because they only accept the primary line’s address. Nobody tested those two, because “the internet worked”.
Test it on purpose, in both directions
A controlled test should use the business activities identified at the start, not just general browsing. Plan it with an agreed time, a person who authorises it, a way to inform staff and a method to reverse it if the result is unexpected. Then test the return to the primary line, which can cause its own interruption.
Record what worked, what paused and what needed manual action.
Know who notices and who acts
Decide who detects that the business has switched to the backup line, who investigates the primary failure and which provider is responsible for which part of the path, under the applicable agreements. A backup that runs unnoticed for weeks leaves the business with no backup at all.
Next step: Ask BootNet to assess secondary connectivity against your defined operational scenarios, with an acceptance test that shows both the benefit and its limits.