bgpreport

Network · data from 2026-11-12

AS7872 USAP-ASN - United States Antarctic Program

Registry name: USAP-ASN - United States Antarctic Program, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7872, 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.
192.207.225.0/24 No ROA None 672 100% 67
157.132.0.0/16 No ROA Other IRR onlyRADB 673 100% 67
192.150.224.0/24 No ROA Other IRR onlyRADB 673 100% 67
198.102.91.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.4.250.0/23 No ROA Other IRR onlyRADB 673 100% 67
199.184.189.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.201.248.0/23 No ROA Other IRR onlyRADB 673 100% 67
204.89.132.0/23 No ROA Other IRR onlyRADB 673 100% 67
204.238.237.0/24 No ROA Other IRR onlyRADB 673 100% 67
2620:11d:3000::/44 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS7872 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none1
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none192.207.225.0/24No ROA covers it. Add a ROA for AS7872, maxLength 24.672 of 673
Route object: none192.207.225.0/24No route object for it. Add a route object with origin AS7872 in the RIR database for the space.672 of 673
ROA: none157.132.0.0/16No ROA covers it. Add a ROA for AS7872, maxLength 16.673 of 673
Route object: RIR157.132.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.150.224.0/24No ROA covers it. Add a ROA for AS7872, maxLength 24.673 of 673
Route object: RIR192.150.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.102.91.0/24No ROA covers it. Add a ROA for AS7872, maxLength 24.673 of 673
Route object: RIR198.102.91.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.4.250.0/23No ROA covers it. Add a ROA for AS7872, maxLength 23.673 of 673
Route object: RIR199.4.250.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.184.189.0/24No ROA covers it. Add a ROA for AS7872, maxLength 24.673 of 673
Route object: RIR199.184.189.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.201.248.0/23No ROA covers it. Add a ROA for AS7872, maxLength 23.673 of 673
Route object: RIR199.201.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.89.132.0/23No ROA covers it. Add a ROA for AS7872, maxLength 23.673 of 673
Route object: RIR204.89.132.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.238.237.0/24No ROA covers it. Add a ROA for AS7872, maxLength 24.673 of 673
Route object: RIR204.238.237.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2620:11d:3000::/44No ROA covers it. Add a ROA for AS7872, maxLength 44.636 of 636
Route object: RIR2620:11d:3000::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS7872 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.