This article lists the public IP ranges for the PoP locations in the Cato Cloud and the geo-localized ranges for countries that currently don't have a PoP. For your convenience, you can download the PoP Location and IP Range data attached to this article in a CSV file. Please click Follow to automatically receive email notifications for updates to this article.
We recommend that you add the IP ranges owned by Cato Networks to the relevant ACL (see the following section) to allow traffic to the Cato Cloud. You can also choose to add IP ranges to specific PoP locations as detailed below IP Ranges per PoP Location.
Occasionally, specific IP addresses within the IP range are reserved and aren't available.
The PoP location IP ranges are within the following ranges that are owned by Cato Networks:
-
45.62.176.0/20
-
85.255.16.0/20
-
103.203.220.0/22
-
113.30.128.0/20
-
123.253.152.0/22
-
140.82.192.0/20
-
149.20.192.0/20
-
150.195.192.0/20
-
150.195.208.0/20
-
159.117.224.0/19
-
185.114.120.0/22
-
199.27.32.0/19
-
202.75.240.0/21
-
209.206.0.0/19
-
216.194.96.0/20
-
216.205.112.0/20
-
216.252.176.0/20
Cato uses these IP ranges for PoP locations in China:
-
43.250.146.128/27
-
58.254.183.224/27
-
59.36.210.32/27
-
101.36.65.64/26
-
103.61.189.0/27
-
103.61.191.0/27
-
103.197.0.32/27
-
103.203.220.0/24
-
111.206.82.0/26
-
114.94.9.0/26
-
114.94.55.192/26
-
119.147.8.0/26
-
140.207.250.192/26
-
202.75.242.0/24
-
203.131.253.208/29
-
211.95.135.128/26
This section lists the IP ranges for each PoP location in the Cato Cloud.
When Cato adds a new PoP location to the Cato Cloud or a new range to an existing PoP location, it will be listed as Coming soon. A comment will be added to this article for coming soon announcements and when the PoP location or range is in production.
|
PoP Location |
IP Range |
|---|---|
|
Auckland, NZ |
140.82.204.1 - 140.82.204.254 |
|
Bangkok, TH |
140.82.194.1 - 140.82.194.254 |
|
Beijing, CN |
101.36.65.71 - 101.36.65.127 103.197.0.32 - 103.197.0.63 111.206.82.4 - 111.206.82.54 |
|
Chennai, IN |
140.82.202.1 - 140.82.202.254 |
|
Ho Chi Minh City, VN |
140.82.198.1 - 140.82.198.254 |
|
Hong Kong, HK |
103.203.220.1 - 103.203.220.254 203.131.253.208 - 203.131.253.215 202.75.242.1 - 202.75.242.254 |
|
Jakarta, ID |
140.82.200.1 - 140.82.200.254 |
|
Kuala Lumpur, MY |
140.82.192.1 - 140.82.192.254 |
|
Manila, PH |
123.253.155.1 - 123.253.155.254 124.105.152.64 - 124.105.152.71 140.82.199.1 - 140.82.199.254 |
|
Melbourne, AU |
140.82.206.1 - 140.82.206.254 |
|
Mumbai, IN |
123.253.153.1 - 123.253.153.254 140.82.201.1 - 140.82.201.254 |
|
Osaka, JP |
140.82.207.1 - 140.82.207.254 150.195.210.1 - 150.195.210.254 150.195.211.1 - 150.195.211.254 150.195.212.1 - 150.195.212.254 202.75.243.1 - 202.75.243.254 |
|
Perth, AU |
140.82.196.1 - 140.82.196.254 |
|
Sapporo, JP |
Limited Availability (see this article for more information: FAQ - Limited Availability PoPs) |
|
Seoul, KR |
140.82.205.1 - 140.82.205.254 |
|
Shanghai, CN |
43.250.146.128 - 43.250.146.191 103.61.189.1 - 103.61.189.31 114.94.9.1 - 114.94.9.63 114.94.55.192 - 114.94.55.254 140.207.250.192 - 140.207.250.254 |
|
Shenzhen, CN |
58.254.183.224 - 58.254.183.254 59.36.210.32 - 59.36.210.63 103.61.191.1 - 103.61.191.31 119.147.8.1 - 119.147.8.63 211.95.135.128 - 211.95.135.191 |
|
Singapore, SG |
103.203.221.1 - 103.203.221.254 116.51.18.152 - 116.51.18.159 140.82.203.1 - 140.82.203.254 150.195.214.1 - 150.195.214.254 |
|
Sydney, AU |
140.82.195.1 - 140.82.195.254 202.75.244.1 - 202.75.244.254 (coming soon) |
|
Taipei, TW |
140.82.193.1 - 140.82.193.254 |
|
Tokyo, JP |
103.203.222.1 - 103.203.222.254 123.253.152.1 - 123.253.152.254 123.253.154.1 - 123.253.154.254 (coming soon) 150.195.208.1 - 150.195.208.254 150.195.209.1 - 150.195.209.254 150.195.218.1 - 150.195.218.254 150.195.219.1 - 150.195.219.254 150.195.222.1 - 150.195.222.254 - Tokyo_DC4 Limited Availability (see this article for more information: FAQ - Limited Availability PoPs) |
|
PoP Location |
IP Range |
|---|---|
|
Ashburn, VA |
45.62.176.1 - 45.62.176.254 45.62.184.1 - 45.62.184.254 45.62.185.1 - 45.62.185.254 149.20.197.1 - 149.20.197.254 149.20.199.1 - 149.20.199.254 150.195.205.1 - 150.195.205.254 150.195.206.1 - 150.195.206.254 216.194.103.1 - 216.194.103.254 |
|
Atlanta, GA |
45.62.188.1 - 45.62.188.254 149.20.196.1 - 149.20.196.254 216.205.113.1 – 216.205.113.254 |
|
Austin, TX |
150.195.199.1 - 150.195.199.254 |
|
Bogota, CO |
216.194.111.1 – 216.194.111.254 |
|
Boston, MA |
149.20.200.1 - 149.20.200.254 216.205.119.1 - 216.205.119.254 |
|
Calgary, CAN |
45.62.190.1 - 45.62.190.254 |
|
Charlotte, NC |
149.20.205.1 - 149.20.205.254 199.27.39.1 - 199.27.39.254 (coming soon) |
|
Chicago, IL |
45.62.178.1 - 45.62.178.254 149.20.202.1 – 149.20.202.254 150.195.204.1 - 150.195.204.254 216.194.104.1 – 216.194.104.254 216.205.127.1 - 216.205.127.254 |
|
Cincinnati, OH |
199.27.35.1 - 199.27.35.254 216.194.98.1 - 216.194.98.254 |
|
Dallas, TX |
45.62.179.1 - 45.62.179.254 149.20.195.1 - 149.20.195.254 216.194.105.1 - 216.194.105.254 216.205.125.1 - 216.205.125.254 |
|
Denver, CO |
45.62.182.1 - 45.62.182.254 150.195.203.1 - 150.195.203.254 |
|
Detroit, MI |
149.20.198.1 - 149.20.198.254 216.205.116.1 - 216.205.116.254 |
|
Honolulu, HI |
216.205.120.1 - 216.205.120.254 |
|
Houston, TX |
149.20.201.1 - 149.20.201.254 199.27.33.1 - 199.27.33.254 |
|
Kansas City, MO |
216.205.112.1 - 216.205.112.254 |
|
Las Vegas, NV |
149.20.194.1- 149.20.194.254 216.205.118.1 - 216.205.118.254 |
|
Lima, PER |
149.20.207.1 - 149.20.207.254 |
|
Los Angeles, CA |
45.62.177.1 - 45.62.177.254 149.20.203.1 - 149.20.203.254 150.195.201.1 - 150.195.201.254 199.27.32.1 - 199.27.32.254 216.194.106.1 - 216.194.106.254 216.205.115.1 - 216.205.115.254 |
|
Mexico City, MEX |
149.20.192.1 - 149.20.192.254 189.206.87.104 - 189.206.87.111 |
|
Miami, FL |
45.62.181.1 - 45.62.181.254 45.62.191.1 - 45.62.191.254 150.195.202.1 - 150.195.202.254 |
|
Minneapolis, MN |
216.194.97.1 - 216.194.97.254 216.205.117.1 - 216.205.117.254 |
|
Monterrey |
|
|
Montreal, CAN |
150.195.193.1 - 150.195.193.254 |
|
New York, NY |
45.62.183.1 - 45.62.183.254 45.62.186.1 - 45.62.186.254 149.20.204.1 - 149.20.204.254 150.195.207.1 - 150.195.207.254 216.205.126.1 - 216.205.126.254 |
|
Phoenix, AZ |
150.195.194.1 - 150.195.194.254 |
|
Portland, OR |
199.27.34.1 - 199.27.34.254 216.194.99.1 - 216.194.99.254 |
|
Quito, ECU |
216.194.100.1 – 215.194.100.254 |
|
Salt Lake City, UT |
150.195.198.1 - 150.195.198.254 |
|
San Jose, CR |
216.194.101.1 – 215.194.101.254 |
|
Santa Clara, CA |
45.62.187.1 - 45.62.187.254 216.194.108.1 – 216.194.108.254 |
|
Santiago, CHL |
149.20.193.1 - 149.20.193.254 |
|
São Paulo, BRA |
149.20.206.1 - 149.20.206.254 |
|
Seattle, WA |
45.62.180.1 - 45.62.180.254 199.27.38.1 - 199.27.38.254 (coming soon) 216.194.107.1 - 216.194.107.254 |
|
Toronto, CAN |
45.62.189.1 - 45.62.189.254 199.27.36.1 - 199.27.36.254 (Coming soon) |
|
Vancouver, CAN |
150.195.200.1 - 150.195.200.254 |
The following table lists IP ranges that you can use to configure a 3rd-party solution for geo-location settings for a country, even though there is no Cato PoP there. The Serviced Through column shows which PoP services the traffic. For example, you can use the range 216.194.96.16 - 216.194.96.31 for the localization of Colombia, and the traffic uses the Miami PoP.
|
IP Location |
IP Range |
Serviced Through |
|---|---|---|
|
Albania |
215.252.183.1 - 215.252.183.15 |
Milan |
|
Argentina |
150.195.196.1 - 150.195.196.254 |
Santiago |
|
Austria |
209.206.0.1 - 209.206.0.127 209.206.0.224 - 209.206.0.239 |
Munich |
|
The Bahamas |
45.62.191.48 - 45.62.191.63 216.194.96.1 - 216.194.96.15 |
Miami |
|
Belize |
216.194.96.64 - 216.194.96.79 |
Miami |
|
Benin |
85.255.21.209 - 85.255.21.222 |
Paris |
|
Bulgaria |
209.206.2.1 - 209.206.2.254 |
Prague |
|
Burkina Faso |
85.255.21.225 - 85.255.21.238 |
Paris |
|
Cameroon |
85.255.21.177 - 85.255.21.190 |
Paris |
|
Cayman Islands |
45.62.191.80 - 45.62.191.95 |
Miami |
|
Côte d'Ivoire |
85.255.21.193 - 85.255.21.206 |
Paris |
|
Croatia |
209.206.3.1 - 209.206.3.127 |
Prague |
|
Cyprus |
209.206.4.1 - 209.206.4.254 |
Milan |
|
Denmark |
209.206.17.128 - 209.206.17.254 |
Stockholm |
|
El Salvador |
216.194.96.112 - 216.194.96.127 |
Miami |
|
Gibraltar |
209.206.9.1 - 209.206.9.254 |
Madrid |
|
Greece |
209.206.10.1 - 209.206.10.254 |
Prague |
|
Guatemala |
216.194.96.128 - 216.194.96.143 |
Miami |
|
Haiti |
216.194.96.176 - 216.194.96.191 |
Miami |
|
Honduras |
216.194.96.96 - 216.194.96.111 |
Miami |
|
Hungary |
209.206.11.1 - 209.206.11.254 |
Bucharest |
|
Iceland |
209.206.12.129 - 209.206.12.250 |
Dublin |
|
Luxembourg |
209.206.16.1 - 209.206.16.191 |
Frankfurt |
|
Mali |
85.255.21.113 - 85.255.21.126 |
Paris |
|
Morocco |
209.206.30.1 - 209.206.30.254 |
Frankfurt |
|
Nicaragua |
216.194.96.80 - 216.194.96.95 |
Miami |
|
Niger |
85.255.21.81 - 85.255.21.94 |
Paris |
|
Nigeria |
85.255.21.145 - 85.255.21.158 |
Paris |
|
North Macedonia |
209.206.29.96 - 209.206.29.111 |
Frankfurt |
|
Norway |
209.206.17.1 - 209.206.17.127 |
Stockholm |
|
Panama |
216.194.96.48 - 216.194.96.63 |
Miami |
|
Paraguay |
150.195.192.1 - 150.195.192.15 |
Santiago |
|
Portugal |
209.206.19.1 - 209.206.19.254 |
Madrid |
|
Russia |
209.206.21.1 - 209.206.21.254 |
Stockholm |
|
Senegal |
85.255.21.241 - 85.255.21.254 |
Paris |
|
Serbia |
209.206.29.16 - 209.206.29.31 |
Frankfurt |
|
Slovakia |
209.206.22.1 - 209.206.22.254 |
Prague |
|
Slovenia |
209.206.3.128 - 209.206.3.254 |
Prague |
|
Tunisia |
85.255.21.1 - 85.255.21.14 |
Paris |
|
Turkey |
209.206.27.1 - 209.206.27.254 |
Bucharest |
|
Uruguay |
216.205.124.1 - 216.205.124.21 |
Sao Paulo |
|
Venezuela |
216.194.96.32 - 216.194.96.47 |
Miami |
|
(British) Virgin Islands |
45.62.191.32 - 45.62.191.47 |
Miami |
The file including the Cato public geo-location IP addresses is available to download in CSV format from this link.
66 comments
Added new range to PoP location in Tokyo, JP
Added new range to upgraded PoP location in Montreal, CAN
Updated the IP Locations in Geo-Localized IPs
Added Warsaw, PL as a new PoP Location for Europe, Middle East
Updated the IP ranges for these PoP locations: Shanghai, CN and Frankurt, DE
Updated the IP Locations in Geo-Localized IPs
Updated the IP ranges for these PoP locations: Beijing, CN and Osaka, JP
Added Salt Lake City, USA as a new PoP Location for Americas
Updated the IP ranges for these PoP locations: Ashburn, US and Dubai, UAE
Updated the IP ranges for these PoP locations: Frankfurt, and Paris
Can we depend upon the CSV file linked in the article to be always up to date and keep the same format so that it can be used programmatically, or is there another way (API?) to query for production PoP information?
JM Thanks for the comment! The CSV file and this article are always updated at the same time. In addition, we keep the same format for the CSV file.
Currently, it is not possible to use the Cato API to query for the production PoP information.
We are seeing users using a Vancouver POP, but I don't see one in this document. Could you let us know if we should be seeing this POP and if so, please update the documentation to account for that POP.
Nickolas Hopkins Thanks for your comment. We updated this article as follows:
Added new PoP location for Asia, Australia, Oceania: Chennai, IN
Added new PoP locations for Americas, Austin, TX and Vancouver, CAN
Added new IP ranges for: Los Angeles, CA and Shenzen, CN
Added new IP range for Osaka, JP
Added new Geo-Localized IP ranges for: Haiti, Paraguay, and Uruguay
Added new IP range for Frankfurt, DE
Added new IP ranges to these PoP locations: Singapore, Ashburn, Chicago, Denver, and Amsterdam
Added 150.195.192.0/20 to IP Ranges Owned by Cato Networks
Uploaded new version of CSV file that included bug fixes
Hi Is it possible to get a list of the actual PoP names to match the ranges as we need to test connections for some users that are travelling
Cato owned IP ranges does not list/include 150.195.192.0/20 (in addition to 150.195.208.0/20) which is used for Los Angeles POP among others. Please update Cato Owned IP Ranges to reflect 150.195.192.0/19 (150.195.192.0-150.195.223.255).
Carter Terry Thanks so much for your comment. 150.195.192.0/20 was removed by mistake, and I added it back.
Paul Harrison An excellent suggestion. We will look into making this enhancement for this article.
Added new IP range for New York, NY
The name of the POP in relation to how it is represented in the SDP client needs to be added to this list.
Paul Harrison and Odis Massey - thanks for the excellent suggestions! We will look into using them to improve this article.
Added Nairobi, KE as a new PoP Location for Europe, Middle East
Added a new IP range for Los Angeles, US
If I want to include all possibilities to a Conditional access rule, is the list under “IP Ranges Owned by Cato Networks” sufficient?
We are planning to do the same, also interested in getting confirmation on this. In addition, we would like to automate the management of the named locations for Cato - it would be convenient if the “ranges that are owned by Cato Networks” could be available as a downloadable file in a predefined format, inside Production_POP_Guide.csv or as a separate download.
Microsoft requires a simple list of one range per line. Having the file(s) in that format would be great. The file upload in the conditional policy is smart enough to just add any new entries. Bonus points if file(s) could be available as a FTP download to script our update.
I agree with the above comments. I already scrape http://geoipfeed.catonetworks.com/cato_ip2geo_feed.csv for information that gets loaded into our firewalls and conditional access policies for Microsoft, but I would much appreciate this list to be in JSON format with service identifiers that I can then use JMESPath to filter the data and manipulate the data.
Please sign in to leave a comment.