bgpreport

Network · data from 2026-11-12

AS50577 INTELSC Ltd

Registry name: INTELSC-AS Intelsc Ltd., RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50577, 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.
195.191.158.0/24 No ROA Nonecovered by 195.191.158.0/23 83 12% 31
195.191.159.0/24 No ROA Nonecovered by 195.191.158.0/23 83 12% 31
188.191.160.0/21 No ROA RIR databaseRIPE 673 100% 66
195.191.158.0/23 No ROA RIR databaseRIPE 673 100% 66
188.191.160.0/24 No ROA RIR databaseRIPE 83 12% 31
188.191.161.0/24 No ROA RIR databaseRIPE 83 12% 31
188.191.162.0/24 No ROA RIR databaseRIPE 83 12% 31
188.191.163.0/24 No ROA RIR databaseRIPE 83 12% 31
188.191.164.0/24 No ROA RIR databaseRIPE 83 12% 31
188.191.165.0/24 No ROA RIR databaseRIPE 83 12% 31
188.191.166.0/24 No ROA RIR databaseRIPE 83 12% 31
188.191.167.0/24 No ROA RIR databaseRIPE 83 12% 31

AS-SET

AS50577'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 16 are in fix.csv.

  • ROA: none12
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none195.191.158.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
Route object: none195.191.158.0/24No route object for it. A route object for 195.191.158.0/23 with origin AS50577 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50577 in the RIR database for the space.83 of 673
ROA: none195.191.159.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
Route object: none195.191.159.0/24No route object for it. A route object for 195.191.158.0/23 with origin AS50577 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50577 in the RIR database for the space.83 of 673
ROA: none188.191.160.0/21No ROA covers it. Add a ROA for AS50577, maxLength 21.673 of 673
ROA: none195.191.158.0/23No ROA covers it. Add a ROA for AS50577, maxLength 23.673 of 673
ROA: none188.191.160.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
ROA: none188.191.161.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
ROA: none188.191.162.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
ROA: none188.191.163.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
ROA: none188.191.164.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
ROA: none188.191.165.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
ROA: none188.191.166.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673
ROA: none188.191.167.0/24No ROA covers it. Add a ROA for AS50577, maxLength 24.83 of 673

Route objects not announced

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

188.191.160.0/22RIPENo ROA
188.191.164.0/22RIPENo ROA

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.