bgpreport

Network · data from 2026-11-12

AS3769 HEARST-AS - Hearst Magazines, Inc.

Registry name: HEARST-AS - Hearst Magazines, Inc., US · not in PeeringDB

9IPv4 routes 0.0% RPKI valid · 33.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
9No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS3769, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS3769, 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.8.0/24 No ROA None 673 100% 67
167.173.9.0/24 No ROA None 673 100% 67
167.173.10.0/23 No ROA None 673 100% 67
198.185.162.0/24 No ROA None 673 100% 67
198.185.163.0/24 No ROA None 673 100% 67
198.185.164.0/24 No ROA None 673 100% 67
206.225.145.0/24 No ROA RIR databaseARIN 673 100% 67
206.225.146.0/24 No ROA RIR databaseARIN 673 100% 67
206.225.157.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS3769 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 15 are in fix.csv.

  • ROA: none9
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none167.173.8.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673
Route object: none167.173.8.0/24No route object for it. Add a route object with origin AS3769 in the RIR database for the space.673 of 673
ROA: none167.173.9.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673
Route object: none167.173.9.0/24No route object for it. Add a route object with origin AS3769 in the RIR database for the space.673 of 673
ROA: none167.173.10.0/23No ROA covers it. Add a ROA for AS3769, maxLength 23.673 of 673
Route object: none167.173.10.0/23No route object for it. Add a route object with origin AS3769 in the RIR database for the space.673 of 673
ROA: none198.185.162.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673
Route object: none198.185.162.0/24No route object for it. Add a route object with origin AS3769 in the RIR database for the space.673 of 673
ROA: none198.185.163.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673
Route object: none198.185.163.0/24No route object for it. Add a route object with origin AS3769 in the RIR database for the space.673 of 673
ROA: none198.185.164.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673
Route object: none198.185.164.0/24No route object for it. Add a route object with origin AS3769 in the RIR database for the space.673 of 673
ROA: none206.225.145.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673
ROA: none206.225.146.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673
ROA: none206.225.157.0/24No ROA covers it. Add a ROA for AS3769, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS3769 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.