bgpreport

Network · data from 2026-11-12

AS3724 ALASKA-ANET - State of Alaska

Registry name: ALASKA-ANET - State of Alaska, US · not in PeeringDB

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

Announced routes

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

204.29.174.0/24 No ROA Other origin onlycovered by 204.29.174.0/23 672 100% 67
146.63.71.0/25 No ROA Nonecovered by 146.63.0.0/16 3 0%low visibility 3
204.126.119.0/24 No ROA Other origin only 2 0%low visibility 2
146.63.0.0/16 No ROA Other IRR onlyRADB 671 100% 68
158.145.0.0/16 No ROA Other IRR onlyRADB 671 100% 68
204.89.222.0/24 No ROA Other IRR onlyRADB 671 100% 68
204.90.103.0/24 No ROA Other IRR onlyRADB 671 100% 68
204.126.118.0/24 No ROA Other IRR onlyRADB 671 100% 68
204.17.169.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 3
204.17.196.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 3
204.29.174.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 3
205.159.89.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 3
205.159.91.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 3
205.166.26.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 3

AS-SET

AS3724 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 31 are in fix.csv.

  • ROA: none14
  • Route object: none3
  • Route object: RIR11
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none204.29.174.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.672 of 673
Route object: none204.29.174.0/24Route objects for it name AS8047. A route object for 204.29.174.0/23 with origin AS3724 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3724 in the RIR database for the space.672 of 673
ROA: none146.63.71.0/25No ROA covers it. Add a ROA for AS3724, maxLength 25.3 of 673
Route object: none146.63.71.0/25No route object for it. A route object for 146.63.0.0/16 with origin AS3724 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS3724 in the RIR database for the space.3 of 673
ROA: none204.126.119.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.2 of 673
Route object: none204.126.119.0/24Route objects for it name AS8047. Add a route object with origin AS3724 in the RIR database for the space.2 of 673
ROA: none146.63.0.0/16No ROA covers it. Add a ROA for AS3724, maxLength 16.671 of 673
Route object: RIR146.63.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none158.145.0.0/16No ROA covers it. Add a ROA for AS3724, maxLength 16.671 of 673
Route object: RIR158.145.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.89.222.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.671 of 673
Route object: RIR204.89.222.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.90.103.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.671 of 673
Route object: RIR204.90.103.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.126.118.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.671 of 673
Route object: RIR204.126.118.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.17.169.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.2 of 673
Route object: RIR204.17.169.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none204.17.196.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.2 of 673
Route object: RIR204.17.196.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none204.29.174.0/23No ROA covers it. Add a ROA for AS3724, maxLength 23.2 of 673
Route object: RIR204.29.174.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none205.159.89.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.2 of 673
Route object: RIR205.159.89.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none205.159.91.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.2 of 673
Route object: RIR205.159.91.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none205.166.26.0/24No ROA covers it. Add a ROA for AS3724, maxLength 24.2 of 673
Route object: RIR205.166.26.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

198.22.190.0/24RADBNo ROA
198.245.186.0/24RADBNo ROA
204.29.175.0/24RADBNo ROA

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.