ResearchRouting table, RPKI, IRR & looking glass

AS44907 Telegram Messenger Inc

AS44907 (Telegram_Messenger_CDN) is registered to Telegram Messenger Inc in VG. It originates 3 prefixes in the global routing table.

2
IPv4 prefixes
1
IPv6 prefixes
1,024
IPv4 addresses
100%
RPKI valid

Who holds AS44907

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS44907
Handle
Telegram_Messenger_CDN
Organization
Telegram Messenger Inc
Country
VG
ASPA
None published

What AS44907 announces

Prefixes originated by AS44907 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
2
IPv6 prefixes
1
IPv4 addresses
1,024 (4 /24s)
RPKI valid
3 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS44907
3
With an IRR route object
2 66%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (2)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS44907 buys transit from

Inferred from the AS paths in the RouteViews tables, refreshed every 4 hours, most-seen first. 2 upstreams.

Who buys transit from AS44907

None seen: AS44907 does not appear to provide transit to anyone.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RIPETelegram_Messenger_CDNRIPE-NCC-END-MNT, MNT-GLOBAL-NET

Route objects with origin AS44907: RIPE 9

as-sets that list AS44907 (14)