Skip Navigation
Expand
  • Advanced SearchOpens new dialog
    Enter plus (+) or minus (-) signs in search terms to make a word required or excluded
    Search Tips
    Filter by product
    Filter by category
Getting the IP Address from Intelligent Advisor for Firewall Rules
Answer ID 12863   |   Last Review Date 05/22/2025

Can I get the IP address of incoming web service connection calls from Intelligent Advisor cloud, so I can use it in firewall rules in my on-premises environment?

Environment:
Intelligent Advisor
 
Resolution:

Step 1: Ping the Intelligent Advisor Site to Get the IP Address
•    Open a terminal or command prompt on your local machine.
•    Execute the ping command to determine the IP address of the Intelligent Advisor site. Replace yoursitename.custhelp.com with the actual site URL
>    ping yoursitename.custhelp.com

Example Output:

Pinging yoursitename.custhelp.com [205.223.86.79] with 32 bytes of data:
Reply from 205.223.86.79: bytes=32 time=134ms TTL=54
Reply from 205.223.86.79: bytes=32 time=141ms TTL=54
Reply from 205.223.86.79: bytes=32 time=135ms TTL=54
Reply from 205.223.86.79: bytes=32 time=129ms TTL=54

In this example, the IP address of the Intelligent Advisor site is 205.223.86.79.

 
Step 2: Configure Inbound Firewall Rules for the On-Premises Network
In the inbound firewall rules for the on-premises network either:

a) Allow communication coming from the entire subnet (205.223.86.0/24); or

b) Allow communication only from the Service Cloud outbound PAT at .254 so 205.223.86.254 in this example.

c) If an IPv6 address is returned, replace the last octet with fe. For example, 2a02:6900:8808:f000::4a75:cf40 becomes 2a02:6900:8808:f000::4a75:cffe

Important Note: 
If static IP addresses are allowed for the Oracle servers and the IP range happens to change, there might be serious impact to your site. Oracle Cloud Operations can never guarantee that all site related communication will always originate within specific IP addresses. Hardware maintenance, server failover, server rotation, network appliance failover and many other factors can contribute to communications originating from differing IP addresses over time. Additionally, there are times when a site can be migrated to a different pod with considerably varying IP addresses, either to mitigate loading issues or at the customer's request. You must ensure you have a process in place to modify the allowlist as soon as possible should the IP range changes. 
 
For options related to restricting access to your Intelligent Advisor site, see Answer ID 8452: Restricting computers or hosts that can access Oracle Policy Automation Hub, interviews and web service end-points
 
Conclusion:
By following these steps, you can obtain the IP address of incoming web service connection calls from the Intelligent Advisor cloud and configure your firewall rules accordingly. This ensures secure and controlled access to your on-premises environment.