How to Choose Business Broadband: Dedicated Lines, Shared Broadband, SLAs and Backup Explained
| Network Infrastructure
Broadband is the upstream bottleneck of the whole network. This guide compares dedicated lines and shared broadband structurally, explains how to read upload, download, SLA and repair commitments in a contract, and how to design dual-line backup that genuinely keeps working through an outage.
Introduction: Broadband Is the Upstream Bottleneck of the Whole Network
No matter how good the office Wi-Fi or how new the switches, data still has to leave through the broadband connection to reach the internet. When broadband fails, the whole office stops together: email cannot go out, cloud systems cannot be reached, video meetings drop, and tills cannot reach payment services. The most common mistake businesses make when choosing broadband is looking at one number — download speed. That number is only one parameter in the contract, and often not the most important one.
This article explains three things: the fundamental structural difference between dedicated lines and shared broadband; how to read upload, download, SLA and repair commitments in a contract; and how to design backup so that an outage does not mean a full stop. It does not discuss individual operators' prices or promotions — those change frequently and should be taken from operator quotations. What this article covers is the judgement method that does not go out of date.
Dedicated Lines vs Shared Broadband: The Structural Difference Is the Point
Shared Broadband: Many Users Sharing, Queuing at Peak Times
The structure of shared broadband (typical home and small-business broadband) is that many users share a stretch of upstream capacity. Operators allocate capacity on a statistical model: not every user uses full bandwidth at the same time, so sharing works. But the cost is that at peak times, when many users are online together, each user's real bandwidth falls and latency rises. That is not a fault; it is the normal characteristic of a shared architecture.
Another characteristic of shared broadband is that upload and download are usually asymmetric: fast download, slow upload. For mainly "browsing, watching video, receiving email" use, that allocation is sensible. But for "uploading" use — cloud backup, sending large files, uploading video-meeting video, remotely accessing company systems — slow upload becomes the bottleneck.
Dedicated Lines: Exclusive Bandwidth, Symmetric Upload and Download
A dedicated line (Dedicated Internet Access) is structurally completely different: from the customer premises to the operator's network, it is an exclusive circuit whose bandwidth is not shared with other users. Upload and download are generally symmetric — the same speed in both directions. The benefit of this structure is not "faster downloads" but "stable, predictable performance": it does not slow down at peak times because of neighbours, and upload does not become a bottleneck.
Dedicated lines are usually provided together with a service level agreement (SLA) stating availability targets, fault-repair times, notification arrangements and similar commitments. Shared broadband generally has no SLA of the same level; fault repair follows general maintenance scheduling. For businesses where "an outage means stopping work", that difference can matter more than any speed figure.
How to Choose: Ask About the Business, Not the Speed
The choice should not start from "how fast do we want" but from "what happens if it slows down or goes down". If the business can tolerate brief interruptions and mainly browses and emails, shared broadband is generally sufficient. If the business involves continuous uploading, real-time systems, remote access, inter-branch VPN, or revenue that stops the moment the connection drops, a dedicated line deserves serious consideration. The criterion is business impact, not the number on the speed table.
Comparison Table
| Item | Shared broadband | Dedicated line |
|---|---|---|
| Bandwidth structure | Many users share upstream capacity | Exclusive bandwidth, not shared with other users |
| Upload / download | Generally asymmetric; download faster than upload | Generally symmetric; upload and download the same |
| Peak-time performance | Real speed may fall at peak times; latency may rise | Relatively stable and predictable performance |
| Service level agreement | Generally no SLA of the same level | Generally provided with an SLA stating availability and repair arrangements |
| Installation time | Generally shorter | Generally longer; may involve circuit engineering works |
| Suitable use | Browsing, email, general office work, tolerates brief interruptions | Continuous uploading, real-time systems, remote access, branch VPN, revenue affected by outages |
This table describes structural characteristics, not any individual operator's promises. Actual terms are as stated in the contract; confirm each item before signing.
How to Read a Contract: Four Must-Ask Items
First: Upload Speed — Do Not Look Only at Download
In a contract, the download speed is usually printed largest and most prominently, while the upload speed is printed far smaller. Before signing, always ask what the upload speed is, and whether it is "guaranteed" or "up to". For offices with cloud backup, video meetings and large file transfers, upload speed is what decides everyday experience. Do not sign first and discover afterwards that uploads are so slow that backups take all night.
Second: What the SLA Says — and What It Does Not Say
An SLA (service level agreement) is not a single word but a set of concrete commitments. When reading an SLA, check four things: the availability target (for example the proportion of monthly available time), the fault-repair time (how long from reporting a fault to repair), the notification mechanism (who notifies whom when there is a fault, and how), and what happens when targets are missed (whether there are service credits and how to claim them). If a contract merely says "SLA provided" without specific figures and handling methods, that SLA has no real binding force. Before signing, ask about each item and have it written into the contract.
Third: Installation Period and Circuit Works
Dedicated-line installation generally requires circuit engineering works, and lead times can range from weeks to months depending on the building's circuit situation. If the office has a hard opening deadline, the installation period must be built into the schedule — do not assume "sign and it works". Before signing, ask: does the building have existing circuits? Are extra works needed? Who is responsible for them? If there is a wait, plan a transitional arrangement, such as shared broadband or mobile data to bridge the gap.
Fourth: Contract Term, Renewal and Relocation Terms
The contract term, renewal arrangements, early-termination conditions and what happens on relocation must all be clarified before signing. When an office lease and a broadband contract term do not align, relocation becomes very troublesome: the old address's contract has not expired, and the new address needs fresh installation. These clauses are the ones nobody reads in normal times — and the ones that matter most when something goes wrong.
Backup Design: What Genuinely Keeps Working Through an Outage
Backup Is Not Just "Having More Than One Line"
Many businesses believe "two broadband lines equals backup". That is not so. Backup needs the whole chain: two independent circuits, a router that can switch over automatically, critical applications that keep running after the switch, and a way to switch back once the fixed line recovers. If any link is missing, the backup is fake backup.
Key Points of Dual-Line Design
First, the primary and backup lines should preferably come from different operators, or at least follow different physical paths. If both lines belong to the same operator and run through the same entry duct, one construction accident or one operator fault can take both down together. Second, backup-line bandwidth should be sized on critical applications, not on "having something". During backup, not all traffic needs to be maintained; decide in advance which applications take priority — for example tills, VPN and email — and let the rest pause. Third, switchover must be automatic. Relying on someone noticing the outage and switching manually means the gap in between may already have caused losses. An automatic-failover router switches to the backup line the moment the primary fails, and switches back when the fixed line recovers.
Mobile Data as Backup
Mobile data (via a 5G or 4G router) is a common backup method, with the advantages of fast deployment and no cabling, suiting temporary sites and serving as a second layer of backup. Note that mobile-data performance is affected by signal, base-station load and data-usage caps, and indoor signal in particular needs on-site testing. Do not assume "having a mobile signal equals having backup" — test the switchover time, speed and whether critical applications stay up.
Backup Must Be Tested in Practice
The biggest misconception about backup is "installed means it exists". Backup must be tested regularly in practice: unplug the primary line and see whether switchover really happens automatically, how long it takes, whether critical applications stay up, and whether it switches back once the fixed line recovers. Backup that has never been tested equals no backup. Record the test results so the next test has something to compare against.
Capacity Planning: Estimating Without Over- or Under-Buying
Capacity planning needs no complex mathematics, but it needs a method. First, list the devices online at the same time and what they do: how many people are on video meetings at once, how many use cloud systems at once, and whether there is continuous uploading (backup, surveillance). Second, estimate peak simultaneous usage, not average usage. When broadband is insufficient, the failure always happens at the peak, not at the average. Third, leave room for growth: more headcount, new systems going live and deeper cloud adoption all push usage up. Reserved growth room avoids changing contracts every year. Fourth, separate traffic that "needs a guarantee" from traffic that "can be best-effort": critical applications go on a dedicated line or guaranteed bandwidth, general browsing goes on shared broadband — that is how cost and performance balance.
Pre-Signing Checklist
| Check item | What to clarify |
|---|---|
| Upload speed | What is the upload speed? Is it guaranteed or "up to"? |
| SLA | Availability target, repair time, notification mechanism, and handling when targets are missed — all written into the contract? |
| Installation period | Does the building have existing circuits? Are extra works needed? How long until it is ready? |
| Contract term | How long is the term? How does renewal work? What about early termination? What about relocation? |
| Backup | Are primary and backup lines from different operators / different paths? Is switchover automatic? Has it been tested? |
| Critical applications | Tills, VPN, video meetings, cloud backup — which must stay up first during an outage? |
| Transitional arrangement | During dedicated-line installation, what bridges the gap? Shared broadband or mobile data? |
Common Misunderstandings
- Does higher download speed mean a better network? No. Download is only one parameter. Upload, latency, stability, SLA and backup all affect real experience.
- Do two lines equal backup? No. Backup needs independent circuits, automatic switchover, critical applications maintained, and switching back — and it must have been tested. Missing any link means it is not real backup.
- Is a dedicated line always faster than shared broadband? Not necessarily. The value of a dedicated line is stability, predictability and an SLA, not necessarily a win on the download figure. The selection criterion should be business impact, not the speed table.
- Does a contract saying "SLA provided" equal protection? No. An SLA without specific figures, repair times, notification mechanisms and handling for missed targets has no real binding force.
Conclusion: Broadband Is a Business Decision, Not a Speed Contest
When choosing broadband, do not start from the speed table; start from the business: what happens if the connection drops? Which applications cannot stop? How large is the upload need? Is the SLA specific? Has the backup been tested? Once those questions are answered, the answers for dedicated vs shared, how much bandwidth, and how to back up will follow naturally. For broadband, backup and overall network planning assessed against your actual site, see office networks; for Wi-Fi deployment, see Wi-Fi solutions. Our team surveys the site first, then recommends a solution.