bgpreport

Network · data from 2026-11-12

AS14519 APPLIEDI - Applied Innovations Corporation

Registry name: APPLIEDI - Applied Innovations Corporation, US · not in PeeringDB

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

Announced routes

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

64.135.64.0/24 No ROA Other IRR onlyRADB 673 100% 67
174.136.64.0/19 No ROA Other IRR onlyRADB 673 100% 67
174.136.80.0/20 No ROA Other IRR onlyRADB 673 100% 67
216.167.192.0/20 No ROA Other IRR onlyALTDB 673 100% 67
64.238.36.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
64.238.37.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
64.238.38.0/24 No ROA RIR databaseARIN, RADB 673 100% 67

AS-SET

AS14519 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 125 are in fix.csv.

  • ROA: none7
  • Route object: RIR4
  • Route object: not announced114
ChangePrefix or setDetailFull-table peers
ROA: none64.135.64.0/24No ROA covers it. Add a ROA for AS14519, maxLength 24.673 of 673
Route object: RIR64.135.64.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none174.136.64.0/19No ROA covers it. Add a ROA for AS14519, maxLength 19.673 of 673
Route object: RIR174.136.64.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none174.136.80.0/20No ROA covers it. Add a ROA for AS14519, maxLength 20.673 of 673
Route object: RIR174.136.80.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.167.192.0/20No ROA covers it. Add a ROA for AS14519, maxLength 20.673 of 673
Route object: RIR216.167.192.0/20Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none64.238.36.0/24No ROA covers it. Add a ROA for AS14519, maxLength 24.673 of 673
ROA: none64.238.37.0/24No ROA covers it. Add a ROA for AS14519, maxLength 24.673 of 673
ROA: none64.238.38.0/24No ROA covers it. Add a ROA for AS14519, maxLength 24.673 of 673

Route objects not announced

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

66.252.224.0/24RADBNo ROA
66.252.225.0/24RADBNo ROA
66.252.226.0/24RADBNo ROA
66.252.227.0/24RADBNo ROA
66.252.228.0/22RADBNo ROA
66.252.228.0/23RADBNo ROA
66.252.228.0/24RADBNo ROA
66.252.229.0/24RADBNo ROA
66.252.230.0/23RADBNo ROA
66.252.230.0/24RADBNo ROA
66.252.231.0/24RADBNo ROA
66.252.232.0/21RADBNo ROA
66.252.232.0/22RADBNo ROA
66.252.232.0/23RADBNo ROA
66.252.232.0/24RADBNo ROA
66.252.233.0/24RADBNo ROA
66.252.234.0/23RADBNo ROA
66.252.234.0/24RADBNo ROA
66.252.235.0/24RADBNo ROA
66.252.236.0/22RADBNo ROA
66.252.236.0/23RADBNo ROA
66.252.236.0/24RADBNo ROA
66.252.237.0/24RADBNo ROA
66.252.238.0/23RADBNo ROA
66.252.238.0/24RADBNo ROA
66.252.239.0/24RADBNo ROA
70.34.16.0/20RADBNo ROA
70.34.16.0/22RADBNo ROA
174.136.64.0/20RADBNo ROA
174.136.64.0/21RADBNo ROA
174.136.64.0/22RADBNo ROA
174.136.64.0/23RADBNo ROA
174.136.64.0/24RADBNo ROA
174.136.65.0/24RADBNo ROA
174.136.66.0/23RADBNo ROA
174.136.66.0/24RADBNo ROA
174.136.67.0/24RADBNo ROA
174.136.68.0/22RADBNo ROA
174.136.68.0/23RADBNo ROA
174.136.68.0/24RADBNo ROA
174.136.69.0/24RADBNo ROA
174.136.70.0/23RADBNo ROA
174.136.70.0/24RADBNo ROA
174.136.71.0/24RADBNo ROA
174.136.72.0/21RADBNo ROA
174.136.72.0/22RADBNo ROA
174.136.72.0/23RADBNo ROA
174.136.72.0/24RADBNo ROA
174.136.73.0/24RADBNo ROA
174.136.74.0/23RADBNo ROA
174.136.74.0/24RADBNo ROA
174.136.75.0/24RADBNo ROA
174.136.76.0/22RADBNo ROA
174.136.76.0/23RADBNo ROA
174.136.76.0/24RADBNo ROA
174.136.77.0/24RADBNo ROA
174.136.78.0/23RADBNo ROA
174.136.78.0/24RADBNo ROA
174.136.79.0/24RADBNo ROA
174.136.80.0/21RADBNo ROA
174.136.80.0/22RADBNo ROA
174.136.80.0/23RADBNo ROA
174.136.80.0/24RADBNo ROA
174.136.81.0/24RADBNo ROA
174.136.82.0/23RADBNo ROA
174.136.82.0/24RADBNo ROA
174.136.83.0/24RADBNo ROA
174.136.84.0/22RADBNo ROA
174.136.84.0/23RADBNo ROA
174.136.84.0/24RADBNo ROA
174.136.85.0/24RADBNo ROA
174.136.86.0/23RADBNo ROA
174.136.86.0/24RADBNo ROA
174.136.87.0/24RADBNo ROA
174.136.88.0/21RADBNo ROA
174.136.88.0/22RADBNo ROA
174.136.88.0/23RADBNo ROA
174.136.88.0/24RADBNo ROA
174.136.89.0/24RADBNo ROA
174.136.90.0/23RADBNo ROA
174.136.90.0/24RADBNo ROA
174.136.91.0/24RADBNo ROA
174.136.92.0/22RADBNo ROA
174.136.92.0/23RADBNo ROA
174.136.92.0/24RADBNo ROA
174.136.93.0/24RADBNo ROA
174.136.94.0/23RADBNo ROA
174.136.94.0/24RADBNo ROA
204.29.162.0/24RADBNo ROA
216.167.192.0/21RADBNo ROA
216.167.192.0/22RADBNo ROA
216.167.192.0/23RADBNo ROA
216.167.192.0/24RADBNo ROA
216.167.193.0/24RADBNo ROA
216.167.194.0/23RADBNo ROA
216.167.194.0/24RADBNo ROA
216.167.195.0/24RADBNo ROA
216.167.196.0/22RADBNo ROA
216.167.196.0/23RADBNo ROA
216.167.196.0/24RADBNo ROA
216.167.197.0/24RADBNo ROA
216.167.198.0/23RADBNo ROA
216.167.198.0/24RADBNo ROA
216.167.199.0/24RADBNo ROA
216.167.200.0/21RADBNo ROA
216.167.200.0/22RADBNo ROA
216.167.200.0/23RADBNo ROA
216.167.201.0/24RADBNo ROA
216.167.202.0/23RADBNo ROA
216.167.204.0/22RADBNo ROA
216.167.204.0/23RADBNo ROA
216.167.206.0/23RADBNo ROA
216.167.206.0/24RADBNo ROA
216.167.207.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.