Sonar IP Addressing

Kristen Fiddes Updated by Kristen Fiddes

Read Time: 1 min

Unlike the legacy version of Sonar, Sonar V2 exists as a series of containers within Azure, with front end devices and NAT handling traffic flow (see our blog post for details). Most Sonar V2 instances are located in our US Azure data center have these ingress and egress IP addresses:

  • Ingress/Inbound IP Address: (a.k.a.,
  • Egress/Outbound IP Address:,, and (a.k.a.,

Canadian V2 instances are located in our CA Azure data center, and therefore use a single IP for both inbound and outbound traffic:

  • Ingress/Inbound/Egress/Outbound IP Address: (a.k.a.,



Ingress / Inbound

These terms are synonymous - they both represent the address you would “point at” if you were initiating a connection that was from outside the instance but destined to the instance.

Egress / Outbound

These terms are synonymous - they are used to define the address that you would expect to see when the instance initiates traffic destined for somewhere outside the instance.

Ingress and Egress IP addresses will need to be added to your network management devices and your firewall in the event DHCP and RADIUS is being used.

Additional IPs to Note

Support Access IPs
  1. Hardware/Client Equipment access IP
  2. Instance Access/Application Firewall Access IP
Looker SFTP IPs:

How did we do?

Building a Device Mapper

Automating IP Assignments, Data Rates, and Network Access in Sonar