bgpreport

Network · data from 2026-11-12

AS62041 Telegram Messenger EUR

Registry name: Telegram Telegram Messenger Inc, VG · PeeringDB

24IPv4 routes 100.0% RPKI valid · 91.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
55Route objects not announced registered with origin AS62041, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62041, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

95.161.64.0/21 Valid Nonecovered by 95.161.64.0/20 673 100% 67
95.161.72.0/21 Valid Nonecovered by 95.161.64.0/20 673 100% 67
91.108.4.0/22 Valid RIR databaseRIPE 673 100% 67
91.108.4.0/23 Valid RIR databaseRIPE 673 100% 67
91.108.6.0/23 Valid RIR databaseRIPE 673 100% 67
91.108.8.0/22 Valid RIR databaseRIPE 673 100% 67
91.108.8.0/23 Valid RIR databaseRIPE 673 100% 67
91.108.10.0/23 Valid RIR databaseRIPE 673 100% 67
91.108.56.0/22 Valid RIR databaseRIPE 673 100% 67
95.161.64.0/20 Valid RIR databaseRIPE 673 100% 67
149.154.160.0/22 Valid RIR databaseRIPE 673 100% 67
149.154.160.0/23 Valid RIR databaseRIPE 673 100% 67
149.154.160.0/24 Valid RIR databaseRIPE 673 100% 67
149.154.161.0/24 Valid RIR databaseRIPE 673 100% 67
149.154.162.0/23 Valid RIR databaseRIPE 673 100% 67
149.154.162.0/24 Valid RIR databaseRIPE 673 100% 67
149.154.163.0/24 Valid RIR databaseRIPE 673 100% 67
149.154.164.0/22 Valid RIR databaseRIPE 673 100% 67
149.154.164.0/23 Valid RIR databaseRIPE 673 100% 67
149.154.166.0/23 Valid RIR databaseRIPE 673 100% 67
149.154.166.0/24 Valid RIR databaseRIPE 673 100% 67
149.154.164.0/24 Valid RIR databaseRIPE 672 100% 67
149.154.165.0/24 Valid RIR databaseRIPE 670 100% 67
149.154.167.0/24 Valid RIR databaseRIPE 670 100% 67
2001:67c:4e8::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS62041's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 57 are in fix.csv.

  • Route object: none2
  • Route object: not announced55
ChangePrefix or setDetailFull-table peers
Route object: none95.161.64.0/21No route object for it. A route object for 95.161.64.0/20 with origin AS62041 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62041 in the RIR database for the space.673 of 673
Route object: none95.161.72.0/21No route object for it. A route object for 95.161.64.0/20 with origin AS62041 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62041 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS62041 whose prefix no peer sees AS62041 announce. Many are kept on purpose (backup routes, space announced only in some places).

91.108.4.0/24RIPEValid
91.108.5.0/24RIPEValid
91.108.6.0/24RIPEValid
91.108.7.0/24RIPEValid
91.108.8.0/24RIPEValid
91.108.9.0/24RIPEValid
91.108.10.0/24RIPEValid
91.108.11.0/24RIPEValid
91.108.56.0/23RIPEValid
91.108.56.0/24RIPEValid
91.108.57.0/24RIPEValid
91.108.58.0/23RIPEValid
91.108.58.0/24RIPEValid
91.108.59.0/24RIPEValid
95.161.64.0/23RIPEInvalid: maxLength
95.161.64.0/24RIPEInvalid: maxLength
95.161.65.0/24RIPEInvalid: maxLength
95.161.66.0/23RIPEInvalid: maxLength
95.161.66.0/24RIPEInvalid: maxLength
95.161.67.0/24RIPEInvalid: maxLength
95.161.68.0/23RIPEInvalid: maxLength
95.161.68.0/24RIPEInvalid: maxLength
95.161.69.0/24RIPEInvalid: maxLength
95.161.70.0/23RIPEInvalid: maxLength
95.161.70.0/24RIPEInvalid: maxLength
95.161.71.0/24RIPEInvalid: maxLength
95.161.72.0/23RIPEInvalid: maxLength
95.161.72.0/24RIPEInvalid: maxLength
95.161.73.0/24RIPEInvalid: maxLength
95.161.74.0/23RIPEInvalid: maxLength
95.161.74.0/24RIPEInvalid: maxLength
95.161.75.0/24RIPEInvalid: maxLength
95.161.76.0/23RIPEInvalid: maxLength
95.161.76.0/24RIPEInvalid: maxLength
95.161.77.0/24RIPEInvalid: maxLength
95.161.78.0/23RIPEInvalid: maxLength
95.161.78.0/24RIPEInvalid: maxLength
95.161.79.0/24RIPEInvalid: maxLength
95.161.80.0/24RIPENo ROA
149.154.160.0/20RIPENo ROA
149.154.160.0/21RIPENo ROA
149.154.168.0/21RIPENo ROA
149.154.168.0/23RIPEInvalid: origin
149.154.168.0/24RIPEInvalid: origin
149.154.169.0/24RIPEInvalid: origin
149.154.170.0/23RIPEInvalid: origin
149.154.170.0/24RIPEInvalid: origin
149.154.171.0/24RIPEInvalid: origin
149.154.172.0/23RIPEInvalid: origin
149.154.172.0/24RIPEInvalid: origin
149.154.173.0/24RIPEInvalid: origin
149.154.174.0/23RIPEInvalid: origin
149.154.174.0/24RIPEInvalid: origin
149.154.175.0/24RIPEInvalid: origin
2001:b28:f23f::/48RIPEInvalid: origin

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.