bgpreport

Network · data from 2026-11-12

AS14762 AMGEN - AMGEN, Inc.

Registry name: AMGEN - AMGEN, Inc., US · not in PeeringDB

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

Announced routes

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

198.178.219.0/24 No ROA None 673 100% 67
138.133.25.0/24 No ROA None 667 99% 67
138.133.61.0/24 No ROA None 667 99% 67
138.133.232.0/22 No ROA Other IRR onlyRADB 672 100% 67
192.207.147.0/24 No ROA Other IRR onlyRADB 672 100% 67
198.176.189.0/24 No ROA Other IRR onlyRADB 672 100% 67
198.176.190.0/24 No ROA Other IRR onlyRADB 672 100% 67
138.133.60.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.133.192.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.133.194.0/24 No ROA Other IRR onlyRADB 667 99% 67
198.176.188.0/24 No ROA Other IRR onlyRADB 667 99% 67
198.176.191.0/24 No ROA Other IRR onlyRADB 667 99% 67
198.178.218.0/24 No ROA Other IRR onlyNTTCOM 667 99% 67
198.178.220.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.133.52.0/24 No ROA Other IRR onlyRADB 665 99% 67
138.133.183.0/24 No ROA RIR databaseARIN 673 100% 67
138.133.177.0/24 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS14762 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 40 are in fix.csv.

  • ROA: none17
  • Route object: none3
  • Route object: RIR12
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none198.178.219.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.673 of 673
Route object: none198.178.219.0/24No route object for it. Add a route object with origin AS14762 in the RIR database for the space.673 of 673
ROA: none138.133.25.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: none138.133.25.0/24No route object for it. Add a route object with origin AS14762 in the RIR database for the space.667 of 673
ROA: none138.133.61.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: none138.133.61.0/24No route object for it. Add a route object with origin AS14762 in the RIR database for the space.667 of 673
ROA: none138.133.232.0/22No ROA covers it. Add a ROA for AS14762, maxLength 22.672 of 673
Route object: RIR138.133.232.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.207.147.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.672 of 673
Route object: RIR192.207.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.176.189.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.672 of 673
Route object: RIR198.176.189.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.176.190.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.672 of 673
Route object: RIR198.176.190.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none138.133.60.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: RIR138.133.60.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.133.192.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: RIR138.133.192.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.133.194.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: RIR138.133.194.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none198.176.188.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: RIR198.176.188.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none198.176.191.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: RIR198.176.191.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none198.178.218.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: RIR198.178.218.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
ROA: none198.178.220.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.667 of 673
Route object: RIR198.178.220.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.133.52.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.665 of 673
Route object: RIR138.133.52.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none138.133.183.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.673 of 673
ROA: none138.133.177.0/24No ROA covers it. Add a ROA for AS14762, maxLength 24.672 of 673

Route objects not announced

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

138.133.0.0/26RADBNo ROA
138.133.17.0/24RADBNo ROA
138.133.71.0/24RADBNo ROA
138.133.81.0/24RADBNo ROA
138.133.82.0/24RADBNo ROA
138.133.192.0/22RADBNo ROA
138.133.240.0/22RADBNo ROA
192.207.148.0/24RADBNo 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.