bgpreport

Network · data from 2026-11-12

AS397019 ROCKETCONNECT - Rocket Connect LLC

Registry name: ROCKETCONNECT - Rocket Connect LLC, US · not in PeeringDB

8IPv4 routes 12.5% RPKI valid · 50.0% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No 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 AS397019, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS397019, 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.
130.51.228.0/24 No ROA Nonecovered by 130.51.228.0/22 672 100% 67
130.51.229.0/24 No ROA Nonecovered by 130.51.228.0/22 672 100% 67
130.51.230.0/24 No ROA Nonecovered by 130.51.228.0/22 672 100% 67
130.51.231.0/24 No ROA Nonecovered by 130.51.228.0/22 671 100% 68
2605:c0::/34 No ROA Nonecovered by 2605:c0::/32 634 100% 68
23.155.160.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.39.214.0/23 No ROA Other IRR onlyRADB 671 100% 68
2605:c0::/32 No ROA Other IRR onlyRADB 634 100% 69
67.210.51.0/24 No ROA RIR databaseARIN 669 99% 68
71.86.143.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS397019 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 19 are in fix.csv.

  • ROA: none9
  • Route object: none5
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none130.51.228.0/24No ROA covers it. Add a ROA for AS397019, maxLength 24.672 of 673
Route object: none130.51.228.0/24No route object for it. A route object for 130.51.228.0/22 with origin AS397019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397019 in the RIR database for the space.672 of 673
ROA: none130.51.229.0/24No ROA covers it. Add a ROA for AS397019, maxLength 24.672 of 673
Route object: none130.51.229.0/24No route object for it. A route object for 130.51.228.0/22 with origin AS397019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397019 in the RIR database for the space.672 of 673
ROA: none130.51.230.0/24No ROA covers it. Add a ROA for AS397019, maxLength 24.672 of 673
Route object: none130.51.230.0/24No route object for it. A route object for 130.51.228.0/22 with origin AS397019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397019 in the RIR database for the space.672 of 673
ROA: none130.51.231.0/24No ROA covers it. Add a ROA for AS397019, maxLength 24.671 of 673
Route object: none130.51.231.0/24No route object for it. A route object for 130.51.228.0/22 with origin AS397019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397019 in the RIR database for the space.671 of 673
ROA: none2605:c0::/34No ROA covers it. Add a ROA for AS397019, maxLength 34.634 of 636
Route object: none2605:c0::/34No route object for it. A route object for 2605:c0::/32 with origin AS397019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397019 in the RIR database for the space.634 of 636
ROA: none23.155.160.0/24No ROA covers it. Add a ROA for AS397019, maxLength 24.671 of 673
Route object: RIR23.155.160.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.39.214.0/23No ROA covers it. Add a ROA for AS397019, maxLength 23.671 of 673
Route object: RIR38.39.214.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2605:c0::/32No ROA covers it. Add a ROA for AS397019, maxLength 32.634 of 636
Route object: RIR2605:c0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none67.210.51.0/24No ROA covers it. Add a ROA for AS397019, maxLength 24.669 of 673
Route object: RIR71.86.143.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

130.51.228.0/22RADBNo 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.