Verkada devices are designed to maintain your network’s security while still offering remote access and easy management of your devices. In most cases, little to no updates to your network settings are required. Depending on your particular case, however, some configuration may be required to get your devices online.

If your network is configured properly as per the instructions below, and you still cannot get your device online, please reach out to Verkada Support and try to use this guide to provide a packet capture to the team so we can best solve your issue.

Verkada devices must be assigned a routable IP address via DHCP. For network security reasons, static IP addresses are not currently supported. A DHCP reservation is a hassle-free way to ensure the device receives a specific IP address. You need the camera's MAC address to create a reservation. The MAC address of an AC41 can be found on the sticker below the cable management compartment.

Verkada devices require a DNS server to be able to resolve specific domains in order to communicate with Verkada Command. DNS servers can only be set with DHCP. Verkada devices will always query DNS servers via the standard destination port 53 using UDP. DNS over HTTPS (DoH) is not currently supported.

Verkada devices need to communicate with specific domains owned by Verkada to provide you with a full-featured experience. All communication between a Verkada device and the Verkada servers uses HTTPS (TCP/443). Additionally, all devices synchronize their time using NTP (Bi-directional UDP/123).

When Verkada devices communicate with Verkada servers, connections are made outbound from your LAN to our servers over the internet. As per standard IP communication practices, the source port will fall into the ephemeral port range (49152-65535).

Note: If bandwidth is a concern we recommend utilizing both upload and download traffic shapers on the network.

You can use the following links to jump to the relevant sections:

All Verkada devices require the following access:

The above can also be shortened as:

Note: Most devices will also require additional access, outlined in the below sections

The Verkada next-generation video streaming capability requires the following access:

If you are using cloud backup on your cameras, the following is also required:

To allow NTS time synchronization:

Note: NTS will use SSL for secure time synchronization, unlike NTP. It is recommended to exempt these connections from SSL decryption policies.

Access control devices require the following additional access:

In addition to those required for cameras and access control, intercom devices (including TD52 and Desk Station) require the following additional access:

The Desk Station and Pass app require these additional endpoints if they are set as an Intercom Receiver:

This table explains how the above ports are used for your reference:

Alarms devices require the following additional access:

Alarm Consoles (BC51) require the following additional access:

Note: Alarm consoles also require access to Apple servers, please refer to the Apple section

Sensor devices require the following additional access:

Viewing stations require the following additional access:

Note: Viewing stations also require access to Apple servers, please refer to the Apple section

Guest apps/iPads might require the following additional access:

The alarm console (BC51) and viewing stations (VX51 and VX52) all run on Apple hardware, and therefore require the following access:

In order to ensure reliable delivery of Verkada emails (including event notifications, password reset emails, and magic links) the following email domains should be whitelisted on your mail server.

Verkada devices are incompatible with LANs that require the use of proxy servers or that require SSL/TLS inspection. If either are in use, a bypass for all Verkada devices must be put in place in order for Verkada devices to communicate with Verkada Command.

Visit Training Center for bite-sized video tutorials on how to accomplish role-based tasks in Command.