What Telegram Knows About Your Device And Network

People land on this question after seeing an unfamiliar city in their Telegram active sessions list and assuming the worst. Before you panic or start terminating every session in sight, it’s worth understanding what that screen is actually built from. We run managed Telegram hosting and proxy setups for a living, so we spend a lot of time explaining to clients why their own bot server shows up as a “device” in a country they’ve never visited. Here’s what’s really going on.

In Telegram, go to Settings, then Devices. That list is the closest thing to a login history the app gives you. Each row is one active session: one authorized client instance connected to your account. Desktop, mobile, web, a userbot script running on a VPS, each of these gets its own row because each one holds its own authorization key issued when it logged in.

This is not a log of every action you’ve taken. It’s a list of currently valid sessions, plus a “last active” timestamp for each. If a session hasn’t been terminated, it stays on the list indefinitely, even if you haven’t opened that particular client in months.

What each field actually comes from

Four things show up per session: app name and version, device name, IP address, and an approximate location. They don’t all carry the same weight, and conflating them is where most of the confusion starts.

App name, version, and device name are self-reported. When a client authenticates, it sends a string describing itself, and Telegram displays that string back to you. This is why you can rename a session’s device label in some clients, or why a script using the Telegram API can identify itself as basically anything. If you’re auditing your own account, don’t treat the device name as proof of what hardware is connected. Treat it as a label the client chose to send.

The IP address is real. It’s the address of the TCP connection that authenticated the session, seen at the server. This one isn’t spoofable in the way the device name is, because it’s tied to the actual network path the connection took.

Location is derived from that IP address through a geolocation lookup, and this is the part that trips people up. It’s a city-level estimate based on which network block the IP belongs to, not a GPS fix and not tied to any location permission you’ve granted the app. IP geolocation databases attribute an address to wherever the owning ISP or hosting provider has registered that block, which can be off by a city, a region, or occasionally a country, especially for mobile carrier IPs and hosting provider ranges.

Why your own server shows up as a stranger

This is the case we deal with most often. If you’re running a Telegram bot or userbot on a VPS as part of a hosting setup, that session’s IP belongs to the datacenter, not to you. Geolocation databases will report whatever city the hosting provider’s IP block is registered to, which is frequently not the city the physical server sits in and almost never the city you’re sitting in while you manage it. A session showing up in Frankfurt or a US datacenter hub when you’ve never been there usually just means that’s where your hosting provider’s IP range is registered, not that someone else is in your account.

The fix here isn’t panic, it’s memory: know which sessions correspond to which of your own deployments before you start reviewing the list, so an unfamiliar-looking entry doesn’t send you terminating sessions you actually need.

What changes when you use a proxy

If you connect Telegram through a proxy, whether that’s a SOCKS5 proxy or an MTProto proxy, the IP that reaches Telegram’s servers is the proxy’s exit IP, not your ISP-assigned address. That’s not a side effect, it’s the entire mechanism: a proxy sits between your client and Telegram’s servers and relays traffic, so from the server’s point of view, the connection originated at the proxy.

People use proxies with Telegram for a few concrete reasons: to get a stable connection when their ISP throttles or blocks Telegram’s own IP ranges, to reduce connection latency to a specific data center, or to keep multiple accounts routed through separate, consistent network paths for operational reasons. Whatever the reason, the practical consequence for your login history is the same. Your active sessions list will show the proxy’s location, and if you switch proxies or your proxy’s exit node changes, you’ll see a session’s location shift even though nothing about the device itself changed. This is expected behavior, not a sign of compromise, as long as you know which proxy you configured for which session.

MTProto proxies specifically are also visible to Telegram at the protocol layer in a way generic SOCKS5 proxies aren’t, since MTProto proxy support is built into the client and negotiated as part of the connection. Functionally, though, the result for your session list is the same: an IP and a location that belong to the proxy, not to your home or office connection.

What the terminate button actually does

Terminating a session revokes that session’s authorization key. The next time that client tries to connect, it has to log in again, which means entering the phone number, the login code, and the two-step verification password if one is set. That’s the whole mechanism.

What it doesn’t do is retroactively touch message history. Cloud chats in Telegram are stored server-side and synced across every authorized device, so messages already sent or received from a now-terminated session remain part of your account’s message history everywhere else. The exception is secret chats, which are end-to-end encrypted and tied to the specific device pair that created them; those don’t sync to other devices and aren’t stored server-side in the same way. If you’re reviewing sessions because you’re worried about exposure, know that terminating a session cuts off future access from that client, it doesn’t erase what already happened while it was connected.

There’s also a single “terminate all other sessions” action, which revokes every session except the one you’re currently using. It’s the blunt-instrument option, useful if you’re not sure which specific session is the problem and would rather start clean.

Scanning a Telegram QR code from another device (typically to log into Telegram Web or Desktop) creates a brand new session bound to whichever device confirmed the scan. It’ll show up in your active sessions list like any other login, with its own app label, IP, and location. If you ever see a session you don’t recognize appear right after you scanned a QR code, work backward from that: did you actually initiate a QR login recently, and on what device? A QR-based session with an unfamiliar location and no corresponding action from you is the one scenario on this list actually worth taking seriously.

What this screen doesn’t tell you

It’s worth being precise about the limits here too. The active sessions list doesn’t show carrier information, doesn’t expose GPS-level positioning, and doesn’t track in-app behavior beyond the fact that a session exists and when it was last active. Bots you interact with see your user ID and username (and whatever profile info you’ve made public), not your IP or device list. Live location sharing in a chat is a separate, explicit feature you opt into per conversation, unrelated to what shows up on the Devices screen.

Practical habits

Check the Devices screen periodically, not just when something feels off. Keep a mental (or written) map of which sessions correspond to your own infrastructure, proxy configurations, and devices, so an unfamiliar entry is actually informative rather than just alarming. Pair session review with two-step verification, since a cloud password is what stops a new login even if someone has your phone number’s SMS code. And when a session’s location doesn’t match anything you set up, terminate it and change your two-step password rather than guessing.

If you’re running Telegram bots, userbots, or multiple accounts across proxies and want the network side of that set up correctly from the start, that’s what we do at telegramvault.org.

Take a look at what we offer on the home page.

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

The devices screen is your login history