Verify Your Verkada Camera's Network Configuration
If your Verkada camera is missing recordings, start by validating the network configuration. Begin with the Network Diagnostics tool in Verkada Command, which provides real-time metrics for latency, packet loss, and bandwidth usage. Focus on the Bandwidth Monitor to identify congestion points, particularly if multiple cameras share the same subnet. Ensure the camera's VLAN matches the switch port configuration, as mismatched VLANs can block ONVIF discovery and prevent successful VMS integration. If multicast/IGMP snooping is enabled on the switch, this can interfere with ONVIF traffic, so disable it temporarily during troubleshooting. Finally, check the Device Health dashboard for firmware updates—pending updates may cause recording gaps if applied during critical periods.
Check VLAN Assignment
Verify the camera's VLAN in Verkada Command → Cameras → [device] → Network Settings. Cross-reference this with the switch port configuration. If the VLANs differ, reassign the camera to the correct VLAN and restart the device. If the switch supports VLAN tagging, ensure the camera is configured for 802.1Q tagging. For PoE cameras, confirm the switch port is set to Class 3 or higher to support 4K resolution. If the port shows Class 0, the switch may not be negotiating PoE correctly, leading to power failures.
Validate PoE Budget
Access the Power Budget section in Verkada Command → Devices → [switch] → Network Settings. Confirm the camera's PoE requirement (802.3af/at) is within the switch's allocated budget. If multiple cameras share the same PoE budget, consider upgrading to a PoE++-capable switch. For CD62 Dome or CB62 Bullet cameras, ensure the switch port is configured for 4K resolution—lowering the stream profile to 'Sub' may reduce bandwidth but will also lower resolution. If the camera shows offline in the VMS dashboard but responds to ping, this often indicates a DHCP lease exhaustion issue. Renew the camera's IP address via Verkada Command → Cameras → [device] → Network Settings → Renew Lease.
Confirm Firmware Channel
Navigate to Verkada Command → Cameras → [device] → Firmware. Ensure the camera is registered to the correct firmware channel (stable/beta). If updates are pending, apply them using the Firmware Update tool. Avoid staged rollouts during critical recording periods. If the camera is part of a large deployment, use Bulk Firmware Management to apply updates to multiple devices simultaneously. If the firmware update gets stuck, reset the camera by deregistering it from Verkada Command and re-registering it after 10 minutes.
Test RTSP Stream
In Verkada Command → VMS Integration → Camera Settings, verify the Stream Profile is set to 'Main' for 4K resolution or 'Sub' for lower bandwidth. Test the RTSP URL directly in a browser: rtsp://[camera_ip]:55/stream (replace [camera_ip] with the camera's actual IP). If the stream fails, check the ONVIF Profile compatibility and ensure the authentication mode is set to basic or digest. For CB62 Bullet cameras, confirm the RTSP port is open on the switch and not blocked by a firewall. If the stream is intermittent, reconfigure QoS policies on the switch to prioritize video traffic.
Diagnose Verkada Command Connectivity Issues
If the camera is not appearing in Verkada Command or showing as offline, begin by checking the Cloud Connectivity status in Verkada Command → Analytics → Event Logs. Ensure the camera is registered to the correct region and that Cloud Connectivity is active. If the camera is part of a hybrid deployment (local storage + cloud backup), confirm the local storage is not full. Use the Motion Search feature in Verkada Command to highlight movement in specific areas of the frame—this can help identify if missed recordings are due to detection sensitivity gaps. If the camera is not sending events to the cloud, enable Person/Vehicle Detection under Camera Settings and ensure the camera has a minimum of 40 pixels per foot resolution for reliable AI processing.
Check VMS Integration
In Verkada Command → VMS Integration → Camera Settings, verify that the Stream Profile is set to 'Main' for 4K resolution or 'Sub' for lower bandwidth. If the camera is not recording to the VMS, ensure the VMS is licensed for the number of cameras connected. For large deployments, use Bulk VMS Configuration to apply settings to multiple devices simultaneously. If the VMS is not receiving footage, check the VMS Database for corruption and repair it using the Database Consistency Check tool. If the VMS is not compatible with the camera's ONVIF profile, reconfigure the camera to use a compatible profile (e.g. Profile S or Profile G).
Advanced Troubleshooting and Enterprise Support
If basic fixes fail, proceed to advanced diagnostics. Use the Packet Capture tool in Verkada Command to analyze network traffic between the camera and the VMS. Look for dropped packets or TCP retransmissions that could indicate network congestion. If the issue persists, initiate a VMS Database Repair via Verkada Command → VMS Integration → Database Tools. For large enterprises, use Enterprise Support Escalation to contact Verkada's support team directly. Provide them with the Packet Capture file, Device Health metrics, and Event Logs from Verkada Command. If the camera is part of a hybrid deployment, ensure the local storage is not full and that the cloud backup is configured correctly. For CD62 Dome or CB62 Bullet cameras, confirm the PoE budget is sufficient and that the switch port is set to Class 3 or higher.
Root Causes and Enterprise Considerations
Missed recordings in Verkada cameras often stem from network instability, firmware incompatibility, or VMS licensing issues. In enterprise deployments, DHCP scope exhaustion can cause cameras to lose connectivity if the VLAN is not properly configured. PoE budget exhaustion on switches can lead to power failures, particularly in deployments with multiple 4K cameras. Firmware incompatibility after staged rollouts may prevent cameras from recording correctly, so always verify firmware channels before applying updates. In the UK, ensure compliance with Building Regulations Part Q for data security and GDPR retention policies when configuring storage timelines. If the camera is not recording due to cloud connectivity issues, ensure the camera is registered to the correct region and that Cloud Connectivity is active in Verkada Command.
Prevention and Long-Term Care
To prevent missed recordings, schedule firmware updates during off-peak hours and use Bulk Firmware Management for large deployments. Monitor VMS health using the Database Consistency Check tool and ensure QoS policies prioritize video traffic. For PoE switches, allocate 20% headroom in the power budget to accommodate unexpected increases in camera density. Use Dedicated VLANs for cameras to isolate them from other network traffic. Regularly check Event Logs in Verkada Command for signs of AI analytics failures or cloud connectivity issues. Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera systems. scOS uses permanently powered cameras connected via ethernet.
Replacement Decisions and Lifecycle Management
If troubleshooting exceeds 30 minutes without success, consider hardware replacement. Wired cameras (e.g. CD62 Dome, CB62 Bullet) typically last 5-8 years, while battery-powered models degrade after 3-5 years. For VMS systems, replace surveillance-rated HDDs every 3-5 years to avoid data loss. Use high-endurance microSD cards for hybrid deployments. In the UK, the Consumer Rights Act 2015 provides a 6-year right to bring a claim for faulty goods for faulty goods. If hardware replacement is needed, initiate the RMA process via Verkada's support portal and provide Packet Capture files for expedited resolution.