Tristan Wood, Managing Director at Livewire Digital, argues that resilience is being undermined by hidden shared dependencies – and that true network diversity must be designed, verified, and exercised, not assumed.

As data centres become critical infrastructure for digital economies, the most significant connectivity risks they face are no longer driven by capacity constraints. They stem from hidden dependencies embedded in network design. Resilience is not defined by how much bandwidth a facility can deliver, but by how effectively connectivity failures are contained when they occur. Genuine network diversity has therefore become a key feature of resilient data centre design, rather than a secondary enhancement.

Connectivity strategies are still too often assessed on speed, latency, and headline cost. Bandwidth scale remains central to commercial positioning, and resilience is frequently assumed to improve alongside capacity. In practice, most connectivity failures in data centre environments are not caused by insufficient bandwidth. They arise from shared infrastructure that turns supposedly independent paths into correlated points of failure. When outages occur, the surprise is rarely that something broke, but that multiple routes described as diverse failed at the same time. For operators and developers of critical digital infrastructure, the objective is no longer simply to deliver capacity. It is to limit the impact of failures that are, in complex networks, unavoidable.

Redundancy is not resilience

Many facilities meet formal redundancy requirements without achieving genuine independence. Multiple circuits, multiple providers, and favourable service level agreements can create confidence while concealing common dependencies. Two carriers may enter a site through different meet-me points yet share the same external duct for much of their route. Providers that appear diverse on paper may still converge at the same metropolitan point of presence or rely on the same wholesale backhaul. Even routes designed to be physically separate can terminate at power-dependent aggregation facilities that receive limited design and operational scrutiny.

When a regional fibre cut, power incident, or maintenance error occurs, these dependencies are exposed immediately. Outages then cascade not because redundancy was absent, but because it was assumed rather than verified. For data centre operators, this distinction is critical. Redundancy addresses individual component failure. Resilience addresses systemic failure across interconnected infrastructure.

Physical and carrier diversity require discipline

Physical diversity is not an abstract principle. It is a discipline rooted in route awareness. Operators and developers need a clear understanding of how fibre actually reaches a site, where routes intersect, and which assets are genuinely independent. This extends beyond high-level topology diagrams to include ducting, road crossings, building entry points, and campus-level distribution.

The last mile remains one of the most common sources of connectivity failure, where construction activity, accidental damage, and environmental factors converge. Multiple entry routes from different directions, built on genuinely separate infrastructure, significantly reduce this risk. These decisions are far easier to implement during site selection, when meaningful diversity can be designed in, than during later retrofit projects where vulnerabilities are costly and complex to address.

Carrier diversity only delivers value when it provides real operational separation. Selecting multiple providers offers limited protection if they rely on the same upstream plant or terminate in the same facilities. Separation of points of presence should be treated as a design requirement rather than a commercial preference. Within the campus, connectivity should be treated as core infrastructure, not as a bolt-on service. Route separation, equipment placement, and meet-me room design all influence whether diversity survives beyond the perimeter fence or collapses into a single effective failure domain.

Operational design determines whether diversity works

Operational models ultimately determine whether diversity translates into resilience. Designs that rely on idle backup links are straightforward to specify but carry risk. Secondary paths are often under-tested, poorly monitored, or quietly degraded over time. When they are finally activated, it is usually during an incident when tolerance for failure is at its lowest.

By contrast, distributing traffic across multiple active paths can surface weaknesses earlier. Continuous use allows degradation to be identified before it becomes an outage and supports more controlled responses when conditions deteriorate. This approach requires stronger monitoring, clearer accountability, and greater operational discipline, but it reduces recovery times and avoids surprises during incidents.

No single operational model is universally correct. What matters is clarity about trade-offs and rigour in execution. Regular failover testing is essential, and it must extend beyond idealised scenarios. Facilities should test partial failures that reflect real-world conditions, including upstream provider incidents and application behaviour, not just device-level events. The aim is to understand how services behave under stress and whether the intended diversity preserves continuity for customers.

Failure modes are predictable

The industry does not lack evidence of how networks fail. Regional fibre cuts frequently affect multiple carriers at once due to shared civil routes. Incidents at a single point of presence can isolate entire metropolitan areas. Maintenance and configuration errors continue to account for a significant proportion of outages, even in well-designed environments.

What distinguishes resilient data centres is not the absence of these events, but their containment. When connectivity is distributed across genuinely independent routes, facilities, and operators, failures remain localised. Recovery becomes a matter of rerouting traffic rather than waiting for physical repairs. Diversity also creates operational choice. Teams with multiple independent paths retain options under pressure. Teams without them are constrained, regardless of preparation or expertise.

Designing for failure is a strategic choice

One of the biggest barriers to meaningful network diversity is cultural. Projects are often driven by timelines, cost controls, and standardised templates that treat diversity as a secondary consideration rather than a core design constraint. This approach underestimates the true cost of failure. Outages do not only disrupt customer operations. They damage availability metrics, erode confidence, increase contractual exposure, and invite regulatory scrutiny.

For boards, investors, and developers, treating network diversity as a baseline requirement is often less costly than absorbing the impact of repeated major incidents. Designing for failure is not pessimistic. It is pragmatic in a landscape where complex systems fail in ways that design documents rarely anticipate.

Rethinking how resilience is measured

Traditional resilience metrics are reaching their limits. Availability targets and recovery time objectives remain useful, but they do not capture the difference between a contained fault and a systemic outage. A more meaningful measure is service continuity under stress. This includes how much functionality is retained when components fail, how quickly traffic can be rerouted, and how many genuinely independent failure domains exist between a data centre and the wider network.

As reliance on digital infrastructure accelerates, these questions are becoming central to how facilities are designed, assessed, and trusted.

The resilience of data centres is no longer defined by the absence of failure, but by the ability to absorb disruption while continuing to deliver dependable services. Achieving this requires deliberate, verifiable network diversity across routes, carriers, facilities, and operations, rather than a narrow focus on raw bandwidth. Hybrid network diversity, designed from the outset and exercised through day-to-day operations, can be an effective yet underused approach to meeting continuity expectations.