Very often if happens customers need to confirm whether their instances are actually located in certain datacenters (DCs) or not. Also, my IP information shows the IPs in a CIDR format that could could be confusing. This trigger several questions.
Certain geo-location services online will show the Ips registered for the instances are in the US. Also, when reviewing the IP information in Hi, the information shows on a format IP/netmask that could be confusing.
Here are a few questions commonly asked related to firewall rules to open.
Which IPs do I have to open?
Answer. The recommended solution it to open up to all the ServiceNow IPs, which allows customer support to troubleshot and the greatest amount of flexibility and accommodation for migrations or datacenter moves.
Our full ServiceNow CIDR IP ranges (recommended):
|CIDR range||IP ranges equivalent|
For a more granular range, please use my IP information on Hi:
* KB0538621 - Finding the IP information for your instance
For example, consider the following extract for one instance:
Here are some additional questions and answers:
Q. If our instance are located in AMS and LHR DC, then why the IP on which our instance resolves is an IP of US (United States)?
Answer. As service-now is a US based company so as part of the cloud space IP registration all our IPs are registered in US but do not refer to the WHOIS website as that site is outdated. You can share the KB article about KB0656358 - ServiceNow Customer IP ranges over the datacenters to the customer so that he believe us that the IP to which his instance resolves actually belongs to the cloud space allocation of that specific DC.
NOTE: All our DC have their own cloud space IP allocation even when the geolocations shows in US incorrectly.
Q. What IP should we use when we need to establish an integration to customer network?
Answer. It depends if the customer has a VPN or not. Most customer do not have a VPN
Here are the reasons not to have a VPN (community link)
On this case (see above screenshot), the recommended solution is to open 188.8.131.52/21 and 184.108.40.206/21 for the primary and failover datacenter plus the IP addresses (VIP) of the instances.
Alternatively, (based on the screenshot) a more granular range can be achieved. IP depending on whether the customer has a VPN connection with us or not:
Without VPN: 220.127.116.11/29 and 18.104.22.168/29, plus your OWN VIPs (on this case 22.214.171.124)
With VPN: 126.96.36.199 and 188.8.131.52
Q. What IP should we use when we need a 3rd Party to connect to service NOW (As web service)
Answer. For all inbound connection to the instance, customer should send traffic to the IP on which his instance resolves, thus you OWN instance IPs (on this case 184.108.40.206)
It would be wise to open up the ranges, to cover IP moves, on this case the 149.x.x.x series
* KB0598826 IP address information - access and integration articles