bgpreport

Network · data from 2026-11-12

AS47054 JETWASN - JetWire, INC

Registry name: JETWASN - JetWire, INC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47054, 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.189.0/24 No ROA Nonecovered by 130.51.188.0/22 673 100% 67
130.51.190.0/24 No ROA Nonecovered by 130.51.188.0/22 673 100% 67
130.51.191.0/24 No ROA Nonecovered by 130.51.188.0/22 673 100% 67
204.13.160.0/23 No ROA Nonecovered by 204.13.160.0/22 673 100% 67
8.3.51.0/24 No ROA None 671 100% 68
8.19.133.0/24 No ROA None 671 100% 68
8.34.117.0/24 No ROA None 671 100% 68
8.19.133.66/32 No ROA None 1 0%low visibility 1
8.34.117.138/32 No ROA None 1 0%low visibility 1
172.99.128.76/32 No ROA Nonecovered by 172.99.128.0/22 1 0%low visibility 1
130.51.188.0/22 No ROA RIR databaseARIN 673 100% 68
172.83.64.0/22 No ROA RIR databaseARIN 673 100% 68
172.99.128.0/22 No ROA RIR databaseARIN 673 100% 68
204.13.160.0/22 No ROA RIR databaseARIN 673 100% 68

AS-SET

AS47054 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 24 are in fix.csv.

  • ROA: none14
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: none130.51.189.0/24No ROA covers it. Add a ROA for AS47054, maxLength 24.673 of 673
Route object: none130.51.189.0/24No route object for it. A route object for 130.51.188.0/22 with origin AS47054 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47054 in the RIR database for the space.673 of 673
ROA: none130.51.190.0/24No ROA covers it. Add a ROA for AS47054, maxLength 24.673 of 673
Route object: none130.51.190.0/24No route object for it. A route object for 130.51.188.0/22 with origin AS47054 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47054 in the RIR database for the space.673 of 673
ROA: none130.51.191.0/24No ROA covers it. Add a ROA for AS47054, maxLength 24.673 of 673
Route object: none130.51.191.0/24No route object for it. A route object for 130.51.188.0/22 with origin AS47054 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47054 in the RIR database for the space.673 of 673
ROA: none204.13.160.0/23No ROA covers it. Add a ROA for AS47054, maxLength 23.673 of 673
Route object: none204.13.160.0/23No route object for it. A route object for 204.13.160.0/22 with origin AS47054 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47054 in the RIR database for the space.673 of 673
ROA: none8.3.51.0/24No ROA covers it. Add a ROA for AS47054, maxLength 24.671 of 673
Route object: none8.3.51.0/24No route object for it. Add a route object with origin AS47054 in the RIR database for the space.671 of 673
ROA: none8.19.133.0/24No ROA covers it. Add a ROA for AS47054, maxLength 24.671 of 673
Route object: none8.19.133.0/24No route object for it. Add a route object with origin AS47054 in the RIR database for the space.671 of 673
ROA: none8.34.117.0/24No ROA covers it. Add a ROA for AS47054, maxLength 24.671 of 673
Route object: none8.34.117.0/24No route object for it. Add a route object with origin AS47054 in the RIR database for the space.671 of 673
ROA: none8.19.133.66/32No ROA covers it. Add a ROA for AS47054, maxLength 32.1 of 673
Route object: none8.19.133.66/32No route object for it. Add a route object with origin AS47054 in the RIR database for the space.1 of 673
ROA: none8.34.117.138/32No ROA covers it. Add a ROA for AS47054, maxLength 32.1 of 673
Route object: none8.34.117.138/32No route object for it. Add a route object with origin AS47054 in the RIR database for the space.1 of 673
ROA: none172.99.128.76/32No ROA covers it. Add a ROA for AS47054, maxLength 32.1 of 673
Route object: none172.99.128.76/32No route object for it. A route object for 172.99.128.0/22 with origin AS47054 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47054 in the RIR database for the space.1 of 673
ROA: none130.51.188.0/22No ROA covers it. Add a ROA for AS47054, maxLength 22.673 of 673
ROA: none172.83.64.0/22No ROA covers it. Add a ROA for AS47054, maxLength 22.673 of 673
ROA: none172.99.128.0/22No ROA covers it. Add a ROA for AS47054, maxLength 22.673 of 673
ROA: none204.13.160.0/22No ROA covers it. Add a ROA for AS47054, maxLength 22.673 of 673

Route objects not announced

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