Verkada cameras are equipped with an outside LED light status, which lets you know what’s happening at a glance. Newer models also have an interior LED that can help identify errors on the LAN or WAN.
Exterior LED statuses
On most Verkada cameras, you’ll find a white ring-shaped LED that illuminates the status of the camera. Depending on the camera model, this LED may dip to or flash different colors, which can indicate an event or the camera’s current status.
During regular operation, the camera uses only one color to communicate its status:
Solid orange: Camera is on and booting up
Flashing orange: Camera is updating firmware
Solid blue: Camera is running, connected, and recording data
Flashing orange+blue: Specific network error, see below
Solid red*: Contact Verkada Support
Flashing red*: Specific network error, see below
The initial boot sequence (solid orange) can take up to 20 minutes to reflect the correct LED status if the camera is unable to reach any endpoint.
* Only available on the CD63 and CF83
Status indicators on Command
Cameras also have a status indicator in Command to show the camera's status at a glance:
Orange status indicator: Camera is offline
Flashing Blue status indicator: Camera is downloading and upgrading firmware
Solid Blue status indicator: Camera is validating the new firmware version
Green status indicator: Camera is online
Green status indicator inside white circle: Camera is local streaming
Slowly flashing green status indicator: Live feed is buffering
CDx3 and CF83 network errors
In case the camera is unable to reach the required endpoints and services for regular operation, it attempts to communicate to Verkada Command by performing network checks.
After the camera conducts each of the network checks, it shows one of the LED statuses listed below.
Exterior LEDs
When the camera top cover is on, an error will be communicated through the outer status LED, which will flash a specific number of times depending on the error state.
LED Status | LAN Error | Initial Troubleshooting Step |
1 Red | Camera has not received an IP address. | Verify the cable and that the camera has received an IP assignment by a Dynamic Host Configuration Protocol (DHCP) server. |
2 Red | Camera has detected duplicate IP addresses on the LAN. | Identify and reconfigure one of the devices with a duplicate IP to use a unique IP address or enable DHCP to avoid conflicts. |
3 Red | Camera is not able reach the configured gateway. | Verify the camera's IP address, subnet mask, and gateway are correctly configured and verify the gateway is operational and accessible. |
4 Red | Camera is connected with Power over Ethernet (PoE), but is unable to connect to the switch. | Verify the physical layer status of the camera's Ethernet interface. |
5 Red | Camera is unable to resolve Verkada hostnames. | Verify the camera can reach a functioning DNS server. |
6 Red | Camera is unable to receive a response from the Network Time Protocol (NTP) server. | Verify the correct NTP server address is configured, and confirm that the server is reachable from the network. |
7 Red | Verkada endpoints are not reachable after booting up. | Check for firewall rules that may block access to Verkada endpoints. |
Interior LEDs
When the camera top cover is removed, the specific error will be communicated locally on the LAN or WAN debug LED, while the device status LED will show solid red.
LAN errors
LED Status | LAN Error | Initial Troubleshooting Step |
1 Red | Camera has not received an IP address. | Verify the cable and that the camera has received an IP assignment by a Dynamic Host Configuration Protocol (DHCP) server. |
2 Red | Camera has detected duplicate IP addresses on the LAN. | Identify and reconfigure one of the devices with a duplicate IP to use a unique IP address or enable DHCP to avoid conflicts. |
3 Red | Camera is not able reach the configured gateway. | Verify the camera's IP address, subnet mask, and gateway are correctly configured and verify the gateway is operational and accessible. |
4 Red | Camera is connected with Power over Ethernet (PoE), but is unable to connect to the switch. | Verify the physical layer status of the camera's Ethernet interface. |
WAN errors
LED Status | WAN Error | Initial Troubleshooting Step |
1 Red | Camera is unable to resolve Verkada hostnames. | Verify the camera can reach a functioning DNS server. |
2 Red | Camera is unable to receive a response from the Network Time Protocol (NTP) server. | Verify the correct NTP server address is configured, and confirm that the server is reachable from the network. |
3 Red | Verkada endpoints are not reachable after booting up. | Check for firewall rules that may block access to Verkada endpoints. |
All other camera's network errors
If a camera cannot reach the required endpoints and services for regular operation, it attempts to communicate to Verkada Command by performing network checks.
After the camera conducts each network check, it shows one of the LED statuses listed below.
Flashing blue LED
The camera is unable to connect to Verkada Command.
The flashing blue LED status only appears on cameras running factory firmware. Once the camera connects to Command and updates to the latest firmware, it only uses the granular LED statuses listed below.
Blue+orange LEDs
LED Status | Network Error | Initial Troubleshooting Step |
1 Blue 1 Orange | Camera is connected with Power over Ethernet (PoE), but is unable to connect to the switch. | Verify the physical layer status of the camera's Ethernet interface. |
1 Blue 2 Orange | Camera has not received an IP address. | Verify the camera has received an IP assignment by a Dynamic Host Configuration Protocol (DHCP) server. |
1 Blue 3 Orange | Camera is not able reach the configured gateway. | Verify the camera's IP address, subnet mask, and gateway are correctly configured and verify the gateway is operational and accessible. |
1 Blue 4 Orange | Camera has detected duplicate IP addresses on the LAN. | Identify and reconfigure one of the devices with a duplicate IP to use a unique IP address or enable DHCP to avoid conflicts. |
1 Blue 5 Orange | Camera is unable to resolve Verkada hostnames. | Verify the camera can reach a functioning DNS server. |
1 Blue 6 Orange | Camera is unable to receive a response from the Network Time Protocol (NTP) server. | Verify the correct NTP server address is configured, and confirm that the server is reachable from the network. |
1 Blue 7 Orange | Camera is unable to certify the Secure Sockets Layer (SSL) connection, likely due to SSL inspection. | Validate the certificate presented to the camera while attempting a Transport Layer Security (TLS) handshake with Verkada endpoints. |
1 Blue 8 Orange | Verkada endpoints are not reachable after booting up. Note: This LED status is only shown if at least 1 endpoint is unreachable. | Check for firewall rules that may block access to Verkada endpoints. |
Endpoints used for network diagnostics
There are multiple endpoints that a camera can use, depending on which features are enabled. For LED statuses, only the endpoints that are crucial for camera operation are tested and are reflected on the LED statuses.
US
Here is the list of endpoints that are tested:
*.kinesisvideo.us-west-2.amazonaws.com - TCP+UDP/443
*.us-west-2.compute.amazonaws.com - TCP+UDP/443
*:4100 - TCP/UDP on LAN (only required for local streaming)
EU
*.kinesisvideo.eu-west-1.amazonaws.com - TCP+UDP/443
*.eu-west-1.compute.amazonaws.com - TCP+UDP/443
*:4100 - TCP/UDP on LAN (only required for local streaming)
US and EU (NTP servers)
In addition to those endpoints, for time synchronization reachability to the following time, the camera verifies the servers:
NTS servers
time.cloudflare.com - TCP/4460
time.cloudflare.com - UDP/123
NTP servers
time.control.verkada.com - UDP/123
Network Time Security (NTS) uses Secure Socket Layer (SSL) for secure time synchronization, unlike NTP. We recommend exempting these connections from SSL decryption policies.
Prefer to see it in action? Check out the video tutorial.
Need more help? Contact Verkada Support.