Skip to main content

AS59930

Telegram_Messenger

Telegram Messenger Inc

Registry

Authoritative registration data

AS number
59930
Name
Telegram_Messenger
Organisation
Telegram Messenger Inc
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS59930
149.154.172.0/22 IPv4 /22 not checked
91.108.12.0/22 IPv4 /22 not checked
2001:b28:f23d::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS59930
Address families
Equinix Miami 200,000 Mbps IPv4 · IPv6
FL-IX 100,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 200,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS59930 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS59930 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 136 204
v4 v6
AS9002 RETN-AS 73 176
v4 v6
AS1299 TWELVE99 44 94
v4 v6
AS174 COGENT-174 37 78
v4 v6
AS6453 AS6453 25 55
v4 v6
AS1273 CW 23 51
v4 v6
AS3491 PCCWG-APAC-HK 16 35
v4 v6
AS3356 LEVEL3 26 34
v4 v6
AS6762 SEABONE-NET 15 23
v4 v6
AS12956 TELXIUS 3 4
v6
AS6057 6057 2 4
v4 v6
AS37468 ORG-AC4-AFRINIC 2 4
v4
AS61626 ASN61626 1 3
v4 v6
AS31500 GNM-AS 1 2
v4
AS64126 64126 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS59930 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

21 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.