A static IP address is a fixed internet address that stays the same every time a machine connects. In algo trading it matters for one reason: brokers require the API traffic that places your orders to arrive from an address they already know, and a changing address gets rejected.
That single requirement catches out more first-time algo traders than any other part of the setup, because nothing warns you about it. Your broker connects. Your test order goes through. Everything reads as working — right up until the morning it does not.
This guide covers what a static IP actually is, why broker APIs are built around it, what happens to a live strategy without one, what the whole thing costs in India, and how to get it right the first time.
What a static IP actually is
Every device on the internet has an IP address — a number that tells other machines where to send a reply. Most of them are dynamic: your provider hands you an address from a shared pool, and you get a different one when the router restarts, the lease expires, or you move between networks.
A static IP is the opposite. It is reserved for one account and does not rotate. The address you have today is the address you will have next month, and the month after that.
| Dynamic IP | Static IP | |
|---|---|---|
| Changes over time | Yes, without warning | No |
| Assigned to | A shared pool | One account |
| Survives a reconnect | Usually not | Yes |
| Usable for API whitelisting | No | Yes |
| Typical use | Home and mobile browsing | Servers, APIs, trading |
| Cost | Included in a normal plan | A paid add-on, or bundled |
For browsing, streaming and everyday use, a dynamic address is completely fine and you will never notice it. The distinction only becomes load-bearing the moment another system has to recognise you by address.
Why brokers insist on one
A broker API can move real money. The broker's security model therefore does not rely on your API key alone — it also checks where the request came from. An address you registered in advance is a second factor that a stolen key cannot provide on its own.
What the requirement buys the broker
Three things follow from that:
- A stolen key is less useful. An attacker with your credentials still has to send the request from your registered address, which they do not control.
- Traffic is attributable. If orders ever need to be investigated — by the broker, by you, or by a regulator — there is a clean record of where they originated.
- Abuse is rate-limitable. Per-address limits only work when the address is stable. Without that, one bad actor rotating through a pool is indistinguishable from ordinary traffic.
The reason that is becoming more important
There is a fourth reason that matters more as retail algo trading grows: regulators increasingly expect automated order flow to be traceable to a specific, identifiable origin. A fixed address is the simplest mechanism that provides that.
What breaks without a static IP
The failure is not a clean error at setup time. That is precisely what makes it expensive — everything looks correct until the moment it matters.
How it actually goes wrong
A realistic sequence:
- You connect your broker from a home connection and whitelist whatever address you had that day.
- Setup succeeds. A test order goes through. Everything reads as working.
- You backtest, paper trade, and eventually deploy live. Still fine.
- Overnight your provider rotates the address. Nothing notifies you.
- Next morning your strategy's entry condition fires and the order is sent.
- The broker rejects it — the request came from an address it does not recognise.
- Your strategy is now half-positioned, or not positioned at all, and you find out when you next look at the screen.
Why it is hard to diagnose
The second-order problem is diagnosis. A rejected order from an unregistered address usually comes back as an authorisation or credentials error, which sends people off regenerating API keys that were never the problem. Hours get lost to the wrong fix.
What a static IP costs in India
Bought separately, a static IP is a recurring line item, and the cost shows up in one of two shapes.
Route one: your internet provider
Through your ISP. Most Indian providers will sell a static address, but generally only on a business connection. You are therefore paying the difference between a consumer and a business tariff, plus the address itself. Provisioning takes days and sometimes a site visit.
Route two: a cloud server
Through a cloud provider. Rent a small instance in a Mumbai region and attach a reserved address. The address is stable and the latency to the exchanges is good. You are billed monthly for both the instance and the reserved address.
Route three: bundled with the platform
On Arthalab a dedicated IP is included with the plan at no separate charge. It is allocated from a managed pool, and the allocation takes a few minutes. There is no add-on to buy and no server for you to maintain.
Paper trading does not need an IP at all. Simulated orders never reach a broker, so there is nothing to whitelist — which makes paper mode the fastest way to see a strategy run before any of this applies. Paper trading versus live trading covers what else differs.
Setting it up properly
1
Get a dedicated address
From your ISP, a cloud provider, or your trading platform. It has to be genuinely reserved for you, not merely stable-looking today.
2
Create your broker's API app
Done in the broker's developer portal, not the trading app. You receive a key and a secret.
3
Whitelist the address
Paste it into the API app's allowed-IP field, exactly as shown. A single wrong digit fails identically to no entry at all.
4
Complete the daily broker login
Separate from the IP, and required before anything can be tested.
5
Validate with a real test order
IP validation places a tiny order and reverses it, exercising the whole path before a live signal depends on it.
6
Record where to check it
When orders fail months from now, you want to know in thirty seconds where the current address is displayed.
Mistakes that look like solutions
Three workarounds come up constantly. None of them hold up, and it is worth knowing why before you spend a weekend on one.
| Workaround | Why it fails |
|---|---|
| A consumer VPN | Most route you through shared exit nodes that rotate. You have swapped one changing address for another and added a hop of latency |
| Dynamic DNS | Keeps a hostname pointing at a changing address. Broker whitelists take an address, not a hostname, so it solves nothing here |
| Re-whitelisting manually each morning | Works right up until the address rotates at 9:10 on an expiry day |
| Assuming your IP is static because it has not changed | Dynamic addresses can hold steady for weeks. Stability is not the same as a reservation |
That last row deserves emphasis. The most common version of this mistake is checking your public IP twice, seeing the same number, and concluding it is static. Static and dynamic addresses explains how to actually tell them apart.
Checklist before you go live
- You have a dedicated IP that is genuinely reserved for your account
- That exact address is whitelisted in your broker's API settings
- You have run a validation order and seen it accepted
- You know which screen shows your current address
- Your broker login for the day is done
- You have tested what happens when a leg is rejected mid-strategy
The broker login catches people out more often than the IP does. Most Indian brokers expire the API session daily, so a fresh login is needed every trading morning regardless of how your IP is set up. The two problems produce similar symptoms and have completely different fixes.
What it looks like when it is working
Worth stating, because the absence of problems is hard to recognise. A correctly configured address produces no events at all. There is no notification, no status change, nothing to check.
That silence is why people stop thinking about it, and why a rotation months later is so disorienting. The thing to internalise is where to look when orders start failing, not to monitor something that never changes.
- You know which screen displays your current address
- You know which broker setting holds the whitelist entry
- You know how to re-run validation
- You know the difference between an IP error and a session error
Four facts, learned once. That is the entire ongoing cost of this part of the setup.
Where this fits in the bigger picture
A static IP is infrastructure, not strategy. It decides whether your orders arrive, not whether they are any good. It is worth getting right precisely because it is boring: nobody ever improved their returns by having a better IP, but plenty of people have lost a day's trading to not having one.
If you are still deciding what to run, start with backtesting and paper trading — neither needs an IP, a broker or any capital — and sort the plumbing out when you are ready to put money behind it.
Frequently asked questions
It is an internet address that is reserved for you and does not change. A dynamic IP is handed out from a shared pool and rotates; a static one stays the same, which is what lets a broker recognise your traffic.
Because an API key alone is not enough security for something that can place real orders. Checking that the request came from an address you registered in advance means a stolen key is far less useful on its own. It also makes automated order flow traceable, which regulators increasingly expect.
Not for live trading through a broker API. You can build strategies, backtest them and run them in paper mode without one, because none of those send an order to a broker.
No. Paper orders are simulated and never reach a broker, so there is nothing to whitelist.
No, and a VPN is usually the wrong tool here. Most VPN services route you through shared exit addresses that change, which is the exact problem a static IP solves. Only a dedicated-IP VPN plan would work, and that is a specific paid product.
Bought on its own it is a recurring monthly cost, either as a business broadband upgrade or a reserved cloud address plus the instance it attaches to. On Arthalab it is included with the plan rather than billed separately.
Orders from the new address get rejected by the broker. The strategy keeps trying and keeps failing until the new address is whitelisted. On a multi-leg strategy this can leave you holding an unbalanced position.
Read the broker's error text. An expired session usually names the session or login explicitly, while an unregistered address usually reads as unauthorised or forbidden. If it is ambiguous, check the token first — it expires daily, so it is the likelier of the two.
Start with a free 3-day trial
Build a strategy, backtest it and run it on paper — no broker, no IP and no money needed to try it.
