bgpreport

Network · data from 2026-11-12

AS16435 FLUKE-ELECTRONICS - Fluke Electronics

Registry name: FLUKE-ELECTRONICS - Fluke Electronics, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16435, 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.
129.196.230.0/24 No ROA Nonecovered by 129.196.224.0/19 673 100% 67
129.196.231.0/24 No ROA Nonecovered by 129.196.224.0/19 673 100% 67
129.196.0.0/17 No ROA Nonecovered by 129.196.0.0/16 672 100% 67
129.196.128.0/17 No ROA Nonecovered by 129.196.0.0/16 672 100% 67
129.196.0.0/16 No ROA Other IRR onlyRADB 673 100% 67
129.196.224.0/19 No ROA Other IRR onlyRADB 672 100% 67
129.196.226.0/24 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS16435 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none129.196.230.0/24No ROA covers it. Add a ROA for AS16435, maxLength 24.673 of 673
Route object: none129.196.230.0/24No route object for it. A route object for 129.196.224.0/19 with origin AS16435 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16435 in the RIR database for the space.673 of 673
ROA: none129.196.231.0/24No ROA covers it. Add a ROA for AS16435, maxLength 24.673 of 673
Route object: none129.196.231.0/24No route object for it. A route object for 129.196.224.0/19 with origin AS16435 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16435 in the RIR database for the space.673 of 673
ROA: none129.196.0.0/17No ROA covers it. Add a ROA for AS16435, maxLength 17.672 of 673
Route object: none129.196.0.0/17No route object for it. A route object for 129.196.0.0/16 with origin AS16435 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16435 in the RIR database for the space.672 of 673
ROA: none129.196.128.0/17No ROA covers it. Add a ROA for AS16435, maxLength 17.672 of 673
Route object: none129.196.128.0/17No route object for it. A route object for 129.196.0.0/16 with origin AS16435 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16435 in the RIR database for the space.672 of 673
ROA: none129.196.0.0/16No ROA covers it. Add a ROA for AS16435, maxLength 16.673 of 673
Route object: RIR129.196.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.196.224.0/19No ROA covers it. Add a ROA for AS16435, maxLength 19.672 of 673
Route object: RIR129.196.224.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none129.196.226.0/24No ROA covers it. Add a ROA for AS16435, maxLength 24.670 of 673
Route object: RIR129.196.226.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS16435 is announced.

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.