Telegram IP Ranges
Telegram runs its own network for its messaging service. Its servers answer from AS62041, registered with the RIPE NCC to Telegram Messenger Inc, and a small separate CDN network, AS44907, carries the rest.
- Provider
- Telegram
- Primary ASN
- AS62041
- Category
- Tech
- Headquarters
- Dubai, UAE
- Announced IPv4 prefixes
- 24
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS62041 (Telegram Telegram Messenger Inc). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
95.161.64.0/20
95.161.64.0/21
95.161.72.0/21
91.108.4.0/22
149.154.164.0/22
91.108.8.0/22
91.108.56.0/22
149.154.160.0/22
91.108.10.0/23
149.154.160.0/23
2001:67c:4e8::/48 (IPv6)
What does a Telegram IP mean in a privacy test?
A Telegram address is one of Telegram's own servers, so finding one in a lookup means you were connected to Telegram rather than that anything of yours was routed through it. The address a Telegram user shows the world is still the ISP or VPN address underneath: none of this space is ever handed out to people using the app.
Where Telegram publishes its IP ranges
Telegram publishes a complete list as a plain text file at core.telegram.org/resources/cidr.txt: one CIDR block per line, no header and no metadata. It is short. Nine IPv4 blocks - among them 91.108.4.0/22, 91.108.8.0/22, 91.108.56.0/22, 149.154.160.0/20 and 185.76.151.0/24 - and five IPv6 blocks including 2001:67c:4e8::/48 and 2a0a:f280::/32. A service used at that scale from a network this compact is unusual, and it is why an allowlist for Telegram is a handful of lines rather than a feed you have to poll.
The Bot API documentation narrows it further for the one case that needs it. Webhook deliveries come from 149.154.160.0/20 and 91.108.4.0/22; the page tells you to accept those POSTs on port 443, 80, 88 or 8443 and shows the iptables and ufw rules that restrict the port to them. It also carries the caveat that belongs with any hardcoded rule - Telegram says the range might change in future, so the published file is the thing to re-read rather than the rule you wrote once.
Why a Telegram address is never a user's address
Telegram's network is used by Telegram alone. Nothing on AS62041 is rented out, so unlike a cloud or hosting range there is no customer machine to confuse with the operator's own service: every address in that space is Telegram infrastructure answering a client. In a website's logs an address from these blocks is Telegram itself fetching something, most often a webhook delivery to a bot's endpoint or a link preview.
The corollary is what matters in a privacy test. Somebody using Telegram does not get a Telegram address; their traffic still leaves through their ISP or their VPN, and that is what a leak test reports. MTProto proxies, which people sometimes call Telegram proxies, are run by third parties on hosting they rent themselves, so a proxy address belongs to that host's network and will not appear in Telegram's published list at all.
Related tools
Frequently asked questions
What IP ranges does Telegram use?
Telegram publishes the complete list at core.telegram.org/resources/cidr.txt: nine IPv4 blocks, including 91.108.4.0/22, 91.108.56.0/22 and 149.154.160.0/20, and five IPv6 blocks. The addresses are announced under AS62041, registered with the RIPE NCC to Telegram Messenger Inc, with AS44907 carrying its CDN space.
Why does a Telegram IP appear in my privacy test?
A Telegram address is one of Telegram's own servers, so finding one in a lookup means you were connected to Telegram rather than that anything of yours was routed through it. The address a Telegram user shows the world is still the ISP or VPN address underneath: none of this space is ever handed out to people using the app.
Which addresses does Telegram send bot webhooks from?
Telegram's Bot API documentation names 149.154.160.0/20 and 91.108.4.0/22, and tells you to accept the incoming POST on port 443, 80, 88 or 8443. It also warns that the range might change, so a firewall rule built on those two blocks needs re-checking against the published file rather than being left alone.
Is a Telegram IP the same as my IP when I use Telegram?
No. That space carries Telegram's servers; your traffic to them leaves through your own ISP or VPN, and that is the address a leak test reports. Nothing in AS62041 is assigned to people using the app.
Is an MTProto proxy on Telegram's network?
Usually not. MTProto proxies are run by third parties on hosting they rent themselves, so the address belongs to that host's network and will not appear in Telegram's published CIDR list. Checking an address against that file is a way to tell one from the other.