Autonomous system
AS59930 TELEGRAM_MESSENGER
Hosting ARIN
Summary
Telegram Messenger
messaging cloud content infrastructure
TELEGRAM_MESSENGER is operated by Telegram Messenger Inc.
What it's used for
- The address space carries Telegram's cloud-based messaging infrastructure, identified by the netname
Telegram_Messenger_Networkon both announced IPv4 blocks. - The AS announces 2048 IPv4 addresses across 2 prefixes and 1 IPv6 prefix, while maintaining 38 observed neighbours; this ratio of limited address space to high peering density indicates a transit or content delivery role rather than an access network.
- Traffic from this AS consists of backend services for the Telegram instant messaging platform, including API endpoints, media storage, and signalling servers that support the global user base.
Notable
- Registrants for both the 91.108.12.0/22 and 149.154.172.0/22 prefixes are listed as Telegram Messenger Inc, matching the AS holder.
- The address inventory is compact, consisting of two /22 IPv4 blocks and a single /48 IPv6 block, all registered under the same netname.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 4 exchanges in 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| IX.br (PTT.br) São Paulo | São Paulo, Brazil | 187.16.209.180 |
| FL-IX - The Florida Internet Exchange / Community IX - Florida | Miami, United States | 206.41.108.63 |
| Equinix Internet Exchange Miami | Miami, United States | 198.32.242.10 |
| Equinix-LA(former Paix) | Los Angeles, United States | 198.32.242.10 |
Transit providers
11 upstream, 0 downstream and 18 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 2.05K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| VG | Virgin Islands (British) | 3 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS59930- Registry name
- Telegram_Messenger
- Registrant
- MNT-TELEGRAM
- Abuse contact
- abuse@telegram.org
- Registered
- 2014-08-05
- Last changed
- 2022-10-28
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 3 valid, 0 with no ROA
- ROAs
- 3 authorising AS59930
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 3 naming AS59930
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 431 networks and 1,775 prefixes, as published 2026-10-11. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere