The Redundancy Illusion: When the Network Goes Down, So Does the Business

Mar 11, 2026

Reading Time: 2 minutes

The Redundancy Illusion: Why Network Resilience Must Be Designed, Not Assumed

Connectivity Intelligence • UK & SA Markets

Strategic Insight: Network resilience is rarely as robust as leadership assumes. In the UK and South African markets, the “Redundancy Illusion” often hides single points of failure within shared last-mile infrastructure. True business continuity requires physically separated carriers, automated failover testing, and proactive governance to ensure downtime doesn’t become a business-ending event.

It rarely starts with a dramatic failure. Instead, it’s the “micro-glitches”—a warehouse system hesitation, a frozen video call, or a financial transaction that hangs just a second too long. These are the early warnings most businesses ignore until the disruption is total.

After thirty years of managing networks across the UK and South Africa, the reality is clear: most organisations believe they are resilient simply because they have invested. But investment without verification is just an expensive assumption.

“Resilience cannot be assumed. It has to be designed.”

The Cost Nobody Budgets For

Unplanned downtime costs thousands per minute. Beyond lost transactions, you face idle staff, logistics bottlenecks, and POPIA/GDPR regulatory exposure. The July 2024 CrowdStrike incident proved that carrier faults aren’t the only threat; your entire software dependency stack must be resilient.

The Redundancy Illusion

Having two internet providers doesn’t always equal failover. We routinely find “redundant” lines that share the same physical street cabinet or duct. If a contractor hits one pipe, both connections die. You haven’t purchased protection; you’ve purchased an illusion.

Our principle is simple: Redundancy that hasn’t been tested under load isn’t redundancy.

5 Questions for Your Next Board Meeting


  • Infrastructure Diversity:
    Do your primary and secondary connections share the same last-mile physical path?

  • Automation:
    Is your failover 100% automatic, or does it require manual intervention during a crisis?

  • Traffic Intelligence:
    Does your network prioritise ERP and VoIP, or does non-essential traffic compete for bandwidth?

  • Proactive Signals:
    Would you detect performance degradation before your customers do?

  • Single Accountability:
    Is there one team owning the entire ecosystem, or is responsibility split across multiple vendors?

Where Modern Architecture Fits

With ERP and logistics now living in the cloud, an outage is no longer an inconvenience—it’s a shutdown. SD-WAN is the intelligent routing layer that manages this risk, but it is not a magic wand. It requires carrier diversity and physical separation to be effective.

author avatar
Geordie Hogarth

Let’s connect