bgpreport

Network · data from 2026-11-12

AS22054 HOOD-CANAL - Hood Canal Communications

Registry name: HOOD-CANAL - Hood Canal Communications, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22054, 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.
206.214.48.0/20 No ROA Other IRR onlyRADB 672 100% 67
216.122.8.0/21 No ROA Other IRR onlyRADB 672 100% 67
216.235.96.0/19 No ROA Other IRR onlyRADB 672 100% 67
64.239.110.0/23 No ROA Other IRR onlyRADB 670 100% 67
66.179.108.0/22 No ROA Other IRR onlyRADB 670 100% 67
164.152.178.0/23 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS22054 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 12 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none206.214.48.0/20No ROA covers it. Add a ROA for AS22054, maxLength 20.672 of 673
Route object: RIR206.214.48.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.122.8.0/21No ROA covers it. Add a ROA for AS22054, maxLength 21.672 of 673
Route object: RIR216.122.8.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.235.96.0/19No ROA covers it. Add a ROA for AS22054, maxLength 19.672 of 673
Route object: RIR216.235.96.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none64.239.110.0/23No ROA covers it. Add a ROA for AS22054, maxLength 23.670 of 673
Route object: RIR64.239.110.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none66.179.108.0/22No ROA covers it. Add a ROA for AS22054, maxLength 22.670 of 673
Route object: RIR66.179.108.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none164.152.178.0/23No ROA covers it. Add a ROA for AS22054, maxLength 23.670 of 673
Route object: RIR164.152.178.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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