Network · data from 2026-11-12
AS29591 NETAPP-EMEA-AS NETAPP Holding and Manufacturing BV
Registry name: NETAPP-EMEA-AS NETAPP Holding and Manufacturing BV, NL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29591, 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.
| 217.70.210.0/24 | No ROA | Nonecovered by 217.70.208.0/22 | 673 100% |
| 217.70.212.0/24 | No ROA | Other origin onlycovered by 217.70.212.0/22 | 673 100% |
| 217.70.223.0/24 | No ROA | Nonecovered by 217.70.208.0/20 | 673 100% |
| 217.70.208.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 217.70.216.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 217.70.220.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.70.221.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS29591 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 16 are in fix.csv.
- ROA: none7
- Route object: none3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 217.70.210.0/24 | No ROA covers it. Add a ROA for AS29591, maxLength 24. |
| Route object: none | 217.70.210.0/24 | No route object for it. A route object for 217.70.208.0/22 with origin AS29591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29591 in the RIR database for the space. |
| ROA: none | 217.70.212.0/24 | No ROA covers it. Add a ROA for AS29591, maxLength 24. |
| Route object: none | 217.70.212.0/24 | Route objects for it name AS18105. A route object for 217.70.212.0/22 with origin AS29591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29591 in the RIR database for the space. |
| ROA: none | 217.70.223.0/24 | No ROA covers it. Add a ROA for AS29591, maxLength 24. |
| Route object: none | 217.70.223.0/24 | No route object for it. A route object for 217.70.208.0/20 with origin AS29591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29591 in the RIR database for the space. |
| ROA: none | 217.70.208.0/22 | No ROA covers it. Add a ROA for AS29591, maxLength 22. |
| ROA: none | 217.70.216.0/22 | No ROA covers it. Add a ROA for AS29591, maxLength 22. |
| ROA: none | 217.70.220.0/24 | No ROA covers it. Add a ROA for AS29591, maxLength 24. |
| ROA: none | 217.70.221.0/24 | No ROA covers it. Add a ROA for AS29591, maxLength 24. |
Route objects not announced
Route objects with origin AS29591 whose prefix no peer sees AS29591 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 217.70.208.0/20 | RIPE | No ROA |
| 217.70.209.0/24 | RIPE | No ROA |
| 217.70.212.0/22 | RIPE | No ROA |
| 217.70.223.0/32 | RIPE | No ROA |
| 2a00:1da0:4000::/48 | RIPE | No ROA |
| 2a00:1da0:4002::/48 | RIPE | No 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.