Half Past Four and Everything Freezes: Why Your Office Broadband Struggles When It Matters Most

Ask most office managers when their internet problems occur and the answer is rarely 'first thing'. At eight o'clock, when one or two early arrivals are checking emails, the connection feels snappy and dependable. By half past four — every laptop active, video calls running, files syncing to the cloud — the same line can feel as though it is wading through treacle. Pages hang, calls stutter and uploads crawl.

This pattern is not a coincidence, and it is not simply a matter of buying a bigger headline speed. It is the predictable consequence of how business broadband is provisioned and shared. Understanding it is the first step towards fixing it.

The Shared Nature of the Local Network

The vast majority of UK business broadband connections — FTTC, SoGEA and most full fibre packages on standard plans — ride over infrastructure that is shared with other users. Your cabinet, exchange or fibre point serves dozens or hundreds of premises, and the capacity back to the provider's core network is finite.

This is where the concept of the contention ratio comes in. In plain terms, it describes how many connections are sharing a common pool of bandwidth. A line sold as '80Mbps' may well deliver 80Mbps in isolation, but that figure assumes the shared infrastructure has headroom. When neighbouring businesses and households all hit the network simultaneously, everyone's effective throughput drops.

Peak pressure typically builds through the working day and reaches its worst in the late afternoon — school-run hours for residential areas, and the point at which office workers are uploading end-of-day reports, backing up files and squeezing in one last video conference.

Throttling and Traffic Management

Some providers go further than passive sharing. Traffic management policies — sometimes buried deep in the fair usage section of a contract — can deprioritise certain types of traffic, or certain customers, during busy periods. Streaming and large downloads are common targets, but business-critical applications such as VoIP can occasionally be caught in the same net on consumer-grade or poorly specified business packages.

It is worth reading the small print of your current contract specifically for phrases like 'traffic shaping', 'network management' and 'peak hours'. If those terms appear without a clear carve-out for business traffic, that is a warning sign.

A Practical Testing Regime for SMEs

The good news is that diagnosing afternoon congestion requires nothing more exotic than a spreadsheet and some discipline. Run a structured test over one representative working week:

• Test at fixed times. Run speed tests and latency checks at, say, 8am, noon, 2pm and 4.30pm each day. Consistency matters more than volume.
• Record latency and jitter, not just speed. A line can show a respectable download figure while jitter renders video calls unusable. Note the ping time and how much it varies between tests.
• Test under load. At least once, run the test while the whole team is working normally. A speed test on an idle line tells you little about real-world afternoon performance.
• Log upload speeds separately. Cloud backups, video calls and file sharing are upload-heavy, and upload capacity is usually the first thing to degrade on contended lines.

If your 4.30pm download speed is routinely less than half your 8am figure, or if latency swings wildly in the afternoon, you have your answer: the line is contended, and no amount of router restarts will change that.

What to Do About It

Armed with your results, the options become clearer. First, raise the issue with your provider — a documented pattern of peak-hour degradation is difficult to argue with, and business-grade packages often include commitments to prioritised traffic or improved contention ratios.

Second, consider whether a dedicated or less-contended service is warranted. Full fibre leased lines offer guaranteed bandwidth and symmetrical speeds, and while they cost more, the calculation changes quickly once afternoon congestion is costing staff hours. Our earlier guidance on the leased line decision framework sets out how to weigh that trade-off.

Third, look at quality of service (QoS) settings on your own equipment. Prioritising VoIP traffic on your router will not create bandwidth that isn't there, but it can ensure that when capacity is tight, phone calls survive even if file syncs slow down.

The Takeaway

A broadband connection should be judged by its worst hour, not its best. The 4pm slump is a diagnostic signal — one that tells you whether your current package genuinely fits the way your team works. Test methodically, document the pattern, and use the evidence to make the case for infrastructure that holds up when everyone is online at once.