The more specific route (longer prefix /30) will take priority over less specific route (shorter prefix /24). Therefore, 192.168.1.8/30 will be routed to 184.108.40.206. All other host under 192.168.1.0/24 (except 192.168.1.8/30 and 192.168.1.12/30) will be routed to 220.127.116.11
I do not see anything here that would cause issues. I see that EIGRP has learned 5 entries about the addres space: it has learned a /24 from one neighbor (18.104.22.168), it has learned a more specific /30 and /32 from another neighbor (22.214.171.124), and it has learned another more specific /30 and /32 from a third neighbor (126.96.36.199).
I am not sure what it means but I note that the /32 address is included within the /30 subnet and is advertised as EIGRP external so the /32 came via redistribution of something whle the /30 came via a network statement.
It is not a problem to have multiple entries which in a sense overlap each other or are contained within each other. The /32 is within the /30 which is within the /24. The way that IOS does route lookup is on the basis of longest match. So even though different neighbors are advertising different parts of the address space we should route to the correct neighbor.
Rick has covered this in great detail. The only thing i would like to add is that if your link to 188.8.131.52 goes down then the next best route will be chosen, in this case 192.168.1.0/24 via 184.108.40.206. This may or may not be what you want depending on the topology of your network, speed of links etc.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...