bgpreport

Network · data from 2026-11-12

AS16669 APPLIED-MATERIALS - Applied Materials

Registry name: APPLIED-MATERIALS - Applied Materials, US · not in PeeringDB

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

Announced routes

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

152.135.0.0/16 No ROA None 673 100% 67
152.135.132.0/24 No ROA Other origin only 673 100% 67
152.135.192.0/19 No ROA None 673 100% 67
152.135.224.0/19 No ROA None 673 100% 67
152.135.226.0/24 No ROA None 673 100% 67
12.151.38.0/24 No ROA None 672 100% 67
152.135.110.0/24 No ROA None 672 100% 67
152.135.128.0/19 No ROA None 672 100% 67
152.135.133.0/24 No ROA None 672 100% 67
152.135.160.0/19 No ROA None 672 100% 67
192.86.88.0/24 No ROA Other origin only 672 100% 67
199.33.179.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.194.155.0/24 No ROA Other IRR onlyRADB 673 100% 67
221.141.178.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.116.115.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS16669 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 28 are in fix.csv.

  • ROA: none14
  • Route object: none11
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none152.135.0.0/16No ROA covers it. Add a ROA for AS16669, maxLength 16.673 of 673
Route object: none152.135.0.0/16No route object for it. Add a route object with origin AS16669 in the RIR database for the space.673 of 673
ROA: none152.135.132.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.673 of 673
Route object: none152.135.132.0/24Route objects for it name AS19905. Add a route object with origin AS16669 in the RIR database for the space.673 of 673
ROA: none152.135.192.0/19No ROA covers it. Add a ROA for AS16669, maxLength 19.673 of 673
Route object: none152.135.192.0/19No route object for it. Add a route object with origin AS16669 in the RIR database for the space.673 of 673
ROA: none152.135.224.0/19No ROA covers it. Add a ROA for AS16669, maxLength 19.673 of 673
Route object: none152.135.224.0/19No route object for it. Add a route object with origin AS16669 in the RIR database for the space.673 of 673
ROA: none152.135.226.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.673 of 673
Route object: none152.135.226.0/24No route object for it. Add a route object with origin AS16669 in the RIR database for the space.673 of 673
ROA: none12.151.38.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.672 of 673
Route object: none12.151.38.0/24No route object for it. Add a route object with origin AS16669 in the RIR database for the space.672 of 673
ROA: none152.135.110.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.672 of 673
Route object: none152.135.110.0/24No route object for it. Add a route object with origin AS16669 in the RIR database for the space.672 of 673
ROA: none152.135.128.0/19No ROA covers it. Add a ROA for AS16669, maxLength 19.672 of 673
Route object: none152.135.128.0/19No route object for it. Add a route object with origin AS16669 in the RIR database for the space.672 of 673
ROA: none152.135.133.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.672 of 673
Route object: none152.135.133.0/24No route object for it. Add a route object with origin AS16669 in the RIR database for the space.672 of 673
ROA: none152.135.160.0/19No ROA covers it. Add a ROA for AS16669, maxLength 19.672 of 673
Route object: none152.135.160.0/19No route object for it. Add a route object with origin AS16669 in the RIR database for the space.672 of 673
ROA: none192.86.88.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.672 of 673
Route object: none192.86.88.0/24Route objects for it name AS16999. Add a route object with origin AS16669 in the RIR database for the space.672 of 673
ROA: none199.33.179.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.673 of 673
Route object: RIR199.33.179.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.194.155.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.673 of 673
Route object: RIR211.194.155.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none221.141.178.0/24No ROA covers it. Add a ROA for AS16669, maxLength 24.672 of 673
Route object: RIR221.141.178.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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