Your Internet Runs on One Cable: Building Circuit Resilience Into Your SME’s Connectivity

  • 6 days ago
  • 0

For many UK SMEs, the internet connection is treated as a utility: it is there, it works, and nobody asks much about the cable that brings it into the building. Yet that last stretch may be a single physical route to a cabinet, exchange or network point of presence. If it is cut or disrupted, the cloud can be perfectly healthy and still be out of reach.

That matters because the office internet connection is now much more than a way to browse websites. It may carry accounting and customer systems, file access, calls, payment transactions and remote access. In practice, “everything is in the cloud” can mean that the cable into the office has become the office.

The cloud is only as reachable as the pipe

Cloud applications remove the need to host every system on-site. They do not remove the need for a reliable connection between your people and those systems. A weak or interrupted circuit can stall work just as effectively as an unavailable application.

Review which services depend on the connection: email, file storage, hosted desktops, CRM, online banking, customer booking and ordering platforms, and cloud telephony. A Cloud Solutions strategy should consider how each service behaves when its users lose their normal route to the internet.

Even services hosted elsewhere can rely on your local circuit. A cloud-hosted IBM i system, for instance, is still inaccessible to a branch whose connection has failed; this is one reason IBM i Management must take connectivity dependencies into account. The hosting location may be resilient. The path from your premises may not be.

A Dynamics 365 Jump Start or other cloud programme should therefore consider the connectivity needed at each site, not only the software configuration and migration plan.

A second line is not automatically a resilient line

Ordering a second broadband service can be a sensible step, but two invoices do not necessarily mean two independent routes. Separate providers may use the same underlying network. Two circuits may share a duct, pole, street cabinet, exchange or other network point. A single incident affecting that shared section could take out both.

The UK Government’s telecoms resilience guidance advises organisations to seek assurance that routes and connection points are physically separate. It also notes that using more than one supplier does not, by itself, guarantee diverse routing.

Before buying a second circuit, ask providers specific questions:

  • What infrastructure does it share with the existing service?
  • Are the building entry, duct, local route and access point separate?
  • Which underlying network carries the service?
  • Is route diversity confirmed by a survey and guaranteed in the contract, or is it only intended?
  • Will the provider notify you of planned works that could affect either service?

If uninterrupted service is important, request evidence of the proposed separation and any shared-risk points. Where the provider cannot confirm the route, treat that uncertainty as part of the risk assessment.

Read the service level agreement carefully, too. Check the fault response and repair or restoration targets, how they are measured, what remedies or service credits apply, and how much notice is given for planned work. A credit may compensate for a service failure; it does not restore access to a system while your staff are waiting.

Two fibre routes approaching an office while sharing part of an underground duct

Make wireless failover a designed path

A 4G or 5G connection can provide a useful alternative when a fixed circuit fails. For many SMEs, automatic mobile failover is a practical first layer: a dual-WAN router monitors the main connection and switches traffic to the mobile link if it stops responding.

But the backup needs to be designed, not merely plugged in. Check signal strength at the actual router location and test it at busy times. A signal that looks good outdoors may perform poorly inside the premises; an external antenna or a different router position may help. Confirm the data allowance, fair-use limits, throttling policy and likely throughput when the whole office is using the backup.

Where 5G is available and performs reliably at the site, it may offer more capacity than 4G. Fixed wireless or low-Earth-orbit satellite may also be options in some locations. Each has its own constraints, such as coverage, congestion, latency, availability or installation requirements. Wireless is a different route, not a magic route: local mobile capacity can be shared, and a disruption may affect more than one network.

The aim is to understand the failure modes and choose a backup that is independent enough to be useful. For some businesses, that means a mobile network different from the one used for the primary service. For others, a surveyed, physically diverse fixed circuit may be justified alongside wireless failover.

Business router and mobile antenna positioned for wireless backup connectivity

Map what must keep working

Resilience is not just about keeping a router online. Start by identifying the business activities that must continue, then trace the services and routes they depend on.

For a retailer, that might include card payments, tills, stock checks and customer Wi-Fi. For an accountancy practice, it could be access to cloud files, client portals and banking. For a professional office, it may include hosted systems, video meetings and incoming calls. Remote and home-working staff may also depend on a central office connection if their access to business applications passes through it.

Include Voice and Connectivity in the map. If your phones use cloud telephony, check whether calls can be routed elsewhere or diverted to mobiles when the office circuit is unavailable. Confirm who can activate the change, whether callers hear an appropriate message and whether staff know how to respond.

Then test the path end to end. Simulate a primary circuit failure and check that the backup actually carries the traffic your business needs: sign-in, DNS, VPN access, key cloud applications, card payments and calls. A router showing “connected” is not proof that a customer can pay or a colleague can answer the phone. Record the result, address any gaps and test again after material network or system changes.

Check what resilience is costing

A resilient design should match the cost of downtime, not the number of circuits on an invoice. Review circuit charges, mobile data plans and site-by-site connectivity as part of Technology Expense Management.

This can reveal duplicate services that share the same physical route, backup SIMs with inadequate allowances, or mobile plans that are paid for but never tested. It may also show that a site needs a stronger backup, while another is paying for capacity or resilience it does not require.

The right question is not simply “How many connections do we have?” It is “What business risk does each connection reduce, and is it delivering that value?”

Put connectivity failure into the recovery plan

A circuit outage is a Disaster Recovery scenario even when every application is running normally. Your plan should identify the services affected, the expected failover route, who checks that it is working, how staff and customers are informed, and what happens if the backup also fails.

A short, clear runbook is more useful than an untested diagram. Include provider fault-reporting details, instructions for switching or diverting calls, and practical alternatives for critical customer transactions. Helpdesk Support can help staff report and resolve issues quickly, but the recovery route itself must be designed and tested in advance.

A carefully arranged network router and distinct routes representing tested connectivity paths

Strategy first, circuits second

The Fractal IT Director approach starts with the business requirement: what must remain available, for whom, and for how long? From there, the resilience design can specify physical route diversity, provider diversity, suitable wireless failover and regular end-to-end testing. Network Solutions and Managed IT Services then support delivery and ongoing operation as execution services beneath that strategy, alongside trusted specialist partners where needed. To explore the wider Evestaff group, visit evestaff.co.uk.

Your cloud services may be hosted far away. Their availability to your team still starts with the route into your building. Find out where that route runs, what happens if it fails, and whether the backup has been tested lately.

SEO keywords: Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, Fractal IT Director, IT Consultancy

Join The Discussion