bgpreport

Network · data from 2026-11-12

AS396322 PC-ASN - Peace Corps

Registry name: PC-ASN - Peace Corps, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS396322, 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.
2601:1201::/40 No ROA None 636 100% 67
2601:1202::/48 No ROA None 636 100% 67
2601:1202:3::/48 No ROA None 636 100% 67
2601:1202:4::/48 No ROA None 636 100% 67
2601:1202:5::/48 No ROA None 636 100% 67
2620:137:7000::/40 No ROA None 636 100% 67
65.205.231.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS396322 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2601:1201::/40No ROA covers it. Add a ROA for AS396322, maxLength 40.636 of 636
Route object: none2601:1201::/40No route object for it. Add a route object with origin AS396322 in the RIR database for the space.636 of 636
ROA: none2601:1202::/48No ROA covers it. Add a ROA for AS396322, maxLength 48.636 of 636
Route object: none2601:1202::/48No route object for it. Add a route object with origin AS396322 in the RIR database for the space.636 of 636
ROA: none2601:1202:3::/48No ROA covers it. Add a ROA for AS396322, maxLength 48.636 of 636
Route object: none2601:1202:3::/48No route object for it. Add a route object with origin AS396322 in the RIR database for the space.636 of 636
ROA: none2601:1202:4::/48No ROA covers it. Add a ROA for AS396322, maxLength 48.636 of 636
Route object: none2601:1202:4::/48No route object for it. Add a route object with origin AS396322 in the RIR database for the space.636 of 636
ROA: none2601:1202:5::/48No ROA covers it. Add a ROA for AS396322, maxLength 48.636 of 636
Route object: none2601:1202:5::/48No route object for it. Add a route object with origin AS396322 in the RIR database for the space.636 of 636
ROA: none2620:137:7000::/40No ROA covers it. Add a ROA for AS396322, maxLength 40.636 of 636
Route object: none2620:137:7000::/40No route object for it. Add a route object with origin AS396322 in the RIR database for the space.636 of 636
ROA: none65.205.231.0/24No ROA covers it. Add a ROA for AS396322, maxLength 24.673 of 673
Route object: RIR65.205.231.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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