bgpreport

Network · data from 2026-11-12

AS196 BOEING196 - The Boeing Company

Registry name: BOEING196 - The Boeing Company, US · not in PeeringDB

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

Announced routes

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

83.210.0.0/16 No ROA None 673 100% 67
130.76.0.0/16 No ROA None 673 100% 67
130.76.0.0/19 No ROA None 673 100% 67
130.76.24.0/23 No ROA None 673 100% 67
130.76.32.0/19 No ROA None 673 100% 67
130.76.64.0/19 No ROA None 673 100% 67
130.76.96.0/19 No ROA None 673 100% 67
130.76.128.0/19 No ROA None 673 100% 67
130.76.160.0/19 No ROA None 673 100% 67
130.76.192.0/19 No ROA None 673 100% 67
192.76.190.0/23 No ROA None 673 100% 67
192.76.191.0/24 No ROA None 673 100% 67
192.76.192.0/22 No ROA None 673 100% 67
192.76.217.0/24 No ROA None 673 100% 67
192.76.218.0/24 No ROA None 673 100% 67
192.76.219.0/24 No ROA None 673 100% 67

AS-SET

AS196 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 32 are in fix.csv.

  • ROA: none16
  • Route object: none16
ChangePrefix or setDetailFull-table peers
ROA: none83.210.0.0/16No ROA covers it. Add a ROA for AS196, maxLength 16.673 of 673
Route object: none83.210.0.0/16No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.0.0/16No ROA covers it. Add a ROA for AS196, maxLength 16.673 of 673
Route object: none130.76.0.0/16No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.0.0/19No ROA covers it. Add a ROA for AS196, maxLength 19.673 of 673
Route object: none130.76.0.0/19No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.24.0/23No ROA covers it. Add a ROA for AS196, maxLength 23.673 of 673
Route object: none130.76.24.0/23No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.32.0/19No ROA covers it. Add a ROA for AS196, maxLength 19.673 of 673
Route object: none130.76.32.0/19No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.64.0/19No ROA covers it. Add a ROA for AS196, maxLength 19.673 of 673
Route object: none130.76.64.0/19No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.96.0/19No ROA covers it. Add a ROA for AS196, maxLength 19.673 of 673
Route object: none130.76.96.0/19No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.128.0/19No ROA covers it. Add a ROA for AS196, maxLength 19.673 of 673
Route object: none130.76.128.0/19No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.160.0/19No ROA covers it. Add a ROA for AS196, maxLength 19.673 of 673
Route object: none130.76.160.0/19No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none130.76.192.0/19No ROA covers it. Add a ROA for AS196, maxLength 19.673 of 673
Route object: none130.76.192.0/19No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none192.76.190.0/23No ROA covers it. Add a ROA for AS196, maxLength 23.673 of 673
Route object: none192.76.190.0/23No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none192.76.191.0/24No ROA covers it. Add a ROA for AS196, maxLength 24.673 of 673
Route object: none192.76.191.0/24No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none192.76.192.0/22No ROA covers it. Add a ROA for AS196, maxLength 22.673 of 673
Route object: none192.76.192.0/22No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none192.76.217.0/24No ROA covers it. Add a ROA for AS196, maxLength 24.673 of 673
Route object: none192.76.217.0/24No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none192.76.218.0/24No ROA covers it. Add a ROA for AS196, maxLength 24.673 of 673
Route object: none192.76.218.0/24No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673
ROA: none192.76.219.0/24No ROA covers it. Add a ROA for AS196, maxLength 24.673 of 673
Route object: none192.76.219.0/24No route object for it. Add a route object with origin AS196 in the RIR database for the space.673 of 673

Route objects not announced

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