Signs your CCTV system has quietly stopped working

A CCTV system has one job, and it performs that job invisibly. Nothing on the screen changes when it stops. The cameras still show a picture, the recorder still hums, the app still connects — and no footage is being kept.

Every serious complaint we are called into starts the same way: somebody went looking for an event, and it was not there. By then the failure is typically months old.

Live view proves almost nothing

Live view proves that a camera has power and a working cable to the recorder. It says nothing about whether the recorder is writing to disk, whether the disk is healthy, whether the write failed on that channel, or whether the retention has collapsed to two days.

Recording and displaying are separate functions on separate parts of the machine. One can fail completely while the other looks perfect. This single fact explains most of the disappointment in this industry.

Seven checks that take ten minutes

Do these on any system, yours or one you are inheriting. No tools needed.

• Play back a random moment from last week on every channel, not just one. Channel-level write failures are common and invisible from the live view.
• Scroll the playback calendar to the earliest date that still holds footage. That date is your true retention. Compare it with what you were promised.
• Check the disk status page in the recorder’s settings. It should report the disk as normal and show its capacity. “No disk”, “unformatted” or an error state means you have been recording nothing.
• Count the channels. A camera that has been offline for weeks often still occupies a tile showing its last frame, or a blue screen that reads as “fine” at a glance.
• Check the system time. A recorder whose clock has drifted or reset makes footage very hard to correlate with an incident, and in a dispute, hard to rely on.
• Look at one night-time recording. Infrared failures, spider webs and lens fogging only show after dark, and daytime checks miss all three.
• Try an export. Getting footage off the recorder onto a pen drive is a different function again, and the moment you need it is the worst moment to discover it does not work.

The failures we find most often

• A dead or dying hard disk. The most common single cause. Disks in recorders run continuously and have a finite life; many systems are still on their original disk years past it.
• A full disk with overwrite disabled. The recorder fills, then simply stops, and keeps showing live view indefinitely.
• One channel silently not recording after a settings change or a firmware update reset a schedule.
• Power supply degradation. Cameras at the end of long cable runs brown out at night when infrared draws more current, so they fail only in darkness.
• A spider web or fogged dome reducing a camera to a white blur after dark while the daytime image stays acceptable.
• Motion detection tuned so tightly that slow movement at the frame edge never triggers a recording at all.

Why nobody notices for months

Because nothing prompts anyone to look. A security system produces no output until it is queried, which makes it unlike almost every other system in a building. A lift that stops working announces itself within an hour. A recorder that stops writing announces itself when there is a theft.

This is also why a maintenance contract that only does cleaning visits misses the point. The valuable part of a service visit is not the cloth on the lens; it is somebody opening the disk status page and the playback calendar, and writing the numbers down.

Building the check into a routine

For a home, running the seven checks once a quarter is enough. For a society or a plant, make it a named responsibility with a written record — a line in the monthly report, not a favour somebody does when they remember.

If you hold an AMC, ask that retention and disk health be reported at every visit rather than confirmed verbally. A number written down each visit turns a slow decline into something visible before it costs you a case.