bgpreport

Network · data from 2026-11-12

AS393924 RIGNET-ISP - RigNet Inc

Registry name: RIGNET-ISP - RigNet Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393924, 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.
216.129.160.0/23 No ROA Other origin onlycovered by 216.129.160.0/21 673 100% 67
216.129.162.0/23 No ROA Other origin onlycovered by 216.129.160.0/21 673 100% 67
216.129.164.0/24 No ROA Nonecovered by 216.129.160.0/21 673 100% 67
216.129.166.0/23 No ROA Other origin onlycovered by 216.129.160.0/21 673 100% 67
216.129.167.0/24 No ROA Other origin onlycovered by 216.129.160.0/21 673 100% 67
66.51.32.0/20 No ROA Other IRR onlyRADB 673 100% 67
208.111.96.0/20 No ROA Other IRR onlyRADB 673 100% 67
216.129.168.0/23 No ROA Other IRR onlyRADB 673 100% 67
216.129.174.0/23 No ROA Other IRR onlyRADB 673 100% 67
2605:c800::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS393924 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 21 are in fix.csv.

  • ROA: none10
  • Route object: none5
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none216.129.160.0/23No ROA covers it. Add a ROA for AS393924, maxLength 23.673 of 673
Route object: none216.129.160.0/23Route objects for it name AS19905. A route object for 216.129.160.0/21 with origin AS393924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393924 in the RIR database for the space.673 of 673
ROA: none216.129.162.0/23No ROA covers it. Add a ROA for AS393924, maxLength 23.673 of 673
Route object: none216.129.162.0/23Route objects for it name AS19905. A route object for 216.129.160.0/21 with origin AS393924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393924 in the RIR database for the space.673 of 673
ROA: none216.129.164.0/24No ROA covers it. Add a ROA for AS393924, maxLength 24.673 of 673
Route object: none216.129.164.0/24No route object for it. A route object for 216.129.160.0/21 with origin AS393924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393924 in the RIR database for the space.673 of 673
ROA: none216.129.166.0/23No ROA covers it. Add a ROA for AS393924, maxLength 23.673 of 673
Route object: none216.129.166.0/23Route objects for it name AS19905. A route object for 216.129.160.0/21 with origin AS393924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393924 in the RIR database for the space.673 of 673
ROA: none216.129.167.0/24No ROA covers it. Add a ROA for AS393924, maxLength 24.673 of 673
Route object: none216.129.167.0/24Route objects for it name AS19905. A route object for 216.129.160.0/21 with origin AS393924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393924 in the RIR database for the space.673 of 673
ROA: none66.51.32.0/20No ROA covers it. Add a ROA for AS393924, maxLength 20.673 of 673
Route object: RIR66.51.32.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.111.96.0/20No ROA covers it. Add a ROA for AS393924, maxLength 20.673 of 673
Route object: RIR208.111.96.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.129.168.0/23No ROA covers it. Add a ROA for AS393924, maxLength 23.673 of 673
Route object: RIR216.129.168.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.129.174.0/23No ROA covers it. Add a ROA for AS393924, maxLength 23.673 of 673
Route object: RIR216.129.174.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2605:c800::/32No ROA covers it. Add a ROA for AS393924, maxLength 32.636 of 636
Route object: RIR2605:c800::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

216.129.160.0/21RADBNo 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.