Your CCTV System Is Only as Good as the Network Behind It
November 22nd, 2026
When the Camera Gets Blamed for a Network Problem
A camera goes offline. Playback is pixelated. A recording has a gap. Remote viewing takes forever to load. The instinct is to replace the camera or call the manufacturer. Often the camera is fine. The network behind it is not.
CCTV is a networked system: cameras, cabling, PoE switches, recorders, storage, and the connection used to view footage remotely. Each layer has a capacity limit. When one is exceeded, the symptom appears at the camera, but the cause is upstream.
Bandwidth: The Math You Need Before Choosing Cameras
Camera marketing focuses on resolution. The network cares about bitrate. Resolution, frame rate, compression, scene complexity, and whether recording is continuous or motion-based all determine how much data each camera produces.
A rough planning example: a 1080p camera using H.265 at 15 frames per second might run 2-4 Mbps. A 4K camera can run 8-15 Mbps or more. Those numbers vary by scene and vendor, but they are enough to show why "just add cameras" is not a network plan.
Use this estimate for continuous recording:
- 1 Mbps running continuously is about 10.8 GB per day.
- A camera at 4 Mbps is about 43 GB per day.
- 16 cameras at 4 Mbps is about 691 GB per day.
- 30 days of retention is roughly 20.7 TB before overhead.
Motion-only recording and smart codecs reduce those numbers, sometimes dramatically. They do not eliminate the need to calculate. The recorder, storage array, and network still have to handle the peak, not the average.
Then consider the path. Sixteen cameras at 4 Mbps is 64 Mbps of sustained traffic into the recorder. That is well within a gigabit switch, but it may be far beyond the upload capacity of the office internet connection. If users pull camera streams directly over the WAN, remote viewing can saturate the circuit and degrade every other cloud application in the building.
PoE and Cabling: The Limits Nobody Reads
Most cameras are powered over Ethernet, which is convenient until the switch's power budget runs out.
- PoE standards. 802.3af provides about 15.4 W per port; 802.3at provides about 30 W. PTZ cameras, heaters, and blowers can draw more, sometimes requiring a separate power source.
- Switch budget. A switch may have 24 PoE ports but a total budget that cannot power 24 cameras at full draw. Add phones, access points, and other PoE devices to the same budget.
- Distance. Copper Ethernet is limited to about 100 meters per run. Beyond that, use fiber or a midpoint switch. Do not solve it with a cheap extender and hope.
- Cable quality. Use solid copper cable rated for the environment. Copper-clad aluminum and thin patch cords cause voltage drop, link instability, and intermittent camera reboots.
- Connections. Outdoor connections need proper cable, surge protection, and weatherproofing. A loose connector behind a soffit can look like a dead camera for months.
Network Segmentation: Keep Cameras Off the Office LAN
Cameras are small computers with firmware, open services, and often weak default credentials. Putting them on the same flat network as servers, workstations, and payment systems gives an attacker a path from a camera to everything else.
Put cameras and recorders on a dedicated VLAN with controlled routing. Allow only the traffic the system needs: camera-to-recorder, recorder-to-viewer, time synchronization, and remote access through a secure path. Block camera internet access by default. Do not expose camera web interfaces or RTSP ports directly to the internet.
This is both a security control and a performance control. Broadcast traffic, discovery protocols, and a busy office network can degrade video streams. Segmentation keeps the camera traffic predictable.
Storage and Recorder Throughput
A recorder can have plenty of disk space and still fail to keep up. Check the sustained write throughput, the number of cameras, the resolution and frame rate, and the retention policy. A drive that is nearly full, overheating, or failing can cause dropped frames and gaps before it fails completely.
Plan retention around what you actually need: days of continuous recording, motion events, or both. Confirm whether the recorder supports the camera count at the chosen bitrate, and whether storage can be expanded without replacing the whole unit. Check disk health regularly, and keep a spare drive or a support agreement that includes replacement.
The Uplink and Remote Viewing
Remote viewing is where many systems quietly fail. The local recorder may handle 32 cameras perfectly, but the office internet connection may have only 20 Mbps of upload. If three managers open live views at once, the circuit saturates and calls, cloud apps, and card processing suffer.
Design for the remote path:
- Use camera substreams for remote and mobile viewing.
- Record the high-resolution mainstream locally; send only what is needed offsite.
- Confirm the upload bandwidth and the number of simultaneous viewers.
- Use a secure remote-access method rather than port forwarding.
- Test remote playback on the devices and connections your team actually uses.
Time, Updates, and the Boring Failures
A camera with the wrong time is nearly useless as evidence. Make sure cameras and recorders synchronize to a reliable time source. Check for drift after power events and daylight-saving changes.
Firmware matters too. Camera vendors release security patches, and unpatched devices are a common entry point. Track firmware versions, test updates before rolling them across every camera, and replace devices that no longer receive support.
Monitor the system instead of waiting for a complaint. Alert on camera offline, recording failure, storage errors, and unusual network behavior. A camera that has been offline for three weeks is not a security system; it is a false sense of protection.
Design the Network First
The reliable sequence is not "buy cameras, then figure out the network." It is:
- Define what you need to see, where, and for how long.
- Choose resolution, frame rate, and retention for each area.
- Calculate bitrate, storage, and PoE load.
- Design the cabling, switches, VLANs, and uplink.
- Size the recorder and storage for the peak.
- Test local recording, remote viewing, failover, and alerts.
- Document the system and set a maintenance schedule.
A camera is only as good as the network carrying its video. Get the network right and the cameras do their job. Get it wrong and you will spend years replacing hardware that was never the problem.
At BTS Technologies, we design and install video surveillance systems and the structured cabling and network infrastructure behind them as one project. That means the camera count, switch budget, storage, and remote-viewing path are planned together instead of discovered after installation. For budgeting, our CCTV system cost breakdown covers what drives the quote; for the bigger picture, see our complete business guide to CCTV.
Planning a new camera system or fixing one that keeps dropping offline? Contact our team for a site and network assessment.
Posted in: Video Surveillance, Network Cabling