Basically, we have an integration with an external service that requires to whitelist the server IP.
I have tried to research about the topic around your documentation, but I haven’t found a way to get the IP Range List - all the answers that I found tell that you don’t share your IP List because they change very often.
What is the CIDR range assigned to Netlify, that they make available to their hosted clients?
How can I resolve the issue on Netlify?
I don’t have access to the third-party implementation that requires to whitelist the API. That means if you don’t have any option, I’ll have to create an external proxy in another host that offers an IP List or choose to host the solution in another provider, that’s is not ideal.
Hi, @evandro-peakonedev. We do not have a public list of IP addresses to share and if I did it would quickly become out of date.
The request you have here, which is for a list of guaranteed IP addresses that will be used for outbound connections to other resources, is a feature request often made. We are looking into providing this type of functionality but it is not possible at this time.
Would you be willing to share more details about how you connect to the external service? For example, which of these are you trying to accomplish (and the answer may be more than one or even all of these below)?
Are you?
wanting to proxy requests to an external service after the deployment is complete using known IP addresses for allow-list purposes
wanting to make requests to an external service from Functions using known IP addresses for allow-list purposes
wanting to make request to an external service during the site build and deploy process at Netlify using known IP addresses for allow-list purposes
Each of those three scenarios uses different sets of IP addresses and, in all three scenarios, the IP addressed used are subject to change at any time and are not known in advance of their being changed.
We we’ll add this topic to the feature request for tracking and follow-up here if it becomes available. However, it would help us to know which of the scenarios above applies to your site (which, again, could be all of them).