Network · data from 2026-11-12
AS394401 HEARST-DC4 - Hearst Corporation
Registry name: HEARST-DC4 - Hearst Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394401, 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.
| 167.173.56.0/24 | No ROA | Nonecovered by 167.173.56.0/22 | 673 100% |
| 167.173.57.0/24 | No ROA | Nonecovered by 167.173.56.0/22 | 673 100% |
| 167.173.58.0/24 | No ROA | Nonecovered by 167.173.56.0/22 | 673 100% |
| 167.173.59.0/24 | No ROA | Nonecovered by 167.173.56.0/22 | 673 100% |
| 167.173.56.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS394401 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 19 are in fix.csv.
- ROA: none5
- Route object: none4
- Route object: RIR1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 167.173.56.0/24 | No ROA covers it. Add a ROA for AS394401, maxLength 24. |
| Route object: none | 167.173.56.0/24 | No route object for it. A route object for 167.173.56.0/22 with origin AS394401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394401 in the RIR database for the space. |
| ROA: none | 167.173.57.0/24 | No ROA covers it. Add a ROA for AS394401, maxLength 24. |
| Route object: none | 167.173.57.0/24 | No route object for it. A route object for 167.173.56.0/22 with origin AS394401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394401 in the RIR database for the space. |
| ROA: none | 167.173.58.0/24 | No ROA covers it. Add a ROA for AS394401, maxLength 24. |
| Route object: none | 167.173.58.0/24 | No route object for it. A route object for 167.173.56.0/22 with origin AS394401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394401 in the RIR database for the space. |
| ROA: none | 167.173.59.0/24 | No ROA covers it. Add a ROA for AS394401, maxLength 24. |
| Route object: none | 167.173.59.0/24 | No route object for it. A route object for 167.173.56.0/22 with origin AS394401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394401 in the RIR database for the space. |
| ROA: none | 167.173.56.0/22 | No ROA covers it. Add a ROA for AS394401, maxLength 22. |
| Route object: RIR | 167.173.56.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394401 whose prefix no peer sees AS394401 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.173.80.0/20 | ALTDB | No ROA |
| 167.173.82.0/24 | ALTDB | No ROA |
| 167.173.83.0/24 | ALTDB | No ROA |
| 167.173.84.0/24 | ALTDB | No ROA |
| 167.173.88.0/24 | ALTDB | No ROA |
| 167.173.89.0/24 | ALTDB | No ROA |
| 167.173.90.0/24 | ALTDB | No ROA |
| 167.173.91.0/24 | ALTDB | No ROA |
| 167.173.92.0/24 | ALTDB | 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.