bgpreport

Network · data from 2026-11-12

AS23172 PENTAGONFEDERALCU - Pentagon Federal Credit Union

Registry name: PENTAGONFEDERALCU - Pentagon Federal Credit Union, US · not in PeeringDB

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

Announced routes

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

199.250.244.0/24 No ROA Nonecovered by 199.250.244.0/23 672 100% 67
199.250.245.0/24 No ROA Nonecovered by 199.250.244.0/23 672 100% 67
199.250.246.0/24 No ROA Nonecovered by 199.250.246.0/23 672 100% 67
67.41.55.0/24 No ROA Other IRR onlyRADB 672 100% 67
199.250.244.0/23 No ROA Other IRR onlyRADB 671 100% 67
199.250.246.0/23 No ROA Other IRR onlyRADB 49 7%low visibility 28
50.234.6.0/24 Valid None 673 100% 67
64.253.166.0/24 Valid Other IRR onlyRADB 672 100% 67
98.182.105.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

AS23172 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 23 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR5
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none199.250.244.0/24No ROA covers it. Add a ROA for AS23172, maxLength 24.672 of 673
Route object: none199.250.244.0/24No route object for it. A route object for 199.250.244.0/23 with origin AS23172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23172 in the RIR database for the space.672 of 673
ROA: none199.250.245.0/24No ROA covers it. Add a ROA for AS23172, maxLength 24.672 of 673
Route object: none199.250.245.0/24No route object for it. A route object for 199.250.244.0/23 with origin AS23172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23172 in the RIR database for the space.672 of 673
ROA: none199.250.246.0/24No ROA covers it. Add a ROA for AS23172, maxLength 24.672 of 673
Route object: none199.250.246.0/24No route object for it. A route object for 199.250.246.0/23 with origin AS23172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23172 in the RIR database for the space.672 of 673
ROA: none67.41.55.0/24No ROA covers it. Add a ROA for AS23172, maxLength 24.672 of 673
Route object: RIR67.41.55.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.250.244.0/23No ROA covers it. Add a ROA for AS23172, maxLength 23.671 of 673
Route object: RIR199.250.244.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.250.246.0/23No ROA covers it. Add a ROA for AS23172, maxLength 23.49 of 673
Route object: RIR199.250.246.0/23Route object only in RADB. Add it in the RIR database for the space.49 of 673
Route object: none50.234.6.0/24No route object for it. Add a route object with origin AS23172 in the RIR database for the space.673 of 673
Route object: RIR64.253.166.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR98.182.105.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

12.36.205.0/24RADBNo ROA
63.239.227.0/24RADBNo ROA
199.250.244.0/22RADBNo ROA
208.4.60.0/22RADBNo ROA
208.4.60.0/24RADBNo ROA
208.4.61.0/24RADBNo ROA
208.4.62.0/24RADBNo ROA
208.4.63.0/24RADBNo 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.