How Telegram voice calls can leak your IP address

You can call someone on Telegram and hand them your IP address in the same breath, without ever realizing you did it. There’s no scam link involved and no malware. It’s just an ordinary voice or video call. Because of the way Telegram connects a call, the person on the other end can often see the IP your phone is using, and that quietly tells them roughly where you are and who your internet provider is.

It’s one of the most overlooked privacy leaks on the platform, and the surprising part is how easy it is to close. One setting, that most people have never opened, decides whether it happens at all. I run managed Telegram hosting on dedicated hardware in Singapore, so keeping accounts on a clean, stable IP is the whole job, and this particular leak is one I watch closely. Here’s how it works, what it exposes, and exactly what to change.

How a Telegram call connects

When you place a voice or video call, Telegram tries, whenever it can, to connect the two devices directly to each other, phone to phone, instead of routing everything through a server in the middle. A direct connection is the fastest and clearest option, with the lowest latency and the best audio, which is exactly why messaging apps reach for it.

But direct means literally direct. Your phone opens a path straight to the other phone, and to do that, each device has to know the other one’s IP address. That isn’t a bug or an oversight. It’s simply what a peer-to-peer connection requires. The two ends can’t reach each other without knowing where the other one is.

The leak, stated plainly

So here’s the whole problem in one sentence: in a direct call, the other person’s device learns your IP, and yours learns theirs. Nobody hacked anything. The connection can’t exist without both ends knowing where to reach each other.

That means anyone you call, and anyone whose call you answer, can capture the IP your phone is on at that moment, just by being on the other end of a normal conversation. The call doesn’t have to be suspicious. A friendly chat is enough to exchange it.

What an IP address actually reveals

An IP address isn’t your street address, and it won’t spell out your name. But it gives away more than most people assume:

• Your rough location, often down to your city or region.
• Your internet provider or your mobile carrier.
• Whether you’re on home broadband, office wifi, or a mobile connection.
• A stable handle that can be watched over time or used to aim something more targeted at you.

Unlike a password, which you can change in seconds, the location and provider an IP points to are hard to take back once someone has written them down. It’s a great deal more than you’d knowingly hand a stranger who called you out of the blue.

And think about who’s actually on the other end of your calls. It isn’t always someone you fully trust. It might be a person you met in a group and barely know, a new contact who turns out not to be who they said, or a business contact you deal with but would never hand your home address. On the wrong setting, the IP is exchanged before either of you says a word.

The fix: the peer-to-peer setting

Here’s the good news. This is genuinely one setting.

Open Telegram, go to Settings, then Privacy and Security, then Calls, and find the option labeled Peer-to-Peer. It usually offers three choices: everybody, my contacts, or nobody. That setting decides when Telegram is allowed to make a call direct, phone to phone, versus when it has to route the call through its own servers instead.

Set it to nobody, and every call, incoming and outgoing, gets relayed through Telegram in the middle. The other party never sees your IP at all, because Telegram’s server sits between you. The exact wording shifts a little between the phone apps and the desktop app, but it lives in the same place, under calls, and it means the same thing everywhere.

Check what yours is set to right now, because a lot of accounts sit on everybody, or on my contacts, without the owner ever having chosen it.

Why “my contacts” isn’t enough

“My contacts” sounds safe, but it isn’t the private option. It still allows a direct connection, and therefore an IP exchange, with anyone in your contact list. And a contact can be someone you added loosely, a long time ago, for a single reason you’ve since forgotten.

If the goal is to not leak your IP on calls, nobody is the setting that actually delivers that. Anything else leaves a door open.

The honest trade-off

There’s always a trade-off, so here it is. When you force calls to relay through Telegram’s servers instead of going direct, you add a little latency, and the audio may be a touch less crisp on a shaky connection, because the sound now takes a slightly longer road.

The calls themselves stay encrypted, so the relay is carrying protected traffic, not listening in. For the overwhelming majority of people, a marginally longer path is a trivial price for not broadcasting your IP to whoever happens to call. Direct connections buy you call quality. They never buy you privacy.

Why a proxy inside Telegram doesn’t save you

This is the part that catches technical people out. Setting an MTProto or SOCKS5 proxy inside Telegram does not hide your IP on a peer-to-peer call.

The in-app proxy carries the Telegram protocol itself, your messages, your login, your chats. But the media of a direct call takes its own path, straight between the two devices, and that path exposes the real connection your phone is using. So someone who has carefully configured a proxy in the app, and assumes every last thing they do is covered, is still leaking their true IP the moment they take a direct call. The proxy setting and the peer-to-peer setting are two different switches, and only one of them governs calls.

Which IP a call exposes

That raises the deeper question: which IP does a call actually expose? The answer is simply whatever connection your device really uses to reach the internet at that moment.

• On your home wifi, a direct call shows your home IP.
• On a device-wide VPN, it shows the VPN’s IP.
• On a handset whose entire connection egresses through a mobile carrier, it shows that mobile IP.

The setting decides whether an IP leaks at all. But if one does leak, the real network path underneath your account decides which IP it is. Both of those are worth controlling, especially if the underlying connection is tied to your personal identity.

Don’t treat this as a voice-only concern, either. Video calls connect the same way, and so does screen sharing built on top of a call. The same peer-to-peer setting governs all of them, so changing it once covers the lot. Video is worth an extra thought, because it feels more personal and people reach for it with looser contacts, which is exactly when a leak bites hardest.

What to actually do

• Open the peer-to-peer setting today, on every account where your location or IP matters, and set it to nobody.
• Accept that relayed calls are the private choice, and that a hair of extra latency is the whole cost.
• Don’t assume a proxy configured in the app covers your calls, because it doesn’t.
• Remember the IP a leaking call would expose is whatever your device genuinely egresses through, so control that connection too.
• Be a little deliberate about answering calls from people you don’t know, at least until you’ve checked the setting.

A quick note on scope: this is about protecting your own IP and rough location from people you never chose to share them with, an ordinary user, a business, an operator running accounts that need to stay private. The relay option isn’t a loophole. It’s a normal privacy control that exists so a regular person can’t be quietly deanonymized by the simple act of taking a phone call.

The part that keeps mattering

Flipping the setting to nobody is one tap, and you should do it the moment you finish reading. But the deeper half, making sure the IP your account actually lives on and egresses through is a clean, stable one that isn’t tied to your personal identity, and keeping it that way over time, is quiet, ongoing work. It’s easy to set once and let drift.

That’s the part managed hosting is built to carry. telegramvault.org runs managed Telegram hosting on dedicated Singapore hardware, real handsets on real carrier SIMs from SingTel, M1, StarHub, and Vivifi. Your account lives on a stable, clean mobile IP, so even if a call ever did connect direct, the IP it exposed would be that neutral hosting connection, not your home line with your name on the bill. The private setting and the clean connection underneath it, the two halves of not leaking on a call, are simply handled. Onboarding starts with a real conversation about your setup, not a checkout page, and the code TGYT gets you a discount when you start.

Get new guides and videos first — join the Telegram channel.