Zerodha shared IP common IP NSE compliance surveillance family accounts

Zerodha IP address shared alert

From WebNotes, a public knowledge base. Last updated 20 June 2026. Reading time ~11 min.

Key facts

What triggers it	Multiple Zerodha accounts logging in from the same device or network, so they share a common public IP address
Why it exists	An NSE compliance mandate under which brokers capture and report users' IP addresses for security and surveillance
Common benign causes	A shared home or office wifi, family members trading on one connection, or several accounts behind one router
Is it an accusation	No. It is a clarification request, not a finding of wrongdoing; the broker must establish why the IP is common
What you must do	Respond with the reason the accounts share the IP, for example that they belong to one family on one home network
Why the rule matters	Common-IP patterns can signal one person operating many accounts or unauthorised access, which surveillance is built to catch

The Zerodha IP address shared alert is an email Zerodha sends when two or more Zerodha accounts log in from the same device or network and therefore share a single public IP address. Zerodha sends it because, under an NSE compliance rule, brokers capture and report client IP addresses for security and surveillance, and a common IP across accounts is something the broker has to explain to the exchange. The alert asks you to clarify why the accounts share the address; it is a question, not a verdict.

This alert unsettles people because the wording sounds like an accusation of misuse. It is not. A shared IP is one of the most ordinary things in retail trading: a household where a husband, wife and parent each hold a Zerodha account and all log in from the same home wifi will present one IP to the exchange. So will several colleagues trading from one office network. The rule does not forbid this; it requires the broker to know about it and to be able to tell innocent sharing apart from one person quietly operating many accounts.

This article explains what the alert means in plain terms, the NSE rule that drives it, why a common IP is a surveillance signal worth capturing, the everyday causes that set it off, what you actually have to do in response, and how this alert differs from the login-from-a-different-city alert it is often confused with.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

What the alert actually says

The trigger, in Zerodha’s own words, is that “multiple accounts accessed Zerodha from the same device or network, and Zerodha needs clarification as per regulatory requirements.” Your public IP address, the address your internet connection presents to the outside world, is shared by every device behind your router. When more than one Zerodha account logs in from behind that one router, those accounts all carry the same IP into the exchange’s records.

The exchange and the broker see a cluster of accounts on one IP and cannot tell, from the IP alone, whether that is a family, an office, or a single operator running multiple accounts. The alert resolves the ambiguity by asking you. Zerodha’s instruction is direct: “respond with clarification about the shared IP address usage” and “explain why multiple accounts accessed Zerodha from the same device or network.” The system needs a human-supplied reason attached to the common-IP pattern.

The NSE compliance rule behind it

Zerodha does not capture IP addresses by choice; it does so because the exchange mandates it. Under the referenced NSE rule, “brokers capture and report users’ IP addresses for security and compliance.” IP capture has become a standard part of the broker’s surveillance obligation: NSE circulars require trading members to store the IP, and in some cases the device details, from which orders are placed, modified and cancelled, so that activity can be traced to a source.

This sits inside the wider broker-surveillance framework that SEBI strengthened with its July 2024 circular on a brokers’ institutional mechanism for the prevention and detection of fraud or market abuse (SEBI/HO/MIRSD/MIRSD-PoD-1/P/CIR/2024/96, dated 4 July 2024), operationalised through NSE inspection and surveillance circulars. The broker is required to run surveillance, flag patterns, seek client clarification, and report back to the exchange. The shared-IP alert is one concrete instance of that loop: a pattern flagged, a clarification sought.

Why a common IP is a surveillance signal

A shared IP matters because some forms of market manipulation depend on one person controlling many accounts that appear independent. If a single operator runs ten accounts and trades among them to create artificial volume or to move a price, those accounts will often log in from one location and share an IP. The IP is the thread that ties supposedly separate clients back to a common controller.

The same pattern catches a different risk: unauthorised access. If your account is being logged into from a device that also logs into other people’s accounts, the shared IP can be the sign of a third party operating accounts that are not theirs. Capturing and querying the common IP lets the exchange separate the benign cases, families and offices, from the cases that warrant a closer look. None of this means a shared IP is itself an offence. It means the exchange wants the IP attached to a known, stated reason, so that the pattern is explained rather than anomalous. This is the same establish-the-genuineness logic that drives the reversal-trades clarification email .

The everyday causes

For an ordinary retail client, a shared-IP alert almost always traces to one of a few household or workplace situations:

Family accounts on one home network. The most common cause. Spouses, parents and adult children each holding a Zerodha account and trading from the same home wifi all share that connection’s public IP.
One office or shared workspace. Colleagues or co-located traders behind a single corporate connection present a common IP to the exchange.
Multiple accounts you operate yourself. A person who legitimately holds more than one account, for example an individual and a Hindu Undivided Family account, logging into both from the same device.
Shared or public networks. Logging in from a network that many people use, such as a hostel or co-working space, can briefly place your account on an IP others also use.

