Network · data from 2026-11-12
AS47049 CERMAK-COLO-PUBLIC - HNI Corporation
Registry name: CERMAK-COLO-PUBLIC - HNI Corporation, US · not in PeeringDB
12IPv4 routes
0.0% RPKI valid · 8.3% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
12No ROA
11 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS47049, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS47049, 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.
| 192.237.32.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 673 100% |
| 192.237.34.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.35.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.36.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.37.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.38.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.52.0/22 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.56.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.57.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.58.0/24 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.60.0/22 | No ROA | Nonecovered by 192.237.32.0/19 | 672 100% |
| 192.237.32.0/19 | No ROA | Other IRR onlyALTDB | 673 100% |
AS-SET
AS47049 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 24 are in fix.csv.
- ROA: none12
- Route object: none11
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.237.32.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.32.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.34.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.34.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.35.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.35.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.36.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.36.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.37.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.37.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.38.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.38.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.52.0/22 | No ROA covers it. Add a ROA for AS47049, maxLength 22. |
| Route object: none | 192.237.52.0/22 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.56.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.56.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.57.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.57.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.58.0/24 | No ROA covers it. Add a ROA for AS47049, maxLength 24. |
| Route object: none | 192.237.58.0/24 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.60.0/22 | No ROA covers it. Add a ROA for AS47049, maxLength 22. |
| Route object: none | 192.237.60.0/22 | No route object for it. A route object for 192.237.32.0/19 with origin AS47049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47049 in the RIR database for the space. |
| ROA: none | 192.237.32.0/19 | No ROA covers it. Add a ROA for AS47049, maxLength 19. |
| Route object: RIR | 192.237.32.0/19 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS47049 is announced.
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.