bgpreport

Network · data from 2026-11-12

AS33236 Hood River Electric & Internet Coop

Registry name: HREC-AS-01 - Hood River Electric Cooperative, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33236, 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.71.150.0/24 Valid Nonecovered by 206.71.150.0/23 673 100% 67
206.71.151.0/24 Valid Nonecovered by 206.71.150.0/23 673 100% 67
69.1.100.0/24 Valid Other IRR onlyRADB 673 100% 67
69.1.112.0/24 Valid Other IRR onlyRADB 673 100% 67
104.244.4.0/24 Valid Other IRR onlyRADB 673 100% 67
104.244.5.0/24 Valid Other IRR onlyRADB 673 100% 67
104.244.6.0/24 Valid Other IRR onlyRADB 673 100% 67
104.244.7.0/24 Valid Other IRR onlyRADB 673 100% 67
216.110.201.0/24 Valid Other IRR onlyRADB 673 100% 67
209.196.80.0/20 Valid RIR databaseARIN, RADB 673 100% 67
2606:efc0::/32 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

AS33236's PeeringDB record names no 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.

  • Route object: none2
  • Route object: RIR7
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none206.71.150.0/24No route object for it. A route object for 206.71.150.0/23 with origin AS33236 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33236 in the RIR database for the space.673 of 673
Route object: none206.71.151.0/24No route object for it. A route object for 206.71.150.0/23 with origin AS33236 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33236 in the RIR database for the space.673 of 673
Route object: RIR69.1.100.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR69.1.112.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.244.4.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.244.5.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.244.6.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.244.7.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.110.201.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS33236 whose prefix no peer sees AS33236 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.87.104.0/24RADBNo ROA
38.87.105.0/24RADBNo ROA
38.87.106.0/24RADBNo ROA
38.87.107.0/24RADBNo ROA
38.87.108.0/24RADBNo ROA
38.87.109.0/24RADBNo ROA
38.87.110.0/24RADBNo ROA
38.87.111.0/24RADBNo ROA
104.244.4.0/22ARINValid
206.71.150.0/23ARIN, RADBValid

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.