These entries are queried from radb.net using whois, you can try my project getting these.
:AS23790 route: 119.161.112.0/21 descr: J:COM (former KCN-TV) origin: AS23790 mnt-by: MAINT-AS9824 changed: radb-notify [at] jupiter.jcom.co.jp 20151224 source: RADB last-modified: 2023-11-13T15:48:29Z rpki-ov-state: valid route: 119.161.112.0/21 descr: JCOM Co., Ltd. (J:COM) origin: AS23790 notify: jpirr-notify [at] jupiter.jcom.co.jp mnt-by: MAINT-AS9824 changed: jpirr-notify [at] jupiter.jcom.co.jp 20230728 source: JPIRR rpki-ov-state: valid route: 123.50.224.0/19 descr: PACNET (proxy-registered route object) origin: AS23790 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:54Z rpki-ov-state: not_found # No ROAs found, or RPKI validation not enabled for source route: 202.157.0.0/18 descr: JCOM Co., Ltd. (J:COM) origin: AS23790 notify: jpirr-notify [at] jupiter.jcom.co.jp mnt-by: MAINT-AS9824 changed: jpirr-notify [at] jupiter.jcom.co.jp 20230728 source: JPIRR rpki-ov-state: valid route: 202.157.0.0/18 descr: J:COM (former KCN-TV) origin: AS23790 mnt-by: MAINT-AS9824 changed: radb-notify [at] jupiter.jcom.co.jp 20151224 source: RADB last-modified: 2023-11-13T15:48:29Z rpki-ov-state: valid