These entries are queried from radb.net using whois, you can try my project getting these.
:AS17741 route: 114.31.96.0/21 descr: PACNET (proxy-registered route object) origin: AS17741 remarks: This route object is for a PACNET customer route which is being exported under this origin AS. + This route object was created because no existing route object with the same origin was found, and since some PACNET peers filter based on these objects this route may be rejected if this object is not created. + Please contact abuse [at] pacnet.net if you have any Concerns regarding Spam/Abuses related to this object + Please contact ip-noc [at] pacnet.net if you have any other Questions regarding this object. notify: ip-noc [at] pacnet.net mnt-by: MAINT-AS4637 changed: ip-noc [at] pacnet.net 20100201 source: RADB last-modified: 2023-11-13T15:58:53Z rpki-ov-state: valid route: 114.31.96.0/21 descr: MEDICAL-OBJECTS origin: AS17741 notify: noc [at] pipenetworks.com mnt-by: MAINT-PIPENOC changed: networks [at] pipenetworks.com 20080515 source: NTTCOM rpki-ov-state: valid route: 202.44.75.0/24 descr: Proxy route object registered by AS38195 origin: AS17741 remarks: This route object was created by Superloop on behalf of a customer. notify: peering [at] superloop.com mnt-by: MAINT-AS38195 changed: peering [at] superloop.com 20230219 source: RADB last-modified: 2023-11-13T16:18:15Z rpki-ov-state: valid route: 202.44.75.0/24 descr: Medical Objects origin: AS17741 notify: noc [at] pipenetworks.com mnt-by: MAINT-PIPENOC changed: david.kuzmak [at] staff.pipenetworks.com 20070206 source: NTTCOM rpki-ov-state: valid