Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Networking

Sonar IP Addressing

Written by Mitchell Ivany

Updated at March 15th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Our Products & Services
  • Getting Started
    First Time Setup Baseline Configuration
  • Accounts
  • Communication
  • Billing
  • Companies
  • Financial
  • Integrations
  • Inventory
  • Jobs
  • ​Mapping
  • Misc.
  • Monitoring
  • Purchase Orders
  • Release Notes
  • Sonar Billing
  • Voice
  • Reporting
  • Security
  • sonarPay
  • Ticketing
  • Working With the Sonar Team & Additional Resources
    Sonar's Security Practices & Certifications
  • System
  • Networking
+ More

Table of Contents

Term Explanation Additional IPs to Note

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: 52.185.67.212 (a.k.a., sonar-prod-az-1.sonar.software)
  • Egress/Outbound IP Address: 20.221.112.37, 20.221.114.13, and 52.158.209.86 (a.k.a., sonar-prod-az-1-egress.sonar.software)

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: 20.104.33.4 (a.k.a., sonar-prod-canadaca-1.sonar.software)

Term

Explanation

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
    1. 52.185.28.83
  2. Instance Access/Application Firewall Access IP
    1. 20.84.183.202
Looker SFTP IPs:
  • 34.200.64.243
  • 54.157.231.76
  • 18.206.32.254
acoustic addressing echo location

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Assigning an IP Address Using Sonar's IPAM: How to
  • Automating IP Assignments, Data Rates, and Network Access in Sonar
  • Building Address Lists
Expand