bgpreport

Network · data from 2026-11-12

AS29068 UT-AS University of Tehran

Registry name: UT-AS University of Tehran, IR · not in PeeringDB

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

Announced routes

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

80.66.176.0/23 No ROA Nonecovered by 80.66.176.0/21 672 100% 67
80.66.178.0/23 No ROA Nonecovered by 80.66.176.0/21 672 100% 67
188.118.64.0/22 No ROA Nonecovered by 188.118.64.0/21 672 100% 67
188.118.68.0/22 No ROA Nonecovered by 188.118.64.0/21 672 100% 67
188.118.80.0/23 No ROA Nonecovered by 188.118.64.0/19 672 100% 67
188.118.85.0/24 No ROA Nonecovered by 188.118.64.0/19 671 100% 67
80.66.176.0/22 No ROA Nonecovered by 80.66.176.0/21 670 100% 67
188.118.72.0/21 No ROA Nonecovered by 188.118.64.0/19 670 100% 67
188.118.90.0/24 No ROA Nonecovered by 188.118.64.0/19 670 100% 67
188.118.64.0/18 No ROA RIR databaseRIPE 672 100% 67
80.66.176.0/20 No ROA RIR databaseRIPE 670 100% 67
185.197.112.0/22 No ROA RIR databaseRIPE 670 100% 67

AS-SET

AS29068 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 38 are in fix.csv.

  • ROA: none12
  • Route object: none9
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none80.66.176.0/23No ROA covers it. Add a ROA for AS29068, maxLength 23.672 of 673
Route object: none80.66.176.0/23No route object for it. A route object for 80.66.176.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.672 of 673
ROA: none80.66.178.0/23No ROA covers it. Add a ROA for AS29068, maxLength 23.672 of 673
Route object: none80.66.178.0/23No route object for it. A route object for 80.66.176.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.672 of 673
ROA: none188.118.64.0/22No ROA covers it. Add a ROA for AS29068, maxLength 22.672 of 673
Route object: none188.118.64.0/22No route object for it. A route object for 188.118.64.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.672 of 673
ROA: none188.118.68.0/22No ROA covers it. Add a ROA for AS29068, maxLength 22.672 of 673
Route object: none188.118.68.0/22No route object for it. A route object for 188.118.64.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.672 of 673
ROA: none188.118.80.0/23No ROA covers it. Add a ROA for AS29068, maxLength 23.672 of 673
Route object: none188.118.80.0/23No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.672 of 673
ROA: none188.118.85.0/24No ROA covers it. Add a ROA for AS29068, maxLength 24.671 of 673
Route object: none188.118.85.0/24No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.671 of 673
ROA: none80.66.176.0/22No ROA covers it. Add a ROA for AS29068, maxLength 22.670 of 673
Route object: none80.66.176.0/22No route object for it. A route object for 80.66.176.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.670 of 673
ROA: none188.118.72.0/21No ROA covers it. Add a ROA for AS29068, maxLength 21.670 of 673
Route object: none188.118.72.0/21No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.670 of 673
ROA: none188.118.90.0/24No ROA covers it. Add a ROA for AS29068, maxLength 24.670 of 673
Route object: none188.118.90.0/24No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space.670 of 673
ROA: none188.118.64.0/18No ROA covers it. Add a ROA for AS29068, maxLength 18.672 of 673
ROA: none80.66.176.0/20No ROA covers it. Add a ROA for AS29068, maxLength 20.670 of 673
ROA: none185.197.112.0/22No ROA covers it. Add a ROA for AS29068, maxLength 22.670 of 673

Route objects not announced

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

80.66.176.0/21RADB, RIPENo ROA
80.66.184.0/21RIPENo ROA
80.66.191.0/24RIPENo ROA
94.184.160.0/21RIPEInvalid: origin
94.184.168.0/21RIPEInvalid: origin
188.118.64.0/19RIPENo ROA
188.118.64.0/21RADB, RIPENo ROA
188.118.74.0/23RIPENo ROA
188.118.96.0/19RIPENo ROA
188.118.96.0/24RIPENo ROA
188.118.110.0/23RIPENo ROA
188.118.112.0/21RIPENo ROA
194.225.8.0/21RIPEInvalid: origin
194.225.8.0/22RIPEInvalid: origin
194.225.12.0/22RIPEInvalid: origin
194.225.14.0/24RIPEInvalid: origin
2001:14e8:9::/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.