New static IP feature

Help
1

I had a query about a recently release feature (https://vercel.com/changelog/static-ips-are-now-available-for-more-secure-connectivity). The thing is that we have a github organization and we want to enable github IP allowlisting so that users and service from a allowed set of IPs are able to access the org (Managing allowed IP addresses for your organization - GitHub Enterprise Cloud Docs). This is for security purpose. Earlier when we enabled the allowlisting , all of our vercel builds were failing which I assume was due to the fact that vercel build servers were not able to fetch the code from github, we have a next js setup with prismic integration (https://vercel.com/guides/how-to-integrate-nextjs-with-prismic). We are on vercel pro plan, and I want to know that if we opt for the newly static IP feature, will we be able to that to solve our problem we faced?

4

Yes, enabling Static IPs on your Vercel Pro plan should solve the GitHub IP allowlisting issue.

Once you turn on Static IPs, all outbound requests from your Vercel deployments (including build-time requests to GitHub and Prismic) will come from a consistent set of static IP addresses. You can then add these IPs to your GitHub organization’s allowlist, which should resolve the build failures you’ve been seeing.

Here’s what to do:

  1. Enable Static IPs for your Vercel project from your dashboard
  2. Copy the static IP addresses assigned to your project
  3. Add those IPs to your GitHub organization’s allowlist in your security settings
  4. Add them to any other services that require IP allowlisting (like Prismic, if applicable)

There’s no expected transition period. Once Static IPs are enabled, all new builds will immediately start using them. So you can safely enable allowlisting in your services right after turning it on.

Let us know if you have any more questions!