Action Required: Changes to IP range utilized by AirWatch SaaS environments

Action Required: Changes to IP range utilized by AirWatch SaaS environments

The AirWatch Cloud Operations team will be implementing networking changes to our Atlanta Based Data Centers.  If you currently utilize an AirWatch SaaS environment and it is hosted in the US (excluding the US Federal environment), the following changes apply to you.  This change also applies to any on-premise customers that use SaaS-hosted services, such as App Wrapping, Auto Discovery, or the Cloud Notification Service.

AirWatch will begin using new IP addresses for outbound network traffic from these datacenters. If you are currently whitelisting inbound traffic for any on-premise components utilizing AirWatch (including devices themselves, MAGs, SEGs, etc), this communication will now come from a new IP address.  These changes will be implemented on November 5th, 2016 (for Shared UAT- CN135/137/138 - and Shared Partner Demo – CN800/801/802 - environments) and November 12th, 2016 (for all production and dedicated UAT environments).  Make sure the IP address below are whitelisted in order to avoid any disruption of service after these changes are made.

  • USA: 63.128.77.234
  • USA: 209.66.96.114
  • USA: 63.128.77.238
  • USA: 209.208.228.192
  • USA: 209.208.228.198
  • USA: 216.235.137.253

A full list of IP ranges utilized by AirWatch is available in the myAirWatch Knowledge Base here.

Have more questions? Submit a request

0 Comments

Article is closed for comments.