bgpreport

Network · data from 2026-11-12

AS395624 GACORP - General Atomics

Registry name: GACORP - General Atomics, US · not in PeeringDB

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

Announced routes

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

141.248.0.0/19 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.32.0/20 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.50.0/23 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.64.0/18 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.128.0/18 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.192.0/19 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.224.0/20 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.240.0/21 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.248.0/23 No ROA Nonecovered by 141.248.0.0/16 673 100% 67
141.248.0.0/16 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS395624 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: none9
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none141.248.0.0/19No ROA covers it. Add a ROA for AS395624, maxLength 19.673 of 673
Route object: none141.248.0.0/19No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.32.0/20No ROA covers it. Add a ROA for AS395624, maxLength 20.673 of 673
Route object: none141.248.32.0/20No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.50.0/23No ROA covers it. Add a ROA for AS395624, maxLength 23.673 of 673
Route object: none141.248.50.0/23No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.64.0/18No ROA covers it. Add a ROA for AS395624, maxLength 18.673 of 673
Route object: none141.248.64.0/18No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.128.0/18No ROA covers it. Add a ROA for AS395624, maxLength 18.673 of 673
Route object: none141.248.128.0/18No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.192.0/19No ROA covers it. Add a ROA for AS395624, maxLength 19.673 of 673
Route object: none141.248.192.0/19No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.224.0/20No ROA covers it. Add a ROA for AS395624, maxLength 20.673 of 673
Route object: none141.248.224.0/20No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.240.0/21No ROA covers it. Add a ROA for AS395624, maxLength 21.673 of 673
Route object: none141.248.240.0/21No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.248.0/23No ROA covers it. Add a ROA for AS395624, maxLength 23.673 of 673
Route object: none141.248.248.0/23No route object for it. A route object for 141.248.0.0/16 with origin AS395624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395624 in the RIR database for the space.673 of 673
ROA: none141.248.0.0/16No ROA covers it. Add a ROA for AS395624, maxLength 16.673 of 673
Route object: RIR141.248.0.0/16Route 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 AS395624 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.