Autonomous system
AS44907 TELEGRAM_MESSENGER_CDN
Unclassified RIPE
Summary
Telegram Messenger
cdn messaging infrastructure
TELEGRAM_MESSENGER_CDN is operated by Telegram Messenger Inc.
What it's used for
- The space carries Telegram's content delivery infrastructure, identified by the netname
Telegram_CDN_Networkand the registry handleTelegram_Messenger_CDN. - The AS announces 1024 IPv4 addresses within a single /22 prefix and one IPv6 /48 prefix, with 8 observed routing neighbours.
- Traffic from this AS consists of CDN endpoints serving media, files, and API requests for the Telegram instant messaging platform.
Notable
- The RDAP registrant for the announced prefix is listed as
Abuse-C Role, which aligns with the operational entity Telegram Messenger Inc. - The address inventory is compact, consisting of one contiguous IPv4 block and one IPv6 block, typical for a dedicated CDN deployment.
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 2 exchanges in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| DE-CIX Mumbai | Mumbai, India | 103.27.171.25 |
| Extreme IX Mumbai | Mumbai, India | 103.77.108.77 |
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 1 prefixes · 1.02K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| VG | Virgin Islands (British) | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS44907- Registry name
- Telegram_Messenger_CDN
- Registrant
- MNT-GLOBAL-NET
- Abuse contact
- abuse@telegram.org
- Registered
- 2014-11-24
- Last changed
- 2022-10-28
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 3 valid, 0 with no ROA
- ROAs
- 3 authorising AS44907
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 9 naming AS44907
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
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