Connect. Secure. Manage.
WAN Circuit Diversity Review
Review evidence of circuit diversity with network providers, separating claimed resilience from shared ducts, exchanges and other common dependencies.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
A WAN circuit diversity review checks whether two connections really use separate paths. Different suppliers may still share a duct, building entry or other weak point. We review the available evidence and record common risks in the Cisco or Meraki WAN design. The result states what is known and which claims of separation remain unproven.
The whole path
Understand how sites, providers, cloud networks and security controls fit together.
Resilience that can be tested
Separate a second circuit from genuine end-to-end service resilience.
Provider coordination
Keep addressing, routing and escalation ownership clear across organisations.
Begin with the service you need to protect
The right level of diversity depends on the consequences of losing network access. A branch that can operate offline for a short period has different needs from a trading location or a site hosting customer-facing apps. We establish the required continuity, the role of each circuit and the practical alternatives available when the building itself becomes inaccessible.
We record the commercial service names alongside the technical identifiers. Circuit references, handoff locations, access carriers, managed-router ownership and escalation contacts are often spread between procurement records and engineering notes. Bringing them together avoids comparing two products as independent simply because their invoices use different descriptions. Unknown ownership is flagged for clarification, not filled in by assumption.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Follow the path beyond the local router
The review starts inside the premises with racks, power, patching, access switches and cable routes. Two circuits entering the same cabinet may be lost together through a local electrical or cabling incident. We trace the documented path to each building entry and compare it with the design’s stated failure aims. Site inspection can be included where records are insufficient.
Beyond the premises, evidence normally comes from providers and their underlying carriers. We ask specific questions about shared access infrastructure, points of presence and route separation. A broad sales statement about resilience is not equivalent to a confirmed route-diversity commitment. Supplier confidentiality may limit the detail available. The report distinguishes checked separation from claims that cannot be independently substantiated.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Assess provider and operational dependencies
Physical routing is only one source of common failure. Two services may depend on the same upstream network, maintenance process, support desk or managed equipment platform. We review these relationships alongside the customer’s routing arrangements. Diversity should be described across the layers that matter rather than reduced to a yes-or-no label on a diagram.
The customer also needs a usable escalation route for each service. We check whether contracts permit direct technical discussion, whether a reseller must open the carrier ticket and whether incident contacts work outside ordinary business hours. These details influence recovery even when the circuits are physically separate. A technically diverse path is less useful if nobody can authorise its activation or get support.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Consider alternatives without overstating them
A different access technology can reduce certain common risks. For example, a cellular service may avoid the local fixed-line duct used by the main circuit. It can introduce other dependencies, including local radio coverage, antenna placement, data allowances and the provider’s wider network. We assess the alternative against the app’s needs rather than treating a different medium as automatic proof of independence.
Where a backup uses another premises or data centre, we review how staff and apps reach it. The design may still rely on the original site’s firewall, DNS service or VPN hub. We identify those hidden dependencies and explain whether the proposed alternative protects against a circuit outage, a device failure or loss of the entire location. Those are different resilience aims.
Turn evidence into practical design decisions
The deliverable groups dependencies by their likely service impact and the confidence of the available evidence. It identifies which risks can be reduced by cabling changes, provider commitments, routing adjustments or a different recovery arrangement. Cost and rollout disruption are considered alongside technical benefit. The most expensive circuit combination is not necessarily the most appropriate one.
For Cisco and Meraki estates, we also check that the network can use the diverse paths as intended. A physically separate backup does not help if routing, VPN or firewall policy prevents important traffic from using it. Detailed changes to the settings remain a separately agreed rollout task, with WAN failover testing used to check the resulting behaviour.
Keep the assessment current
Diversity can change after a carrier migration, building alteration or service renewal. We recommend recording the evidence date, the supplier’s wording and the assumptions requiring periodic confirmation. Procurement teams can then preserve relevant commitments when contracts are renegotiated instead of accidentally replacing a diverse service with a cheaper shared path.
MCI can review one critical site or a multi-location programme across the UK. We provide the questions to raise with providers and a clear explanation of the residual risks. Supply current circuit schedules and redacted diagrams to begin; passwords and unrestricted settings are unnecessary for the initial discussion. The aim is a resilience decision that a business owner can understand and an engineer can substantiate.
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.