Network · data from 2026-11-12
AS32062 ARMSTRONGWORLD-01 - Armstrong World Industries, Inc.
Registry name: ARMSTRONGWORLD-01 - Armstrong World Industries, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32062, 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.
| 204.74.19.0/24 | No ROA | Nonecovered by 204.74.16.0/20 | 673 100% |
| 204.74.20.0/24 | No ROA | Nonecovered by 204.74.16.0/20 | 671 100% |
| 204.74.22.0/24 | No ROA | Nonecovered by 204.74.16.0/20 | 671 100% |
| 204.74.24.0/24 | No ROA | Nonecovered by 204.74.16.0/20 | 671 100% |
| 204.74.23.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 204.74.28.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS32062 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 17 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.74.19.0/24 | No ROA covers it. Add a ROA for AS32062, maxLength 24. |
| Route object: none | 204.74.19.0/24 | No route object for it. A route object for 204.74.16.0/20 with origin AS32062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32062 in the RIR database for the space. |
| ROA: none | 204.74.20.0/24 | No ROA covers it. Add a ROA for AS32062, maxLength 24. |
| Route object: none | 204.74.20.0/24 | No route object for it. A route object for 204.74.16.0/20 with origin AS32062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32062 in the RIR database for the space. |
| ROA: none | 204.74.22.0/24 | No ROA covers it. Add a ROA for AS32062, maxLength 24. |
| Route object: none | 204.74.22.0/24 | No route object for it. A route object for 204.74.16.0/20 with origin AS32062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32062 in the RIR database for the space. |
| ROA: none | 204.74.24.0/24 | No ROA covers it. Add a ROA for AS32062, maxLength 24. |
| Route object: none | 204.74.24.0/24 | No route object for it. A route object for 204.74.16.0/20 with origin AS32062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32062 in the RIR database for the space. |
| ROA: none | 204.74.23.0/24 | No ROA covers it. Add a ROA for AS32062, maxLength 24. |
| Route object: RIR | 204.74.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.74.28.0/24 | No ROA covers it. Add a ROA for AS32062, maxLength 24. |
| Route object: RIR | 204.74.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32062 whose prefix no peer sees AS32062 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 4.15.197.0/24 | RADB | No ROA |
| 8.38.168.0/24 | RADB | No ROA |
| 8.38.169.0/24 | RADB | No ROA |
| 204.74.16.0/20 | RADB | No ROA |
| 204.74.25.0/24 | RADB | 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.