Verify Your Verkada Camera's Time Synchronisation Issues
Incorrect timestamps on Verkada camera footage can compromise forensic integrity. Common causes include misconfigured NTP settings, daylight saving errors, or firewall blocking NTP traffic. This guide provides brand-specific tools in Verkada Command to resolve these issues quickly.
Quick Fixes for Verkada Timestamp Errors
Before diving into advanced diagnostics, perform these 30-second checks:
- Check VMS dashboard: In Verkada Command, navigate to Cameras → [device] → Diagnostics. Look for NTP Sync Status and Time Drift alerts.
- Verify PoE link light: Ensure the camera's PoE port on the switch shows Class 3 (4K resolution). A Class 0 indication suggests power budget exhaustion.
- Ping camera IP: From your management PC, ping the camera's IP address. If it fails, check VLAN assignments or firewall rules.
- Check status LED: A solid red LED on the camera indicates a critical error (e.g. NTP sync failure). A flashing blue LED suggests a firmware update is pending.
- Power cycle via PoE: Disable the switch port for 10 seconds, then re-enable. This resets the camera's network stack without requiring a factory reset.
Diagnose Verkada Command Connectivity Issues
Check NTP Server Configuration
In Verkada Command, go to Cameras → [device] → Configuration → Time & Date. Ensure the NTP Server field is populated with a valid address (e.g. pool.ntp.org). If manual time correction is needed, use the Set Time Manually option. Confirm Daylight Saving Auto-Adjust is enabled. If the camera's time drifts by more than 5 minutes, this feature may be disabled.
Use the Time Sync Diagnostic Tool
Navigate to Cameras → [device] → Diagnostics → Time Sync Diagnostic. This tool runs a 60-second test to measure NTP latency and identify firewall blocks. If the tool reports NTP traffic blocked, adjust your network firewall to allow UDP 123 on the camera's VLAN. For UK users, ensure your ISP router does not enforce double NAT (common with Virgin Media Hub 5x).
Validate VMS Integration Settings
For cameras integrated with third-party VMS platforms (e.g. Milestone XProtect, Genetec), check the RTSP stream URL in Verkada Command (Cameras → [device] → Integration → Stream Profile). Ensure the URL uses RTSP://[camera IP]:554/Streaming/Channels/101 and the ONVIF profile is set to Profile 1 (default). If the VMS platform shows timestamps as incorrect, re-provision the camera via Camera → Re-register in Verkada Command.
Confirm Firmware Channel Settings
Access the Firmware Channel in Verkada Command (Cameras → [device] → Firmware). Ensure the camera is on the Stable channel unless instructed otherwise. If a recent update caused timestamp errors, initiate a Firmware Rollback via Firmware → Rollback. For enterprise deployments, use Staged Rollout to isolate affected devices before full deployment.
Check for Cloud Connectivity Issues
For cloud-managed Verkada cameras, navigate to Cameras → [device] → Device Health. Ensure Cloud Connectivity is marked as Active. If it shows Disconnected, verify your internet gateway allows TCP 443 and UDP 53 (DNS). For UK users, confirm your ISP does not enforce CGNAT (common with EE/Three/Vodafone mobile broadband), which blocks remote access.
Verkada Advanced Troubleshooting Guide
Perform a Packet Capture Analysis
Use the Packet Capture Tool in Verkada Command (Tools → Network Diagnostics). Filter for NTP (UDP 123) packets and check for latency or packet loss. If NTP traffic is blocked, adjust firewall rules to allow UDP 123 on the camera's VLAN. For UK-specific issues, ensure your ISP router does not enforce double NAT (common with Virgin Media Hub 5x).
Repair VMS Database Corruption
If timestamp errors persist across multiple cameras, check for VMS database corruption. In your VMS platform (e.g. Milestone XProtect), run a Database Consistency Check. If corruption is detected, initiate a Database Repair or restore from backup. For Verkada cameras, ensure the Camera Registration ID in the VMS matches the one in Verkada Command.
Escalate to Enterprise Support
If all steps fail, contact Verkada Enterprise Support via help.verkada.com. Provide the Camera Serial Number, Firmware Version, and Time Sync Diagnostic Report. For UK users, request an RMA if hardware failure is suspected. Enterprise support offers 24/7 SLA for mission-critical deployments.
Root Causes of Verkada Timestamp Errors
Common enterprise causes include:
- NTP firewall blocking: UDP 123 ports blocked on the camera's VLAN.
- Daylight Saving misconfiguration: Auto-adjust disabled in Verkada Command.
- VMS integration conflicts: Incorrect RTSP stream URL or ONVIF profile.
- Firmware incompatibility: Recent update caused timestamp drift.
- UK-specific issues: Double NAT or CGNAT disrupting NTP sync.
Long-Term Verkada Maintenance Tips for Verkada Cameras
Schedule Firmware Updates
Use the Firmware Channel in Verkada Command to schedule updates during off-peak hours. For enterprise deployments, enable Staged Rollout to test updates on a subset of cameras first.
Monitor Network Health
Create a dedicated VLAN for Verkada cameras and apply QoS policies to prioritise NTP traffic (UDP 123). Use SNMP monitoring to track PoE budget usage and detect power exhaustion.
Enable Edge Storage Failover
For cloud-managed cameras, configure Edge Storage Failover in Verkada Command. This ensures footage is stored locally if cloud connectivity is lost, preserving timestamp accuracy.
Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.