bgpreport

Network · data from 2026-11-12

AS33707 NUSHAGAK-ASN - Nushagak Electric & Telephone Cooperative, Inc.

Registry name: NUSHAGAK-ASN - Nushagak Electric & Telephone Cooperative, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33707, 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.
38.210.72.0/24 No ROA Nonecovered by 38.210.72.0/22 669 99% 67
38.210.73.0/24 No ROA Nonecovered by 38.210.72.0/22 669 99% 67
38.210.74.0/24 No ROA Nonecovered by 38.210.72.0/22 669 99% 67
38.210.75.0/24 No ROA Nonecovered by 38.210.72.0/22 669 99% 67
38.210.72.0/22 No ROA Other IRR onlyRADB 670 100% 67
2604:35c0::/32 Valid RIR databaseARIN 636 100% 68

AS-SET

AS33707 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 10 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.210.72.0/24No ROA covers it. Add a ROA for AS33707, maxLength 24.669 of 673
Route object: none38.210.72.0/24No route object for it. A route object for 38.210.72.0/22 with origin AS33707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33707 in the RIR database for the space.669 of 673
ROA: none38.210.73.0/24No ROA covers it. Add a ROA for AS33707, maxLength 24.669 of 673
Route object: none38.210.73.0/24No route object for it. A route object for 38.210.72.0/22 with origin AS33707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33707 in the RIR database for the space.669 of 673
ROA: none38.210.74.0/24No ROA covers it. Add a ROA for AS33707, maxLength 24.669 of 673
Route object: none38.210.74.0/24No route object for it. A route object for 38.210.72.0/22 with origin AS33707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33707 in the RIR database for the space.669 of 673
ROA: none38.210.75.0/24No ROA covers it. Add a ROA for AS33707, maxLength 24.669 of 673
Route object: none38.210.75.0/24No route object for it. A route object for 38.210.72.0/22 with origin AS33707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33707 in the RIR database for the space.669 of 673
ROA: none38.210.72.0/22No ROA covers it. Add a ROA for AS33707, maxLength 22.670 of 673
Route object: RIR38.210.72.0/22Route 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 AS33707 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.