About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Last updated: Jan 12, 2024
To allow Spark to access data that is located behind a firewall, you add the appropriate IP addresses for your region to the inbound rules for your firewall.
Dallas (us-south)
- dal12 - 169.61.173.96/27, 169.63.15.128/26, 150.239.143.0/25, 169.61.133.240/28, 169.63.56.0/24
- dal13 - 169.61.57.48/28, 169.62.200.96/27, 169.62.235.64/26
- dal10 - 169.60.246.160/27, 169.61.194.0/26, 169.46.22.128/26, 52.118.59.0/25
London (eu-gb)
- lon05 - 141.125.70.64/26
- lon06 - 158.176.84.0/27, 158.176.166.128/26
- lon04 - 158.175.122.160/27, 158.175.170.128/26
Frankfurt (eu-de)
- fra04 - 161.156.76.64/27, 161.156.115.192/26
- fra05 - 149.81.74.128/27, 149.81.187.192/26
- fra02 - 158.177.124.32/27, 158.177.101.16/28, 158.177.166.0/26
Tokyo (jp-tok)
- tok02 - 169.56.44.128/25
- tok04 - 128.168.71.128/25
- tok05 - 165.192.72.0/25
Parent topic: Configuring firewall access
Was the topic helpful?
0/1000