bgpreport

Network · data from 2026-11-12

AS7774 ALASKA

Registry name: ALASKA - University of Alaska, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7774, 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.
137.229.0.0/16 No ROA RIR databaseARIN, RADB 671 100% 69
199.165.64.0/18 No ROA RIR databaseARIN, RADB 671 100% 69
2607:f318::/32 No ROA RIR databaseARIN, RADB 636 100% 68

AS-SET

AS7774'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 51 are in fix.csv.

  • ROA: none3
  • Route object: not announced48
ChangePrefix or setDetailFull-table peers
ROA: none137.229.0.0/16No ROA covers it. Add a ROA for AS7774, maxLength 16.671 of 673
ROA: none199.165.64.0/18No ROA covers it. Add a ROA for AS7774, maxLength 18.671 of 673
ROA: none2607:f318::/32No ROA covers it. Add a ROA for AS7774, maxLength 32.636 of 636

Route objects not announced

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

137.229.0.0/17RADBNo ROA
137.229.0.0/18RADBNo ROA
137.229.64.0/19RADBNo ROA
137.229.64.0/21RADBNo ROA
137.229.72.0/22RADBNo ROA
137.229.80.0/20RADBNo ROA
137.229.96.0/21RADBNo ROA
137.229.104.0/23RADBNo ROA
137.229.104.0/24RADBNo ROA
137.229.106.0/23RADBNo ROA
137.229.108.0/24RADBNo ROA
137.229.109.0/24RADBNo ROA
137.229.110.0/24RADBNo ROA
137.229.111.0/24RADBNo ROA
137.229.112.0/22RADBNo ROA
137.229.116.0/23RADBNo ROA
137.229.117.224/27RADBNo ROA
137.229.118.0/23RADBNo ROA
137.229.120.0/22RADBNo ROA
137.229.124.0/22RADBNo ROA
137.229.128.0/18RADBNo ROA
137.229.192.0/19RADBNo ROA
137.229.224.0/19RADBNo ROA
137.229.224.0/22RADBNo ROA
137.229.228.0/22RADBNo ROA
137.229.232.0/21RADBNo ROA
137.229.240.0/22RADBNo ROA
137.229.240.0/23RADBNo ROA
137.229.242.0/23RADBNo ROA
137.229.244.0/23RADBNo ROA
137.229.246.0/23RADBNo ROA
137.229.247.0/24RADBNo ROA
137.229.248.0/23RADBNo ROA
137.229.250.0/23RADBNo ROA
137.229.250.192/26RADBNo ROA
137.229.252.0/22RADBNo ROA
199.165.64.0/20RADBNo ROA
199.165.64.0/21RADBNo ROA
199.165.72.0/22RADBNo ROA
199.165.72.8/29RADBNo ROA
199.165.75.32/27RADBNo ROA
199.165.76.0/22RADBNo ROA
199.165.76.16/28RADBNo ROA
199.165.80.0/21RADBNo ROA
199.165.80.0/22RADBNo ROA
199.165.88.0/21RADBNo ROA
199.165.96.0/19RADBNo ROA
199.165.96.0/22RADBNo 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.