Skip to main content
Alarm Network Settings

Learn about the required network settings for Verkada Alarms

Updated over a month ago

This article is a guide for new Alarms. Refer to this article if you have classic Alarms. See New Alarms vs Classic Alarms if you are unsure which version of Alarms you have.


This article outlines the required network settings that your Verkada Alarms devices need to communicate with Verkada Command. For more information on the required network settings for other Verkada product lines see Required Network Settings.

Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command.

IP address

Alarms devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Alarms devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.

If you require your Alarm device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device's label).

Domain Name System

Alarms devices use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Alarms device where the DNS server is on the network and the Alarms device communicates using UDP port 53.

DNS over HTTPS (DoH) is currently not supported.

Firewall settings

Alarms devices require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the devices to communicate with the general required endpoints.

These are the general domains to allow, applicable for all organization-regions:

34.216.15.26 - UDP/123
*.verkada.com - UDP/123 + TCP+UDP/443
*.appcenter.ms - TCP/443
global.turn.twilio.com - TCP/443
time.cloudflare.com - TCP/4460
time.cloudflare.com - UDP/123

If your firewall does not allow wildcard masking, or you prefer to have the entire FQDN of the endpoint in your firewall rules, you can add the domains to your allowlist based on the region your devices are in.

Region: United States

vprotect.control.verkada.com - TCP+UDP/443
34.216.15.26 - UDP/123
api.control.verkada.com - TCP+UDP/443
api.global-prod.control.verkada.com - TCP+UDP/443
device-nlb.verkada.com - TCP+UDP/443
firmware.control.verkada.com - TCP+UDP/443
index.control.verkada.com - TCP+UDP/443
nlb.verkada.com - TCP+UDP/443
relay.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
update.control.verkada.com - TCP+UDP/443
vconductor.command.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
*.appcenter.ms - TCP/443
global.turn.twilio.com - TCP/443

BZ11s in all regions require these endpoints:

global.stun.twilio.com - UDP/3478
global.turn.twilio.com - UDP/3478

Need more help? Contact Verkada Support.

Did this answer your question?