In each case the shared IP is real and innocent, and the correct response is simply to say so. The alert is not asking you to stop sharing a network; it is asking you to confirm what the shared network is.

What you must do

Respond to the clarification, and respond truthfully. Zerodha asks you to explain why multiple accounts accessed Zerodha from the same device or network, which you do by raising a support ticket and stating the reason: the accounts belong to family members on one home connection, or to an office, or to a single person operating both. For a family case, naming the relationship is usually enough.

Do not ignore the email. The risk in a surveillance clarification is rarely the underlying pattern; it is silence. Across Zerodha’s surveillance alerts, an unanswered clarification can lead the broker to restrict the account pending a reply, because the broker must report the outcome to the exchange and cannot report “no response” indefinitely. The cost of answering is a few sentences; the cost of ignoring can be a blocked account. Treat the shared-IP email the same way you would treat the trade-clarity email : a routine question that becomes a problem only if left unanswered.

How it differs from the different-city alert

These two alerts are easy to mix up because both involve IP addresses, but they ask opposite questions.

	Different-city alert	Shared-IP alert
About	One account	Multiple accounts
Trigger	Your account logs in from a new IP location	Several accounts log in from the same IP
Question it asks	Is this login you?	Why do these accounts share an address?
Usual benign cause	Travel, VPN, network switch	Family or office on one connection
Your response	Verify the IP is yours, or secure the account	State the reason the accounts share the IP

The different-city alert is a personal-security signal about one account moving. The shared-IP alert is a surveillance signal about a relationship between accounts. Reading the alert carefully tells you which one you have and therefore which response applies.

What can go wrong

Reading the alert as an accusation. It is a clarification request driven by an NSE reporting rule, not a finding of misuse. A genuine explanation resolves it.
Ignoring the email. Unanswered surveillance clarifications can lead to the account being restricted until you reply. Respond promptly with the real reason.
Giving a vague or false reason. State the actual cause, family on one wifi, an office connection, two of your own accounts. A misleading clarification defeats the purpose and can compound the problem.
Confusing it with the different-city alert. That alert is about one account at a new IP and is a security check; this one is about several accounts at one IP and is a surveillance check. The responses differ.
Assuming a shared IP is forbidden. It is not. Households and offices routinely share an IP. The rule only requires the pattern to be explained, not eliminated.

External references

References

Zerodha support, Why did I receive an email saying my IP address is shared with other devices? (as of 21 June 2026).
NSE requirement that trading members capture and report client IP and device details for orders placed, modified and cancelled (referenced in Zerodha support documentation).
SEBI circular SEBI/HO/MIRSD/MIRSD-PoD-1/P/CIR/2024/96, Measures to instil confidence in securities market: Brokers’ institutional mechanism for prevention and detection of fraud or market abuse, dated 4 July 2024.

Frequently asked questions

Why did Zerodha email me that my IP address is shared with other devices or clients?

Because two or more Zerodha accounts logged in from the same device or network, so they share one public IP address. Under an NSE compliance rule, brokers capture and report client IP addresses, and Zerodha must ask why the IP is common.

Does the shared-IP alert mean I have done something wrong?

No. It is a clarification request, not an accusation. A shared IP is common and usually innocent, such as a family on one home wifi. Zerodha simply has to record and report the reason the accounts share an address, as the rule requires.

My family trades from the same home wifi. Is that why I got the alert?

Yes, that is the most common cause. Several accounts on one router all present the same public IP to the exchange. Respond to Zerodha explaining that the accounts belong to family members trading from a shared home connection.

What exactly do I need to do when I get the alert?

Reply with a clarification of why multiple accounts accessed Zerodha from the same device or network. Usually a short explanation that the accounts are family or household members on one shared connection is enough. Raise it through a support ticket.

Why does the exchange care about a shared IP address?

A common IP across many accounts can indicate one person operating multiple accounts, or unauthorised access to someone else’s account, both of which surveillance is designed to detect. Capturing the IP lets the exchange tell genuine sharing from manipulation.

Could a shared IP get my account blocked?

Not for sharing an IP by itself, if you respond with a genuine explanation. The risk arises from not responding to a clarification request, since unanswered surveillance queries can lead the broker to restrict the account pending an answer.

Is this the same as the login-from-different-city alert?

No. The different-city alert is about one account logging in from a new IP location. The shared-IP alert is about several accounts logging in from the same IP. One is a location-change signal; the other is a common-address signal.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed: 20 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.