bgpreport

Network · data from 2026-11-12

AS17394 NETAPP-AS-1 - NetApp, Inc.

Registry name: NETAPP-AS-1 - NetApp, Inc., US · not in PeeringDB

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

Announced routes

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

46.149.16.0/20 No ROA None 673 100% 67
216.240.16.0/24 No ROA Nonecovered by 216.240.16.0/22 673 100% 67
216.240.17.0/24 No ROA Nonecovered by 216.240.16.0/22 673 100% 67
216.240.21.0/24 No ROA None 673 100% 67
198.95.224.0/22 No ROA Other IRR onlyRADB 673 100% 67
216.240.20.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.240.22.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.240.29.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.240.30.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.240.31.0/24 No ROA Other IRR onlyRADB 673 100% 67
2620:10a:4003::/48 No ROA Other IRR onlyRADB 636 100% 67
2620:10a:4005::/48 No ROA Other IRR onlyRADB 636 100% 67
2620:10a:4004::/48 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

AS17394 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 41 are in fix.csv.

  • ROA: none13
  • Route object: none4
  • Route object: RIR9
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none46.149.16.0/20No ROA covers it. Add a ROA for AS17394, maxLength 20.673 of 673
Route object: none46.149.16.0/20No route object for it. Add a route object with origin AS17394 in the RIR database for the space.673 of 673
ROA: none216.240.16.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: none216.240.16.0/24No route object for it. A route object for 216.240.16.0/22 with origin AS17394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17394 in the RIR database for the space.673 of 673
ROA: none216.240.17.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: none216.240.17.0/24No route object for it. A route object for 216.240.16.0/22 with origin AS17394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17394 in the RIR database for the space.673 of 673
ROA: none216.240.21.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: none216.240.21.0/24No route object for it. Add a route object with origin AS17394 in the RIR database for the space.673 of 673
ROA: none198.95.224.0/22No ROA covers it. Add a ROA for AS17394, maxLength 22.673 of 673
Route object: RIR198.95.224.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.240.20.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: RIR216.240.20.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.240.22.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: RIR216.240.22.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.240.29.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: RIR216.240.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.240.30.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: RIR216.240.30.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.240.31.0/24No ROA covers it. Add a ROA for AS17394, maxLength 24.673 of 673
Route object: RIR216.240.31.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2620:10a:4003::/48No ROA covers it. Add a ROA for AS17394, maxLength 48.636 of 636
Route object: RIR2620:10a:4003::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2620:10a:4005::/48No ROA covers it. Add a ROA for AS17394, maxLength 48.636 of 636
Route object: RIR2620:10a:4005::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2620:10a:4004::/48No ROA covers it. Add a ROA for AS17394, maxLength 48.635 of 636
Route object: RIR2620:10a:4004::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

185.35.244.0/22RADBNo ROA
185.35.244.0/24RADBNo ROA
185.35.245.0/24RADBNo ROA
185.35.246.0/24RADBNo ROA
185.35.247.0/24RADBNo ROA
198.95.224.0/24RADBNo ROA
198.95.225.0/24RADBNo ROA
198.95.226.0/24RADBNo ROA
202.3.112.0/24RADBNo ROA
202.3.113.0/24RADBNo ROA
202.3.119.0/24RADBNo ROA
216.240.16.0/22RADBNo ROA
216.240.23.0/24RADBNo ROA
2620:10a:4001::/48RADBNo ROA
2620:10a:40f0::/56ARINNo 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.