What are the IP addresses used to connect via IPsec to the Threatpulse Cloud?



What are the IP addresses used to connect via IPsec to the Threatpulse Cloud?
What is the IP address for the closest data pod?
Formerly known as KB4567.


Here is a list of IP addresses for the various data pods as of December 8, 2014:

LocationIP address(es)
Portal addresses
Frankfurt, Germany*
Helsinki, Finland*
Johannesburg, South Africa**
London West, England Site #1*
London South, England Site #2*
Madrid, Spain**
Milan, Italy**
Oslo, Norway**
Paris, France*
Stockholm, Sweden*
Tel Aviv, Israel**
Zurich, Switzerland**
Buenos Aires, Argentina**
Chicago, Illinois*
Dallas, Texas*
Denver, Colorado**
Mexico City, Mexico*
Miami, Florida*
Montreal, Canada*
New York, NY*
Sao Paulo, Brazil*
Seattle, Washington*
Sunnyvale, California*
Toronto, Canada*
Washington, DC*
Ashburn, Virginia*
Chennai, India*
Hong Kong**
Mumbai, India*
New Zealand*
Seoul, South Korea*
Shanghai, China* (Site active end of business on 10 December 2014 PST.)
Singapore**** (Load balancer IP available on 11 December 2014 @ 17:00 UTC);

Sydney, Australia*
Taipei, Taiwan*
Tokyo, Japan*

*Site has multiple data pods behind a load balancer.
** Site has a single data pod and does not have a load balancer.  IPsec customers are advised to have secondary tunnels to another data center as a backup.
*** Site has NO load balancer.  IP addresses are for the individual pods.  Please note that a load balancer will be added soon.

Please note that Blue Coat recommends that you should have at least two backup tunnels configured, with at least one tunnel to a geographically different pod.

Examples:  If your primary pod is London Site #1, you may want to make backup tunnels to London Site #2, and Paris.  If your primary pod is Chicago, you may want to make a backup to Washington and Miami or New York.

For a list of auth IPs, please see 000008077. If you want a list of the egress IP addresses, please see 000014870

For a list of WebPulse IPs, please see 000014742.  

Additional Information
Bug Number
InQuira Doc IdKB4567

Article Feedback

Did this Article solve your issue?
Additional Comments:
Previous MonthNext Month