bgpreport

Network · data from 2026-11-12

AS9751 AMERICAN SAMOA TELECOMMUNICATIONS AUTHORITY

Registry name: ASTCA-AS-AP - AMERICAN SAMOA TELECOMMUNICATIONS AUTHORITY, AS · PeeringDB

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

Announced routes

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

208.136.102.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
65.219.178.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
2403:2140::/32 No ROA Other IRR onlyNTTCOM, RADB 635 100% 68
103.117.168.0/22 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
8.41.134.0/24 Valid None 673 100% 67
8.41.132.0/23 Valid Other IRR onlyNTTCOM 673 100% 67
65.167.226.0/24 Valid Other IRR onlyNTTCOM 673 100% 68
206.80.28.0/22 Valid Other IRR onlyNTTCOM 673 100% 68
206.80.28.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
206.80.29.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
206.80.30.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
206.80.31.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
65.167.227.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
205.161.14.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
205.161.15.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
38.101.165.0/24 Valid RIR databaseARIN, NTTCOM, RADB 671 100% 68
38.111.133.0/24 Valid RIR databaseARIN, NTTCOM, RADB 671 100% 68
38.134.240.0/24 Valid RIR databaseARIN, NTTCOM, RADB 670 100% 68
38.134.243.0/24 Valid RIR databaseARIN, NTTCOM, RADB 670 100% 68
208.15.230.0/24 Valid RIR databaseARIN, NTTCOM, RADB 670 100% 68

AS-SET

AS9751'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 29 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: RIR13
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none208.136.102.0/24No ROA covers it. Add a ROA for AS9751, maxLength 24.673 of 673
Route object: RIR208.136.102.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none65.219.178.0/24No ROA covers it. Add a ROA for AS9751, maxLength 24.670 of 673
Route object: RIR65.219.178.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2403:2140::/32No ROA covers it. Add a ROA for AS9751, maxLength 32.635 of 636
Route object: RIR2403:2140::/32Route object only in NTTCOM, RADB. Add it in the RIR database for the space.635 of 636
ROA: none103.117.168.0/22No ROA covers it. Add a ROA for AS9751, maxLength 22.672 of 673
Route object: none8.41.134.0/24No route object for it. Add a route object with origin AS9751 in the RIR database for the space.673 of 673
Route object: RIR8.41.132.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR65.167.226.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR206.80.28.0/22Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR206.80.28.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.80.29.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.80.30.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.80.31.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR65.167.227.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR205.161.14.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR205.161.15.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

65.167.226.0/23ARINValid
66.167.226.0/24RADBNo ROA
66.178.5.0/24NTTCOM, RADBNo ROA
66.178.14.0/24NTTCOM, RADBNo ROA
103.117.168.0/23APNICNo ROA
103.117.168.0/24APNICNo ROA
103.117.169.0/24APNICNo ROA
103.117.170.0/23APNICNo ROA
103.117.170.0/24APNICNo ROA
103.117.171.0/24APNICNo ROA
205.161.14.0/23ARINValid

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.