Telegram Messenger Inc
Data as of 2026-08-30
BGP inherited
This organisation
| Netblocks | 92 · 32,529 IPv4 addresses |
| IPv6 | 28 prefixes (largest 2a0a:f280::/29) |
| Registered in | AG (51) · Germany (12) · Netherlands (4) · Singapore (4) · VG (4) |
| Also registered under this name | 113 netblocks across 2 separate records |
| Record ID | 232142238 |
| Registry | BGP |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 24 shared RIR contact/maintainer handles |
| Registry names | 9 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
10 weekly snapshots · JSON
107
-6 netblocks since 2026-07-05
2026-07-05
peak 113
2026-08-30
IP Ranges (92)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 27.111.229.210/32 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 27.111.230.113/32 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 80.81.193.148/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 80.81.196.155/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 80.81.196.179/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 80.81.196.184/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 80.249.209.69/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 80.249.214.57/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 80.249.214.80/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 80.249.214.239/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 91.105.192.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.4.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.4.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.6.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.8.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.8.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.10.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.12.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.16.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.16.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.18.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.20.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.20.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.56.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.56.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.56.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 91.108.57.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 95.161.64.0/21 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 95.161.64.0/20 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 95.161.72.0/21 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 103.16.102.92/32 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 103.16.102.233/32 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 109.239.136.22/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 149.154.160.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.160.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.160.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.161.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.162.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.162.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.163.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.164.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.164.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.164.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.165.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.166.0/23 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.166.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.167.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.168.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 149.154.172.0/22 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 178.18.225.141/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 178.18.226.168/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 178.18.227.6/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 178.18.227.113/32 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 185.76.151.0/24 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 2001:67c:4e8::/48 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 2001:7f8::f259:0:1/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::f259:0:2/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::f259:0:3/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::f259:0:4/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a506:2041:1/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a506:2041:2/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a506:2041:3/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a506:2041:4/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:b28:3ff::f259:2/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2001:b28:f23c::/48 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 2001:b28:f23d::/48 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 2001:b28:f23f::/48 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 2001:de8:4::6:2014:1/128 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:4::6:2014:2/128 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:12:100::92/128 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:12:100::233/128 | Telegram Messenger APAC | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::225:141/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::226:168/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::227:6/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::227:113/128 | Telegram Messenger EUR | PEERINGDB | ASSIGNED | ● high |
| 2a0a:f280:203::/48 | Telegram Messenger Inc | BGP | ANNOUNCED | ● high |
| 5.28.192.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 5.28.200.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 5.28.208.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 5.28.216.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 5.28.224.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 5.28.232.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 5.28.240.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 5.28.248.0/21 | TELEGRAM-MESSENGER-INFRA-NET | RIPE | ASSIGNED PA | ● low |
| 91.108.36.0/23 | Telegram_CDN | RIPE | ASSIGNED PA | ● low |
| 91.108.38.0/23 | Telegram_CDN | RIPE | ASSIGNED PA | ● low |
| 2001:b28:f23b::/48 | Telegram_Messenger | RIPE | ASSIGNED | ● low |
| 2001:b28:f23e::/48 | Telegram_Messenger_LLP | RIPE | ASSIGNED | ● low |
| 2001:b28:f240::/48 | Telegram_Messenger | RIPE | ASSIGNED | ● low |
| 2001:b28:f241::/48 | Telegram_Messenger | RIPE | ASSIGNED | ● low |
| 2001:b28:f242::/48 | Telegram_CDN | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:f280::/29 | Telegram Messenger Inc | RIPE | ALLOCATED-BY-RIR | ● low |
IPv6 ranges (28)
showing the 15 largest allocationsDomains hosted in this network
what's this?Network trust
what's this?
RPKI hygiene: B
how networks compare →
93.5%
of checked blocks have valid RPKI ROA coverage
(100 of 107)
Possible discrepancies (13)
These blocks are registered to Telegram Messenger Inc but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2001:b28:f23e::/48 /48 | authorized for AS31500 — Global Network Management Inc |
| 2001:b28:f240::/48 /48 | authorized for AS31500 — Global Network Management Inc |
| 2001:b28:f241::/48 /48 | authorized for AS31500 — Global Network Management Inc |
| 2001:b28:f23b::/48 /48 | authorized for AS31500 — Global Network Management Inc |
| 2001:b28:f242::/48 /48 | authorized for AS31500 — Global Network Management Inc |
| 5.28.192.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
| 5.28.200.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
| 5.28.208.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
| 5.28.216.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
| 5.28.224.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
| 5.28.232.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
| 5.28.240.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
| 5.28.248.0/21 /21 | authorized for AS1273 — Vodafone Group PLC |
NIC Handles
AS211157
AS44907
AS59930
AS62014
AS62014
AS62041
AS62041
DUMY-RIPE
DUMY-RIPE
ETELECOM-MNT
ETELECOM-MNT
IPFFM
+12 more