16IPv4 routes
12.5% RPKI valid · 31.2% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
14No ROA
11 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS16072, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS16072, 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.73.36.0/23 | No ROA | Nonecovered by 217.73.36.0/22 | 673 100% |
| 217.73.39.0/24 | No ROA | Nonecovered by 217.73.36.0/22 | 673 100% |
| 217.73.41.0/24 | No ROA | Other origin only | 673 100% |
| 217.73.42.0/23 | No ROA | Other origin only | 673 100% |
| 217.73.32.0/24 | No ROA | Nonecovered by 217.73.32.0/23 | 672 100% |
| 217.73.33.0/24 | No ROA | Nonecovered by 217.73.32.0/23 | 672 100% |
| 217.73.36.0/24 | No ROA | Nonecovered by 217.73.36.0/22 | 672 100% |
| 217.73.37.0/24 | No ROA | Nonecovered by 217.73.36.0/22 | 672 100% |
| 217.73.38.0/23 | No ROA | Nonecovered by 217.73.36.0/22 | 672 100% |
| 217.73.40.0/23 | No ROA | None | 672 100% |
| 217.73.38.0/24 | No ROA | Nonecovered by 217.73.36.0/22 | 670 100% |
| 217.73.40.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 217.73.32.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 217.73.42.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 170.186.205.0/24 | Valid | RIR databaseARIN | 673 100% |
| 170.186.207.0/24 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS16072's PeeringDB record names no 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 28 are in fix.csv.
- ROA: none14
- Route object: none11
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 217.73.36.0/23 | No ROA covers it. Add a ROA for AS16072, maxLength 23. |
| Route object: none | 217.73.36.0/23 | No route object for it. A route object for 217.73.36.0/22 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.39.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: none | 217.73.39.0/24 | No route object for it. A route object for 217.73.36.0/22 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.41.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: none | 217.73.41.0/24 | Route objects for it name AS21169. Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.42.0/23 | No ROA covers it. Add a ROA for AS16072, maxLength 23. |
| Route object: none | 217.73.42.0/23 | Route objects for it name AS198949. Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.32.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: none | 217.73.32.0/24 | No route object for it. A route object for 217.73.32.0/23 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.33.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: none | 217.73.33.0/24 | No route object for it. A route object for 217.73.32.0/23 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.36.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: none | 217.73.36.0/24 | No route object for it. A route object for 217.73.36.0/22 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.37.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: none | 217.73.37.0/24 | No route object for it. A route object for 217.73.36.0/22 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.38.0/23 | No ROA covers it. Add a ROA for AS16072, maxLength 23. |
| Route object: none | 217.73.38.0/23 | No route object for it. A route object for 217.73.36.0/22 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.40.0/23 | No ROA covers it. Add a ROA for AS16072, maxLength 23. |
| Route object: none | 217.73.40.0/23 | No route object for it. Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.38.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: none | 217.73.38.0/24 | No route object for it. A route object for 217.73.36.0/22 with origin AS16072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16072 in the RIR database for the space. |
| ROA: none | 217.73.40.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
| Route object: RIR | 217.73.40.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 217.73.32.0/23 | No ROA covers it. Add a ROA for AS16072, maxLength 23. |
| ROA: none | 217.73.42.0/24 | No ROA covers it. Add a ROA for AS16072, maxLength 24. |
Route objects not announced
Route objects with origin AS16072 whose prefix no peer sees AS16072 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.0.196.0/24 | RADB | No ROA |
| 217.73.36.0/22 | 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.