bgpreport

Network · data from 2026-11-12

AS51655 ILIM-NET Ilim Telecom Ltd.

Registry name: ILIM-NET Ilim Telecom Ltd., RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51655, 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.
2001:67c:8d8::/48 No ROA None 458 72% 66
91.219.136.0/24 No ROA RIR databaseRIPE 673 100% 66
91.219.137.0/24 No ROA RIR databaseRIPE 673 100% 66
91.219.138.0/24 No ROA RIR databaseRIPE 673 100% 66
91.219.139.0/24 No ROA RIR databaseRIPE 673 100% 66
91.237.220.0/24 No ROA RIR databaseRIPE 673 100% 66
91.237.221.0/24 No ROA RIR databaseRIPE 673 100% 66
91.237.222.0/24 No ROA RIR databaseRIPE 673 100% 66
91.237.223.0/24 No ROA RIR databaseRIPE 673 100% 66
2001:67c:2714::/48 No ROA RIR databaseRIPE 636 100% 68

AS-SET

AS51655 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 11 are in fix.csv.

  • ROA: none10
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:8d8::/48No ROA covers it. Add a ROA for AS51655, maxLength 48.458 of 636
Route object: none2001:67c:8d8::/48No route object for it. Add a route object with origin AS51655 in the RIR database for the space.458 of 636
ROA: none91.219.136.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none91.219.137.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none91.219.138.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none91.219.139.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none91.237.220.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none91.237.221.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none91.237.222.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none91.237.223.0/24No ROA covers it. Add a ROA for AS51655, maxLength 24.673 of 673
ROA: none2001:67c:2714::/48No ROA covers it. Add a ROA for AS51655, maxLength 48.636 of 636

Route objects not announced

Every route object with origin AS51655 is announced.

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.