Autonomous system
AS62041 TELEGRAM
Hosting RIPE Content
Summary
Telegram
messaging infrastructure cloud business
TELEGRAM is operated by Telegram Messenger Inc.
What it's used for
- The address space carries Telegram's messaging infrastructure, evidenced by netnames such as
Telegram_Messenger_NetworkandTM-SUBNETS. - The AS announces 8704 IPv4 addresses across 5 prefixes and 1 IPv6 prefix, while maintaining 156 observed neighbours, indicating a role focused on serving application traffic rather than providing transit.
- Traffic from this AS consists of backend services for the Telegram instant messaging platform, including API endpoints and media storage for its global user base.
Notable
- Registrants for the 91.108.0.0/22 range align with the announcer, listing Telegram Messenger Inc, while the 95.161.64.0/20 and 149.154.160.0/21 blocks list Global Network Management Inc.
- The address inventory is subdivided into five distinct IPv4 prefixes, reflecting a segmented corporate estate for different service components.
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 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.193.148 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.209.69 |
Transit providers
37 upstream, 0 downstream and 50 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-30, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 5 prefixes · 8.70K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| VG | Virgin Islands (British) | 6 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS62041- Registry name
- Telegram
- Registrant
- MNT-TELEGRAM
- Abuse contact
- abuse@telegram.org
- Registered
- 2014-03-07
- Last changed
- 2025-08-11
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Telegram Messenger EUR
- Network type
- Content
- Scope
- Not Disclosed
- Traffic ratio
- Heavy Outbound
- Peering policy
- Open
- Present at
- 4 exchanges
- Facilities
- 2 facilities
- Website
- https://telegram.org
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 25 valid, 0 with no ROA
- ROAs
- 39 authorising AS62041
- ASPA
- no ASPA record
- IRR
- 100% registered · 25 of 25 announcements
- Route objects
- 78 naming AS62041
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: 448 networks and 1,849 prefixes, as published 2026-10-30. 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