The morning round is a familiar ritual. Somebody opens the platform, clicks through a wall of live views, sees a picture on each one and moves on. On a site with 40 cameras it takes twenty minutes. On an estate of 2,000 across 50 sites, nobody is doing it at all.
The trouble is that the ritual checks the wrong thing. A live view proves the camera answered when you clicked on it. It proves nothing about whether footage was written last night, which is the question you will actually be asked.
Online and recording are two different states, and a camera can hold the first for weeks while losing the second.
What has to hold for a clip to exist
Between the sensor and the disk there is a chain, and every link in it can fail on its own without the picture on your screen changing.
- The camera. It answers, it streams, and it has not recorded since Thursday.
- The stream. It drops for a few seconds at a time, several times an hour, and each drop leaves a hole in the footage.
- The network in between. Packet loss, a saturated link, a duplicate IP address, and underneath those the Ethernet faults that cause them.
- The recorder. A unit that has stopped reporting, one rebooting again and again, a drive going bad, storage that cannot keep up with what is being written to it.
An operator looking at a live picture sees none of that. Every one of them ends the same way: the footage is not there when somebody asks for it, and by then the cause is weeks in the past.
Watching every link in the chain
TetherX checks each link continuously and names the one that stopped working.
A camera that is online but has not recorded is flagged on its own, without anyone opening it first. Gaps in footage are identified and shown against the camera in the app and in the health report. The network path is diagnosed rather than just observed, so an integrator gets the cause and not only the symptom, and Ethernet faults arrive with the remedy attached: replace the cable, check the switch port for auto-negotiation.
Where a camera or a recorder is configured in a way that costs you footage, TetherX shows the suggested change and offers a button that applies it to the device. The fix happens on the same page as the finding, instead of on a laptop in a plant room, logged into the camera itself.
The health report goes out daily, weekly or monthly. Nothing waits for somebody to go looking.
What an investigation looks like afterwards
The value of all this shows up later, in an investigation. An operator scrubbing back through a night does not have to work out from a witness statement that something is missing. The playback timeline shows where footage is absent, at the moment they reach it.
That is a different conversation with a customer, an insurer or an officer than "we think the camera may have stopped in August".
The question worth asking about your own sites
Whatever platform you run, this one is worth putting to it tonight: if a camera stopped recording, would you find out before somebody asked for the footage?
If the answer is that you would find out by going and looking, then the daily round is not a check. It is a hope, repeated every morning.
See what the platform watches without being asked, or read why integrators choose TetherX.
Leave a Comment