CCTV · Free guide

IP camera online but not recording: a step-by-step check

A camera shows live video but playback is empty or has gaps. Check disks, schedules, streams, time, bandwidth and the network in the right order, with what to record before you change anything.

The camera is online. You can see it on the monitor and on the mobile app. But when someone asks for last night’s footage, the timeline is empty or full of gaps. This guide walks through the checks in the order that finds the cause fastest on most Indian sites, whatever make of NVR or VMS you use. Menu names differ between manufacturers; the logic does not.

Why live view is not proof of recording

Live view and recording are two separate paths through the recorder. Live view usually shows the camera’s sub-stream: a small, low-bitrate copy of the picture that is easy to decode. Recording usually writes the main stream: the full-resolution stream. For the main stream to end up on disk, all of these must be true at the same time:

  • a recording schedule is enabled for that camera, for that hour of that day;
  • if the schedule is motion or event based, the event is actually firing;
  • the recorder can accept the main stream (codec, resolution and bitrate within its limits);
  • at least one disk assigned to that camera is healthy, formatted by the recorder and writable;
  • the recorder’s clock is right, so recordings are filed under the time you search.

A camera can pass every live-view check and still fail one of these. So the question to ask is not “is it online?” but “which of these five is broken?”

Before you change anything

  1. Write down the exact symptom. Which cameras, since when, and is the timeline completely empty or broken into pieces? “All cameras since Tuesday” and “one camera, gaps every few minutes” have very different causes.
  2. Protect footage that may be needed. If an incident is under investigation, export the recordings that do exist before you format, replace or re-assign any disk. Formatting destroys footage permanently.
  3. Check playback for another camera at the same time. If other cameras recorded normally, the problem is specific to this camera’s settings or stream. If none did, look at the recorder and its disks first.
  4. Open the recorder’s log. Search the system log for the period. Entries such as disk error, disk full, video loss, network disconnect, illegal login or reboot point straight at the cause.

If no camera is recording

When every channel stops at the same moment, the cause is almost always shared: storage, the recorder itself, or time.

  1. Check the disk status page. Each disk should show a normal or OK state with free space or overwrite in use. Uninitialised means a new or replaced disk that the recorder has not formatted yet. Error, abnormal, read-only or sleeping states stop writing.
  2. Check overwrite. If overwrite is disabled and the disks are full, recording simply stops. On most sites overwrite should be enabled, with retention set by days if the recorder supports it.
  3. Look at disk health. Run or read the S.M.A.R.T. status where the recorder shows it. Reallocated or pending sectors, or a disk that disappears and returns, mean the disk is failing. Plan a replacement with the right surveillance-rated disk, and export needed footage first.
  4. Check network storage if used. For NAS or iSCSI storage, confirm the recorder can still reach it (network, credentials, IP address unchanged) and that the share is not full.
  5. Check the recorder’s date and time. A recorder that lost its time after a power cut may be filing recordings under the wrong date — sometimes years in the past. Search the timeline around the date shown on the recorder, then set NTP and the time zone (IST, UTC+05:30).
  6. Check whether recording was turned off. Some recorders have a global recording switch, a “holiday” schedule, or a user who changed the schedule template. The audit or operation log shows who changed what.

If one camera is not recording

  1. Open that camera’s recording schedule. Confirm it is enabled and covers the hours that are missing. A schedule copied from another camera may be set to motion only, or to working hours only.
  2. If the schedule is motion or event based, test the event. Walk in front of the camera and watch for the motion indicator. Check that motion detection is enabled on the camera or the recorder (whichever the recorder uses), the detection area covers the scene, and the event is linked to “record this channel”.
  3. Check which stream is recorded and what it is set to. Compare the camera’s main stream (resolution, frame rate, codec, bitrate) with the recorder’s limits. A recorder that accepts only a certain maximum resolution or bitrate per channel, or does not support the camera’s “smart” codec variant, may show live view from the sub-stream but fail to record the main stream. As a test, set the main stream to standard H.264 or H.265 at a moderate bitrate.
  4. Check the recorder’s incoming bandwidth. Recorders have a total incoming (recording) bandwidth limit. When a new camera pushes the total over the limit, the last channels added may not record. The recorder’s channel or network status page usually shows the total.
  5. Check the disk group or quota. If disks are arranged in groups, or cameras have storage quotas, confirm this camera is assigned to a group that contains a healthy disk and has a quota above zero.
  6. Check licences on a VMS. On software VMS platforms, a camera without a recording licence may still appear in the device list. Check the licence status for that channel.
  7. Re-add the camera only as a later step. Deleting and re-adding a channel can reset its schedule, quota and motion settings. Note the current settings first.

If recordings have gaps

Short gaps every few minutes or hours, rather than nothing at all, usually point to the network or power.

  1. Look for video loss or disconnect entries in the log. Match their times to the gaps. If they line up, the camera really is dropping off.
  2. Check the camera’s uptime. A camera that has been up for only a few minutes is rebooting. On PoE, that often means the switch is out of power budget, the cable is long or poor quality, or the camera’s heater or IR draws more than its PoE class allows. See understanding PoE power budgets.
  3. Run a long ping. From a laptop on the camera network, ping the camera for ten minutes (ping -t on Windows, ping -c 600 on macOS or Linux) and count lost replies. Any loss on a wired camera network is a fault: check the patch cords, the cable run, the switch port error counters and duplex settings.
  4. Check for duplicate IP addresses. Two devices with the same address take turns being reachable. Compare MAC addresses in the switch or with arp -a to see whether the address moves between devices.
  5. Check the uplink. If many cameras share one uplink, total their bitrate against its capacity. An uplink running near full drops packets during busy scenes and playback. The camera bitrate lab totals streams against a link.

Prove the fix

  1. Start a manual recording for five minutes, then play it back. This proves the disk and stream path in minutes instead of waiting for tomorrow.
  2. Return the schedule to normal, and confirm the timeline shows the colour for the expected recording type (continuous or event).
  3. Check again after 24 hours, including the night. Night-time noise raises bitrate and can expose bandwidth or storage limits that daytime tests miss.
  4. Record what you changed. Write the setting, old value, new value, date and your name in the site log or service report.

To check whether the disks will hold the retention the site needs at the bitrate you now see, use the NVR storage sizing lab or the worked example in the storage guide.

When to call for help

Call the maintainer or an engineer when a disk must be replaced in a RAID array (a wrong step during a rebuild can lose the whole array), when firmware needs updating (back up the configuration first, and use only firmware published by the manufacturer for that exact model), or when the recorder itself reboots or freezes repeatedly.


This guide is general technical information written for installers, engineers and facility teams. Check the manuals for your exact equipment and follow site safety rules. Brand names identify products only; Foxnet University is independent of the manufacturers mentioned.

Talk to an engineer

Not sure which service fits?

Tell us what you are working on. A Foxnet engineer will point you to the right session, book or request — or tell you honestly if you do not need one.