Network · data from 2026-11-12
AS41734 COMIFAR-AS Comifar Distribuzione S.p.A.
Registry name: COMIFAR-AS Comifar Distribuzione S.p.A., IT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41734, 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.
| 89.221.128.0/23 | No ROA | Nonecovered by 89.221.128.0/20 | 673 100% |
| 89.221.128.0/24 | No ROA | Nonecovered by 89.221.128.0/20 | 673 100% |
| 89.221.130.0/23 | No ROA | Nonecovered by 89.221.128.0/20 | 673 100% |
| 89.221.130.0/24 | No ROA | Nonecovered by 89.221.128.0/20 | 673 100% |
| 89.221.129.32/27 | No ROA | Nonecovered by 89.221.128.0/20 | 18 3%low visibility |
| 89.221.131.32/27 | No ROA | Nonecovered by 89.221.128.0/20 | 18 3%low visibility |
AS-SET
AS41734 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 13 are in fix.csv.
- ROA: none6
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.221.128.0/23 | No ROA covers it. Add a ROA for AS41734, maxLength 23. |
| Route object: none | 89.221.128.0/23 | No route object for it. A route object for 89.221.128.0/20 with origin AS41734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41734 in the RIR database for the space. |
| ROA: none | 89.221.128.0/24 | No ROA covers it. Add a ROA for AS41734, maxLength 24. |
| Route object: none | 89.221.128.0/24 | No route object for it. A route object for 89.221.128.0/20 with origin AS41734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41734 in the RIR database for the space. |
| ROA: none | 89.221.130.0/23 | No ROA covers it. Add a ROA for AS41734, maxLength 23. |
| Route object: none | 89.221.130.0/23 | No route object for it. A route object for 89.221.128.0/20 with origin AS41734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41734 in the RIR database for the space. |
| ROA: none | 89.221.130.0/24 | No ROA covers it. Add a ROA for AS41734, maxLength 24. |
| Route object: none | 89.221.130.0/24 | No route object for it. A route object for 89.221.128.0/20 with origin AS41734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41734 in the RIR database for the space. |
| ROA: none | 89.221.129.32/27 | No ROA covers it. Add a ROA for AS41734, maxLength 27. |
| Route object: none | 89.221.129.32/27 | No route object for it. A route object for 89.221.128.0/20 with origin AS41734 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41734 in the RIR database for the space. |
| ROA: none | 89.221.131.32/27 | No ROA covers it. Add a ROA for AS41734, maxLength 27. |
| Route object: none | 89.221.131.32/27 | No route object for it. A route object for 89.221.128.0/20 with origin AS41734 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41734 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41734 whose prefix no peer sees AS41734 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.221.128.0/20 | 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.