bgpreport

Network · data from 2026-11-12

AS50716 TELECOMRUNET Telecom.ru Ltd

Registry name: TELECOMRUNET Telecom.ru Ltd, RU · not in PeeringDB

9IPv4 routes 88.9% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS50716, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50716, 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.
176.116.142.0/24 Invalid: maxLength Nonecovered by 176.116.140.0/22 94 14% 38
146.158.87.0/24 Valid Nonecovered by 146.158.80.0/21 672 100% 67
176.116.140.0/23 Valid Nonecovered by 176.116.140.0/22 2 0%low visibility 3
87.76.0.0/20 Valid RIR databaseRIPE 673 100% 66
91.239.16.0/22 Valid RIR databaseRIPE 673 100% 66
93.171.72.0/22 Valid RIR databaseRIPE 673 100% 66
109.197.192.0/21 Valid RIR databaseRIPE 673 100% 66
146.158.80.0/21 Valid RIR databaseRIPE 673 100% 66
176.116.136.0/21 Valid RIR databaseRIPE 673 100% 66
2a00:d8c0:100::/48 Valid RIR databaseRIPE 366 58% 63

AS-SET

AS50716 isn't in PeeringDB, where networks name their 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 17 are in fix.csv.

  • ROA: maxLength1
  • Route object: none3
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: maxLength176.116.142.0/24ROA 176.116.136.0/21 AS50716 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 176.116.142.0/24.94 of 673
Route object: none176.116.142.0/24No route object for it. A route object for 176.116.140.0/22 with origin AS50716 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50716 in the RIR database for the space.94 of 673
Route object: none146.158.87.0/24No route object for it. A route object for 146.158.80.0/21 with origin AS50716 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50716 in the RIR database for the space.672 of 673
Route object: none176.116.140.0/23No route object for it. A route object for 176.116.140.0/22 with origin AS50716 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50716 in the RIR database for the space.2 of 673

Route objects not announced

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

87.76.0.0/21RIPEValid
87.76.0.0/22RIPEValid
87.76.3.0/24RIPEInvalid: maxLength
87.76.4.0/22RIPEValid
87.76.8.0/21RIPEValid
87.76.8.0/22RIPEValid
87.76.12.0/22RIPEValid
109.197.192.0/22RIPEValid
109.197.196.0/22RIPEValid
176.116.136.0/22RIPEValid
176.116.139.0/24RIPEInvalid: maxLength
176.116.140.0/22RIPEValid
176.116.143.0/24RIPEInvalid: maxLength

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.