A camera showing offline is one of the few faults in a security system where an owner can genuinely help — not because the work is easy, but because the most useful information about it (what else stopped, when it started, what happened on site that week) lives with you, and half of it is forgotten by the time a technician arrives.
So: a checklist, in order, from most likely and easiest to least likely and hardest. Fifteen minutes covers all of it. Some steps will fix the problem outright; the rest turn "camera four is down" into a report that tells us what to bring.
One boundary, not negotiable. Nothing here asks you to open an electrical panel, a hardwired power supply, or any enclosure with mains wiring inside it. If a step ends at a locked door or a cover with a warning label, that is the end of the step.
This is about a camera that is offline — recorder says disconnected, no live picture, grey tile in the app. Cameras that are online but produce no footage are a different fault, covered in why isn't my security camera recording.
Step 1: One camera, or several?
Ask this before touching anything, because the answer cuts the diagnosis in half. Open the recorder or the app and look at the whole camera list, not just the one somebody complained about.
Several cameras offline points upstream, to something they share: the switch that powers them, the power feeding that switch, or a network change that renumbered everything. If the offline ones are all in one wing, or all outdoors, the grouping tells you which shared thing failed.
One camera offline points at that camera or the cable running to it. Everything it shares with the others is evidently working, because the others are fine.
That split decides whether the rest of your fifteen minutes is spent in the communications room or standing under one camera. Either way, write down which cameras are offline by location. "Camera four" means nothing to anyone who does not use your system daily; "the two on the loading bay and the one over the west door" means something to everyone.
Step 2: What changed, and when did it start?
The second most productive question, and the one owners answer best.
Fix the start time as precisely as you can. The camera list often shows a last-connected time, and playback shows the last frame the camera ever sent — scrub back until the picture appears and note that timestamp. That is your fault time, and it is worth more than any other single fact you can give us. Then look at what happened around it:
- A power event. An outage, a flicker, a tripped breaker, generator testing. Equipment that has run for two years often does not survive being switched off and on again; that is when a marginal power supply or a tired switch finally quits.
- Electrical or trades work. New lighting, a renovation, ceiling tiles up, a tenant fit-out. Cables get moved, unplugged, occasionally cut. If the camera went offline the same afternoon someone was working above that ceiling, you have found the answer.
- A network change. A new router, a new internet provider, a modem swap, a technician who "refreshed" the equipment. This is the classic cause of everything going offline on one day while every camera is still healthy and powered — the recorder is looking for them at addresses that no longer exist.
- New equipment on the network. An access point, a switch, a device installed by somebody else's contractor. Two devices given the same address knock each other offline.
- Weather. Covered in step 6, but note the day's weather now.
If a change and a failure share a day, the change is usually the cause.
Step 3: Look at the switch — link light and PoE light
Most modern cameras are powered and networked by one cable from a network switch, an arrangement called Power over Ethernet. That switch sits in your communications room, and its front panel is a status board you are allowed to read.
Each port typically has a link indicator, and many switches have a separate PoE indicator showing power is being delivered. Read them together:
- No link, no PoE. Nothing is happening on that port: broken cable, dead camera, or a disabled port.
- PoE on, link off. Power is going out, nothing is coming back. Often a damaged cable or a failed camera.
- Both lit, camera still offline. Cable and power are fine, which moves suspicion to addressing and configuration — step 5.
Two safe things you may do: note which ports are lit, and unplug one camera's cable from the switch, wait ten seconds, and plug it back into the same port — a power-cycle for that camera, which sometimes recovers one that has hung. Label the port first. Do not shuffle cables between ports to test them; without a record of the original layout that turns one fault into several.
If the whole switch is dark, that is the finding. Do not go hunting for its power source in a panel.
The power budget case: several cameras, cold weather, intermittent
One pattern is worth recognizing on sight, because it gets misdiagnosed for months.
A PoE switch has a total power budget shared across all its ports, and it is not the port count multiplied by what one port can deliver. Exterior cameras with heaters and infrared illuminators draw far more on a cold winter night than on the summer afternoon when the switch was sized. When demand crosses the budget, the switch protects itself by dropping power to some ports.
The signature: several cameras drop on cold nights, not always the same ones, mostly exterior, and they return by themselves as the day warms up, so every site visit finds a working system. That is not a camera fault, and replacing cameras or re-terminating cables will never fix it — the cause is arithmetic in the communications room. Full explanation in PoE power budget. If your dropouts fit, say so when you call.
Step 4: Is the problem the recorder rather than the camera?
Before condemning a camera, check that the thing reporting it offline is healthy. If every camera is offline at once, the recorder is the prime suspect, not thirty cameras that failed simultaneously. Check it is powered and responding, that its network connection is live, and whether it has rebooted recently. A recorder that is frozen or has lost its network reports a wall of disconnected cameras that are all working perfectly.
Restarting it from its menu is safe, as is removing power at the plug and restoring it after thirty seconds. If everything returns, that is a finding, not a cure — a recorder that needs restarting has a problem underneath.
And here is the point that catches people out when everything comes back: a live picture is not proof of recording. Live view and recording are separate jobs. Once an offline camera returns, go into playback, pick a time a few minutes ago, and confirm footage exists for it. Cameras that drop off and rejoin sometimes come back without rejoining the recording schedule, and you will not find out until the day you need the footage.
Step 5: Does the camera respond on the network at all?
Optional, and aimed at whoever looks after your IT; if that is not you, skip it. Every camera has a network address, listed on the recorder's camera management page, and someone on that network can test whether the camera answers there. The result is diagnostic either way: if it answers but the recorder still calls it offline, the fault is configuration — credentials, a changed address, a port setting — and no ladder is required. If it answers nothing, it is power or cable, and a ladder probably is. Check that page for two devices claiming the same address, too; collisions produce exactly this symptom.
Step 6: The physical checks — from the ground
Last, because it is the most effort — but the fastest when it is obvious.
Has something been unplugged? More often than anyone admits. Cameras fed by a small plug-in power injector are especially vulnerable — the injector looks like a spare adapter to anyone hunting for a socket. If yours runs from a visible injector at a wall outlet, check it is plugged in and lit. Anything hardwired is not yours to touch.
Has a cable been damaged? Look along whatever run you can see from the floor: trades work above ceilings, a delivery truck against an exterior wall, a snagged cable in a parking structure, rodents in a roof space. Visible damage is a complete finding — photograph it.
Is the run outdoors, and has the weather changed? Outdoor connections that were never sealed properly let moisture in, and moisture plus copper equals corrosion. Corroded connections fail intermittently and correlate with weather — the camera drops out when it rains and returns when things dry. From the ground, look for green or white crust on fittings, a junction box hanging open, a cracked jacket, or a run stapled to a wall instead of in conduit.
The camera itself. Hanging loose, hit by a vehicle, knocked out of aim, a water-filled dome.
What you should not do is go up a ladder to poke at connections. Roof-edge positions are not worth a fall, and disturbing a wet connection makes the fault worse right before a technician arrives to diagnose it.
What to write down before you call
This is the part that saves you money. A fault reported well is often a one-visit repair; the same fault reported as "a camera is down" is frequently two, because the first visit is spent discovering what you already knew.
- Which cameras are offline — by location, not channel number. And how many are not offline; the ratio matters.
- When it started — last-connected time, or the timestamp of the last footage. Approximate is fine; "sometime last month" is not.
- Constant or intermittent — and if intermittent, when it drops and when it returns. Nights, cold mornings, during rain. A pattern is a diagnosis.
- What changed — outage, contractor, network equipment, new tenant, renovation, storm. Include things you think are unrelated; several classic causes look unrelated.
- What you already checked — switch lights, a recorder restart, an injector found and re-plugged, what you could see of the cable run. Include what did not work, which stops us repeating it.
- Photographs — the recorder's camera list showing the offline entries, the switch front panel, and any visible cable or camera damage. A photograph of a status panel answers questions nobody thought to ask on the phone.
- Access constraints — locked communications room, a tenant who must be notified, a lift required for high positions, restricted hours.
Item seven is the sleeper. A large share of second visits happen because the first technician could not get into the room or could not reach the camera.
Where the line is between your job and ours
Yours, safely: reading status lights and camera lists; noting times and patterns; power-cycling a recorder at its plug or menu; re-plugging a low-voltage injector at a wall outlet; re-seating one labelled cable at the switch; looking at cable runs from the ground; taking photographs.
Ours: anything on a ladder, anything inside an enclosure, anything involving a panel or hardwired power, testing and re-terminating cable, measuring what a switch actually delivers against its budget, and reconfiguring addressing.
The first list costs fifteen minutes and frequently either fixes the fault or names it. The second needs someone insured to be up there.