bgpreport

Network · data from 2026-11-12

AS3926 FFX-CNTY - Fairfax County Dept of Information Technology

Registry name: FFX-CNTY - Fairfax County Dept of Information Technology, US · not in PeeringDB

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

Announced routes

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

166.94.16.0/24 No ROA Nonecovered by 166.94.0.0/16 673 100% 67
166.94.112.0/24 No ROA Nonecovered by 166.94.0.0/16 673 100% 67
166.94.113.0/24 No ROA Nonecovered by 166.94.0.0/16 673 100% 67
166.94.0.0/16 No ROA Other IRR onlyRADB 673 100% 67
166.94.176.0/20 No ROA Other IRR onlyRADB 673 100% 67
198.24.16.0/20 No ROA Other IRR onlyRADB 673 100% 67
166.94.15.0/24 No ROA Other IRR onlyRADB 671 100% 67
166.94.150.0/23 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS3926 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 25 are in fix.csv.

  • ROA: none8
  • Route object: none3
  • Route object: RIR5
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none166.94.16.0/24No ROA covers it. Add a ROA for AS3926, maxLength 24.673 of 673
Route object: none166.94.16.0/24No route object for it. A route object for 166.94.0.0/16 with origin AS3926 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3926 in the RIR database for the space.673 of 673
ROA: none166.94.112.0/24No ROA covers it. Add a ROA for AS3926, maxLength 24.673 of 673
Route object: none166.94.112.0/24No route object for it. A route object for 166.94.0.0/16 with origin AS3926 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3926 in the RIR database for the space.673 of 673
ROA: none166.94.113.0/24No ROA covers it. Add a ROA for AS3926, maxLength 24.673 of 673
Route object: none166.94.113.0/24No route object for it. A route object for 166.94.0.0/16 with origin AS3926 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3926 in the RIR database for the space.673 of 673
ROA: none166.94.0.0/16No ROA covers it. Add a ROA for AS3926, maxLength 16.673 of 673
Route object: RIR166.94.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none166.94.176.0/20No ROA covers it. Add a ROA for AS3926, maxLength 20.673 of 673
Route object: RIR166.94.176.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.24.16.0/20No ROA covers it. Add a ROA for AS3926, maxLength 20.673 of 673
Route object: RIR198.24.16.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none166.94.15.0/24No ROA covers it. Add a ROA for AS3926, maxLength 24.671 of 673
Route object: RIR166.94.15.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none166.94.150.0/23No ROA covers it. Add a ROA for AS3926, maxLength 23.671 of 673
Route object: RIR166.94.150.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

166.94.6.0/24RADBNo ROA
166.94.8.0/21RADBNo ROA
166.94.36.0/24RADBNo ROA
166.94.148.0/23RADBNo ROA
166.94.192.0/24RADBNo ROA
198.24.28.0/23RADBNo ROA
198.24.30.0/24RADBNo ROA
198.24.31.0/24RADBNo ROA
2606:d00::/32RADBNo 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.