bgpreport

Network · data from 2026-11-12

AS32075 FBL-AS - Iowa Farm Bureau Federation & Affiliated Cos.

Registry name: FBL-AS - Iowa Farm Bureau Federation & Affiliated Cos., US · not in PeeringDB

8IPv4 routes 25.0% RPKI valid · 62.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
6No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS32075, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS32075, 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.
38.190.181.0/24 No ROA None 672 100% 67
74.112.20.0/24 No ROA Nonecovered by 74.112.20.0/22 672 100% 67
74.112.21.0/24 No ROA Nonecovered by 74.112.20.0/22 672 100% 67
205.170.225.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.108.40.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.109.139.0/24 No ROA Other IRR onlyRADB 673 100% 67
12.236.201.0/24 Valid RIR databaseARIN 671 100% 68
12.32.252.0/24 Valid RIR databaseARIN, RADB 670 100% 68

AS-SET

AS32075 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.190.181.0/24No ROA covers it. Add a ROA for AS32075, maxLength 24.672 of 673
Route object: none38.190.181.0/24No route object for it. Add a route object with origin AS32075 in the RIR database for the space.672 of 673
ROA: none74.112.20.0/24No ROA covers it. Add a ROA for AS32075, maxLength 24.672 of 673
Route object: none74.112.20.0/24No route object for it. A route object for 74.112.20.0/22 with origin AS32075 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32075 in the RIR database for the space.672 of 673
ROA: none74.112.21.0/24No ROA covers it. Add a ROA for AS32075, maxLength 24.672 of 673
Route object: none74.112.21.0/24No route object for it. A route object for 74.112.20.0/22 with origin AS32075 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32075 in the RIR database for the space.672 of 673
ROA: none205.170.225.0/24No ROA covers it. Add a ROA for AS32075, maxLength 24.673 of 673
Route object: RIR205.170.225.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.108.40.0/24No ROA covers it. Add a ROA for AS32075, maxLength 24.673 of 673
Route object: RIR207.108.40.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.109.139.0/24No ROA covers it. Add a ROA for AS32075, maxLength 24.673 of 673
Route object: RIR207.109.139.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

74.112.20.0/22RADBNo 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.