Objects With Suspicious Boundaries

Some inetnum objects are just mistyped into the database. While there is not a straightforward way, there are some ways to detect particular mistakes. While checking for shifted overlaps is one way, there is another opportunity to check for mistakes by checking the minimum required number of CIDR-type addresses to describe the inetnum block. If it can't be represented by only one address and one of the addresses contain a network smaller than /28, then it is suggested to be an unreal network block.

Example:

The inetnum object 10.10.34.0 - 10.10.34.147 would be an object with a suspicious boundary, since this address space can be presented only by 10.10.34.0/25, 10.10.34.128/28 and 10.10.34.144/30, that is, three CIDR-type addresses, containing one network smaller than /28.