bgpreport

Network · data from 2026-11-12

AS41620 IUSTCC-AS Iran University Of Science and Technology

Registry name: IUSTCC-AS Iran University Of Science and Technology, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41620, 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.

194.225.228.0/24 Valid Other origin onlycovered by 194.225.224.0/21 671 100% 66
194.225.231.0/24 Valid Other origin onlycovered by 194.225.224.0/21 671 100% 66
194.225.232.0/24 Valid Other origin onlycovered by 194.225.232.0/21 671 100% 66
194.225.234.0/24 Valid Other origin onlycovered by 194.225.232.0/21 671 100% 66
194.225.239.0/24 Valid Other origin onlycovered by 194.225.236.0/22 671 100% 66
194.225.230.0/24 Valid Other origin onlycovered by 194.225.224.0/21 670 100% 66
194.225.233.0/24 Valid Other origin onlycovered by 194.225.232.0/21 670 100% 66
194.225.224.0/20 Valid RIR databaseRIPE 672 100% 67
194.225.224.0/21 Valid RIR databaseRIPE 671 100% 66
194.225.227.0/24 Valid RIR databaseRIPE 671 100% 66
194.225.232.0/21 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS41620 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 10 are in fix.csv.

  • Route object: none7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none194.225.228.0/24Route objects for it name AS6736. A route object for 194.225.224.0/21 with origin AS41620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41620 in the RIR database for the space.671 of 673
Route object: none194.225.231.0/24Route objects for it name AS6736. A route object for 194.225.224.0/21 with origin AS41620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41620 in the RIR database for the space.671 of 673
Route object: none194.225.232.0/24Route objects for it name AS6736. A route object for 194.225.232.0/21 with origin AS41620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41620 in the RIR database for the space.671 of 673
Route object: none194.225.234.0/24Route objects for it name AS6736. A route object for 194.225.232.0/21 with origin AS41620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41620 in the RIR database for the space.671 of 673
Route object: none194.225.239.0/24Route objects for it name AS6736. A route object for 194.225.236.0/22 with origin AS41620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41620 in the RIR database for the space.671 of 673
Route object: none194.225.230.0/24Route objects for it name AS6736. A route object for 194.225.224.0/21 with origin AS41620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41620 in the RIR database for the space.670 of 673
Route object: none194.225.233.0/24Route objects for it name AS6736. A route object for 194.225.232.0/21 with origin AS41620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41620 in the RIR database for the space.670 of 673

Route objects not announced

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

194.225.140.0/22RIPEInvalid: origin
194.225.236.0/22RIPEValid
2001:14e8:4::/48RIPEValid

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.