bgpreport

Network · data from 2026-11-12

AS18773 HENRICO-AS - County of Henrico

Registry name: HENRICO-AS - County of Henrico, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18773, 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.

173.242.160.0/24 No ROA None 672 100% 67
173.242.161.0/24 No ROA None 672 100% 67
173.242.162.0/24 No ROA None 672 100% 67
173.242.163.0/24 No ROA None 672 100% 67
173.242.164.0/24 No ROA None 672 100% 67
173.242.165.0/24 No ROA None 672 100% 67
173.242.166.0/24 No ROA None 672 100% 67
173.242.167.0/24 No ROA None 672 100% 67
173.242.168.0/24 No ROA None 672 100% 67
173.242.169.0/24 No ROA None 672 100% 67
173.242.170.0/24 No ROA None 672 100% 67
173.242.171.0/24 No ROA None 672 100% 67
173.242.172.0/24 No ROA None 672 100% 67
173.242.173.0/24 No ROA None 672 100% 67
173.242.175.0/24 No ROA None 672 100% 67

AS-SET

AS18773 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 30 are in fix.csv.

  • ROA: none15
  • Route object: none15
ChangePrefix or setDetailFull-table peers
ROA: none173.242.160.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.160.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.161.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.161.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.162.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.162.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.163.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.163.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.164.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.164.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.165.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.165.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.166.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.166.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.167.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.167.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.168.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.168.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.169.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.169.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.170.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.170.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.171.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.171.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.172.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.172.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.173.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.173.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673
ROA: none173.242.175.0/24No ROA covers it. Add a ROA for AS18773, maxLength 24.672 of 673
Route object: none173.242.175.0/24No route object for it. Add a route object with origin AS18773 in the RIR database for the space.672 of 673

Route objects not announced

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