Autonomous system
AS62014 TELEGRAM
Hosting RIPE
Summary
Telegram
messaging cloud infrastructure
The AS handle TELEGRAM is held by Telegram Messenger Inc.
What it's used for
- The address space carries the Telegram messaging platform, with all three IPv4 prefixes registered under the netname
Telegram_Messenger_Network. - The inventory consists of 2560 IPv4 addresses across 3 prefixes and 1 IPv6 prefix, connected to 22 observed neighbours.
- Traffic from this AS comprises the backend infrastructure for Telegram's cloud-based instant messaging service, including API endpoints and media storage for its global user base.
Notable
- All registrants for the announced prefixes are
Telegram Messenger Inc, matching the AS holder. - The address inventory is compact and subdivided into three distinct IPv4 blocks, consistent with an internal corporate estate for a specific service provider.
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 3 exchanges in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Equinix Internet Exchange Singapore | Singapore, Singapore | 27.111.229.210 |
| Singapore Internet Exchange | Singapore, Singapore | 103.16.102.92 |
| DE-CIX ASEAN (Singapore, Malaysia, Brunei) | Singapore, Singapore | 103.162.254.119 |
Transit providers
10 upstream, 0 downstream and 17 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-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 2.56K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| VG | Virgin Islands (British) | 4 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS62014- Registry name
- Telegram
- Registrant
- MNT-TELEGRAM
- Abuse contact
- abuse@telegram.org
- Registered
- 2014-03-24
- Last changed
- 2022-10-28
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 8 valid, 0 with no ROA
- ROAs
- 8 authorising AS62014
- ASPA
- no ASPA record
- IRR
- 100% registered · 8 of 8 announcements
- Route objects
- 9 naming AS62014
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: 432 networks and 1,768 prefixes, as published 2026-10-12. 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