If you have ever tried to connect your Heroku app to a bank API, a payment gateway, or any third-party service that asks you to whitelist your IP address, you may have probably faced this problem before. Actually, Heroku doesn’t give your app a fixed IP by default. Every time your dyno restarts, redeploys, or scales, your outbound IP can change. So the IP you gave to your partner API may not be yours today.

Actually, this is one of those problems that looks very small in the start until one day your entire integration gets completely blocked. Let’s see why it happens and the easiest way to fix it.

Why Heroku Apps Don’t Have a Fixed IP by Default

Heroku runs on a dynamic multi-tenant infrastructure. Your app shares network resources with thousands of other apps, and dynos are constantly recycled for scaling and maintenance. That is exactly what makes Heroku so easy to work with. But it also means your outbound traffic comes from a pool of shared, rotating IPs rather than one you control.

Most of the time, this doesn’t matter. But it becomes a real problem the moment you need to:

• Connect to a banking or payment API that requires IP whitelisting
• Pull data from a service that blocks requests from unrecognized or shared IPs
• Meet a client or partner’s security requirement for a fixed origin IP
• Avoid getting rate-limited or flagged because you’re sharing an IP with apps you have nothing to do with

The last one catches people off guard. Since Heroku’s default IP is shared across many apps, if another app on the same IP gets flagged for abuse or spam, your traffic can get caught in the fallout too.

Already know this is your problem? Get your dedicated IP set up in under a minute →

What a Dedicated IP Actually Does

A dedicated IP add-on gives your Heroku app one or more static IP addresses that actually belong only to you. Which means no rotating addresses, no sharing, no surprises breaking your integrations.

With the Express Nodes Dedicated IP add-on, you actually get two static IPs at the price of one. You can run traffic through both or use one as your primary and keep the other one as a backup, so if something ever needs a failover, you have it covered without extra steps.

Here are a few things that you should know about:

Fresh, monitored IPs: These aren’t recycled addresses that ten other companies used before you. Express Nodes actively monitors its IP pool to keep them clean so you don’t get someone else’s bad reputation.

Works across protocols: Whether your stack needs HTTP, HTTPS, or SOCKS5, it’s supported. It actually matters a lot when you are working with tools or APIs that specifically require SOCKS5 rather than standard HTTP proxying.

No bandwidth problem: Depending on your plan, you can get unlimited bandwidth, so you can work without any worries.

Any language, any framework: Ruby, Python, Node.js, Java, PHP, Go — it doesn’t matter what you are running. The setup process is the same.

How to Set Up a Dedicated IP on Heroku

This is the part people expect to be complicated. It isn’t.

1. Open your terminal and make sure you’re logged into the Heroku CLI.
2. Run one command:

heroku addons: create dedicatedip

1. That’s it. No config files to upload, no manual restarts, no waiting around. Your app is assigned two dedicated IPs in under a minute.

Once it’s provisioned, you can actually go and check your assigned IPs directly from your Heroku dashboard or via the CLI, test the connection to make sure everything’s working properly, and start using it in your app’s outbound requests.

If you’re on Ruby, Python, or PHP, there are language-specific setup notes in the documentation to help you route your app’s traffic through the new IPs correctly, since the exact implementation varies slightly by framework.

That’s really the whole setup. Install the Express Nodes Dedicated IP add-on now → 

Choosing the Right Plan

Pricing scales with how much bandwidth and traffic your app actually needs, so there’s no reason to overpay if you’re running a small side project, and no reason to get stuck on a plan that throttles you if you’re running something serious.

• Standard works well for smaller apps just getting started with a dedicated IP.
• Pro and Scale suit apps with growing, steady traffic.
• MAX and Unlimited are built for apps that can’t afford to hit a bandwidth ceiling, ever.

All plans include two dedicated IPs, secure traffic, and a dedicated account manager, so you’re not losing features by starting small. You can always move up a tier later as your traffic grows.

Who Actually Needs This

Not every Heroku app needs a dedicated IP. If your app doesn’t talk to services that require whitelisting, you probably won’t notice the difference. But if any of this sounds familiar, it’s worth setting up:

• You’re integrating with a bank, payment processor, or financial API
• A partner or enterprise client has asked for your “fixed IP address”
• You’re scraping or pulling data from sources that block shared or unrecognized IPs
• You’ve been randomly rate-limited or blocked and can’t figure out why (a noisy neighbor on your shared IP is a common, invisible cause)

If your Heroku app needs a fixed IP for whitelisting, compliance, or just peace of mind, stop losing time to blocked integrations. Get your Express Nodes Dedicated IP today →